From lukas.fryc at gmail.com  Wed Oct  1 01:29:36 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Wed, 1 Oct 2014 07:29:36 +0200
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <9305F238-822C-447A-9612-FC34FBEA8015@gmail.com>
References: <20140930231258.GB26685@abstractj.org>
	<9305F238-822C-447A-9612-FC34FBEA8015@gmail.com>
Message-ID: <CAEroY34dQeug-BR__CR+HDg1yau84=XFtGVatGbaWBtSRisH2A@mail.gmail.com>

+1

On Wed, Oct 1, 2014 at 1:18 AM, S?bastien Blanc <scm.blanc at gmail.com> wrote:

> +1 sounds good !
>
> Envoy? de mon iPhone
>
> > Le 30 sept. 2014 ? 16:12, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> >
> > Good morning guys, I would like to set up a meeting Wednesday next week
> > (same time of our official meeting) if possible.
> >
> > Only to stay up to date with what you have been doing/planning. I can
> > dig into repositories but not into your brain :).
> >
> > Also, plan the next steps for security.
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/0fe9a7de/attachment.html 

From lukas.fryc at gmail.com  Wed Oct  1 01:35:07 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Wed, 1 Oct 2014 07:35:07 +0200
Subject: [aerogear-dev] Data Sync / Conflict Resolution: Kick Off
In-Reply-To: <20140930233414.GF26685@abstractj.org>
References: <CAEroY37VUSTHEr9Nac3rHN6h7QsM1JUd8u8jj5hxYVGrkMz2bA@mail.gmail.com>
	<20140930233414.GF26685@abstractj.org>
Message-ID: <CAEroY34-ZAqyvf1w+XMd8sguBHidtGZMT-HSz1YoRNt3+dtuWQ@mail.gmail.com>

Sure, we currently have two roadmaps for Data Sync in works btw:

Conflict Resolution
https://github.com/aerogear/aerogear.org/blob/data-sync-rebirth-roadmap/docs/planning/roadmaps/AeroGearConflictResolution.asciidoc

Realtime Data Sync
https://github.com/danbev/beta.aerogear.org/blob/2ff3e120cc75f9258aa05d03dc073b4a6a6fbbbb/docs/planning/roadmaps/AeroGearDataSync.asciidoc


Cheers,

~ Lukas

On Wed, Oct 1, 2014 at 1:34 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Hi Luk??, I would like to add my security sauce to the dance if
> possible. May I?
>
> On 2014-09-18, Luk?? Fry? wrote:
> > Hey guys,
> >
> > we have finished a ritual dance around Conflict Resolution Roadmap and
> this
> > is the final draft:
> >
> >
> https://github.com/aerogear/aerogear.org/blob/data-sync-rebirth-roadmap/docs/planning/roadmaps/AeroGearConflictResolution.asciidoc
> >
> >
> > Can I ask all the component leads to do a final review and +1 to
> > acknowledge we can start works here?
> >
> > Off course every review & feedback will be more than welcomed!
> >
> >
> > Cheers,
> >
> > ~ Lukas
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/12a74e47/attachment-0001.html 

From pstribny at redhat.com  Wed Oct  1 04:29:28 2014
From: pstribny at redhat.com (Petr Stribny)
Date: Wed, 1 Oct 2014 04:29:28 -0400 (EDT)
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate	on remote IP
In-Reply-To: <1411036049385-9213.post@n5.nabble.com>
References: <1411036049385-9213.post@n5.nabble.com>
Message-ID: <67887222.39198630.1412152168215.JavaMail.zimbra@redhat.com>

Hi,

> I am trying to configure SSL with self signed certificate on remote IP. I am
> using wildly 8.1 and aerogear push 1.0 jars. I get SSLHandshakeException
> when trying to send register request on port 8443.

Can you be more specific about your approach? 

Generally speaking the client has to use a truststore with your custom certificate and server
has to be configured to present itself with it.

> Moreover when i try to build the source with maven, build is successful but
> war files are not being generated. Have i missed something?

What are you building and how?

--Petr

From bruno at abstractj.org  Wed Oct  1 05:04:08 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 1 Oct 2014 02:04:08 -0700
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate on remote IP
In-Reply-To: <1411036049385-9213.post@n5.nabble.com>
References: <1411036049385-9213.post@n5.nabble.com>
Message-ID: <20141001090408.GA36834@abstractj.org>

I'm so sorry for not getting back you, I was on vacation. Could you
please share the details like which kind of exception did you get,
docker image name.

I would be more than happy trying to reproduce your issue to fix it.

Thanks in advance.

On 2014-09-18, infiniteloop wrote:
> I am trying to configure SSL with self signed certificate on remote IP. I am
> using wildly 8.1 and aerogear push 1.0 jars. I get SSLHandshakeException
> when trying to send register request on port 8443.
> I tried the image mounted with docker created by abstractj but still no
> luck. Please suggest a way out.
> Moreover when i try to build the source with maven, build is successful but
> war files are not being generated. Have i missed something?
>
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unable-to-configure-SSL-by-self-signed-certificate-on-remote-IP-tp9213.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
PGP: 0x84DC9914

From daniel at passos.me  Wed Oct  1 07:01:22 2014
From: daniel at passos.me (Daniel Passos)
Date: Wed, 1 Oct 2014 08:01:22 -0300
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <CAEroY34dQeug-BR__CR+HDg1yau84=XFtGVatGbaWBtSRisH2A@mail.gmail.com>
References: <20140930231258.GB26685@abstractj.org>
	<9305F238-822C-447A-9612-FC34FBEA8015@gmail.com>
	<CAEroY34dQeug-BR__CR+HDg1yau84=XFtGVatGbaWBtSRisH2A@mail.gmail.com>
Message-ID: <CAKjsGbsnfp4Qsh-_JJOynTP9qr_bb2zoEEhpv++ROXJQOJh0AA@mail.gmail.com>

+1

On Wed, Oct 1, 2014 at 2:29 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> +1
>
> On Wed, Oct 1, 2014 at 1:18 AM, S?bastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> +1 sounds good !
>>
>> Envoy? de mon iPhone
>>
>> > Le 30 sept. 2014 ? 16:12, Bruno Oliveira <bruno at abstractj.org> a ?crit
>> :
>> >
>> > Good morning guys, I would like to set up a meeting Wednesday next week
>> > (same time of our official meeting) if possible.
>> >
>> > Only to stay up to date with what you have been doing/planning. I can
>> > dig into repositories but not into your brain :).
>> >
>> > Also, plan the next steps for security.
>> >
>> > --
>> >
>> > abstractj
>> > PGP: 0x84DC9914
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/35c53ef6/attachment.html 

From cvasilak at gmail.com  Wed Oct  1 07:03:24 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Wed, 1 Oct 2014 14:03:24 +0300
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <20140930231258.GB26685@abstractj.org>
References: <20140930231258.GB26685@abstractj.org>
Message-ID: <705AC606-C314-4E03-98D5-E2C5590A18D9@gmail.com>

+1

On Oct 1, 2014, at 2:12 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning guys, I would like to set up a meeting Wednesday next week
> (same time of our official meeting) if possible.
> 
> Only to stay up to date with what you have been doing/planning. I can
> dig into repositories but not into your brain :).
> 
> Also, plan the next steps for security.
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From corinnekrych at gmail.com  Wed Oct  1 07:05:06 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Wed, 1 Oct 2014 13:05:06 +0200
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <705AC606-C314-4E03-98D5-E2C5590A18D9@gmail.com>
References: <20140930231258.GB26685@abstractj.org>
	<705AC606-C314-4E03-98D5-E2C5590A18D9@gmail.com>
Message-ID: <FEFE89E0-6EFB-4FC5-8582-1F76545A8B88@gmail.com>

oki!
I?ll join
++
corinne
On 01 Oct 2014, at 13:03, Christos Vasilakis <cvasilak at gmail.com> wrote:

> +1
> 
> On Oct 1, 2014, at 2:12 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
> 
>> Good morning guys, I would like to set up a meeting Wednesday next week
>> (same time of our official meeting) if possible.
>> 
>> Only to stay up to date with what you have been doing/planning. I can
>> dig into repositories but not into your brain :).
>> 
>> Also, plan the next steps for security.
>> 
>> --
>> 
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From jbalunas at redhat.com  Wed Oct  1 08:31:18 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Wed, 1 Oct 2014 08:31:18 -0400
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <20140930231258.GB26685@abstractj.org>
References: <20140930231258.GB26685@abstractj.org>
Message-ID: <C7974766-21CA-4612-992F-B439C51B8ABE@redhat.com>

+1 I should be able to attend

On Sep 30, 2014, at 7:12 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning guys, I would like to set up a meeting Wednesday next week
> (same time of our official meeting) if possible.
> 
> Only to stay up to date with what you have been doing/planning. I can
> dig into repositories but not into your brain :).
> 
> Also, plan the next steps for security.
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/8d7efe54/attachment.bin 

From lholmqui at redhat.com  Wed Oct  1 09:39:20 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Wed, 1 Oct 2014 09:39:20 -0400
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <C7974766-21CA-4612-992F-B439C51B8ABE@redhat.com>
References: <20140930231258.GB26685@abstractj.org>
	<C7974766-21CA-4612-992F-B439C51B8ABE@redhat.com>
Message-ID: <2F0516A7-47C3-464E-A81B-BFC01BF4B303@redhat.com>

i?m in +1
On Oct 1, 2014, at 8:31 AM, Jay Balunas <jbalunas at redhat.com> wrote:

> +1 I should be able to attend
> 
> On Sep 30, 2014, at 7:12 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> 
>> Good morning guys, I would like to set up a meeting Wednesday next week
>> (same time of our official meeting) if possible.
>> 
>> Only to stay up to date with what you have been doing/planning. I can
>> dig into repositories but not into your brain :).
>> 
>> Also, plan the next steps for security.
>> 
>> --
>> 
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From jegranado at gmail.com  Wed Oct  1 12:00:08 2014
From: jegranado at gmail.com (jegranado)
Date: Wed, 1 Oct 2014 09:00:08 -0700 (PDT)
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
Message-ID: <1412179208281-9287.post@n5.nabble.com>

Hello all!

Do you have anything on the schedule for testing the Cordova plugin for
AeroGear Push to work when using Intel XDK?

Regards
Jeff



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Wed Oct  1 13:39:21 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 1 Oct 2014 19:39:21 +0200
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
In-Reply-To: <1412179208281-9287.post@n5.nabble.com>
References: <1412179208281-9287.post@n5.nabble.com>
Message-ID: <CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>

Hello Jeff!

I don't think anyone from our group has that on the agenda, at the moment
:-)
Are you a XDX user? Would you be interested in helping us regarding the
tests of our plugins?

Or are you already experiencing some issues with our plugins on Intel's XDX
?

Thanks,
Matthias

On Wed, Oct 1, 2014 at 6:00 PM, jegranado <jegranado at gmail.com> wrote:

> Hello all!
>
> Do you have anything on the schedule for testing the Cordova plugin for
> AeroGear Push to work when using Intel XDK?
>
> Regards
> Jeff
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287.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/20141001/e2f7572c/attachment-0001.html 

From jegranado at gmail.com  Wed Oct  1 13:49:37 2014
From: jegranado at gmail.com (jegranado)
Date: Wed, 1 Oct 2014 10:49:37 -0700 (PDT)
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
In-Reply-To: <CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>
References: <1412179208281-9287.post@n5.nabble.com>
	<CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>
Message-ID: <1412185777867-9289.post@n5.nabble.com>

Hi Matthias, thank your the very fast response!

I'm creating a small app and choose XDK 'cause it seems to be a very
interesting tool to rapid, multiplatform developments, and choose AeroGear
Push 'cause I wanted to try it!

Until now I've only tried the Push plugin, so I don't know about the others.

Sure I can test the plugins!
Let me just get a bit more used on the platform, and I can try to pinpoint
where the build failed.

I've asked for help on debugging the build with the XDK guys and as soon as
I get something on response I'll try to figure out and put the info back
here.

Please, let me know if you or someone in the group have already tried the
plugin with XDK and if it worked! (:

Regards,
Jeff



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287p9289.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From daniel at passos.me  Wed Oct  1 14:09:09 2014
From: daniel at passos.me (Daniel Passos)
Date: Wed, 1 Oct 2014 15:09:09 -0300
Subject: [aerogear-dev] Nice GCM improvements
Message-ID: <CAKjsGbuN5yR8=YaXdimoChvdNBiPEkTFDO8-XMB2S8JPsdcs8g@mail.gmail.com>

Nice video to help us in future features to UPS =>
https://www.youtube.com/watch?v=aJNzuxhZSxQ

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

From matzew at apache.org  Wed Oct  1 14:23:38 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 1 Oct 2014 20:23:38 +0200
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
In-Reply-To: <1412185777867-9289.post@n5.nabble.com>
References: <1412179208281-9287.post@n5.nabble.com>
	<CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>
	<1412185777867-9289.post@n5.nabble.com>
Message-ID: <CAAg5f2QuzQ+AzykVVwG7aSaULK3TMCDvJV0ygCUSsaOq0XDw7g@mail.gmail.com>

On Wednesday, October 1, 2014, jegranado <jegranado at gmail.com> wrote:

> Hi Matthias, thank your the very fast response!
>
> I'm creating a small app and choose XDK 'cause it seems to be a very
> interesting tool to rapid, multiplatform developments, and choose AeroGear
> Push 'cause I wanted to try it!
>
> Until now I've only tried the Push plugin, so I don't know about the
> others.



does our push plugin work with XDK?


>
> Sure I can test the plugins!
> Let me just get a bit more used on the platform, and I can try to pinpoint
> where the build failed.
>
> I've asked for help on debugging the build with the XDK guys and as soon as
> I get something on response I'll try to figure out and put the info back
> here.
>
> Please, let me know if you or someone in the group have already tried the
> plugin with XDK and if it worked! (:
>
> Regards,
> Jeff
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287p9289.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/20141001/91046a55/attachment.html 

From jegranado at gmail.com  Wed Oct  1 15:20:05 2014
From: jegranado at gmail.com (jegranado)
Date: Wed, 1 Oct 2014 12:20:05 -0700 (PDT)
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
In-Reply-To: <CAAg5f2QuzQ+AzykVVwG7aSaULK3TMCDvJV0ygCUSsaOq0XDw7g@mail.gmail.com>
References: <1412179208281-9287.post@n5.nabble.com>
	<CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>
	<1412185777867-9289.post@n5.nabble.com>
	<CAAg5f2QuzQ+AzykVVwG7aSaULK3TMCDvJV0ygCUSsaOq0XDw7g@mail.gmail.com>
Message-ID: <1412191205336-9292.post@n5.nabble.com>

in fact, "does our push plugin work with XDK?" is my real question.

Since they support the plugins that are available at plugins.cordova.io, and
AeroGear Push does, I believe that it should work flawlessly.



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287p9292.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Wed Oct  1 15:30:27 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 1 Oct 2014 21:30:27 +0200
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
In-Reply-To: <1412191205336-9292.post@n5.nabble.com>
References: <1412179208281-9287.post@n5.nabble.com>
	<CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>
	<1412185777867-9289.post@n5.nabble.com>
	<CAAg5f2QuzQ+AzykVVwG7aSaULK3TMCDvJV0ygCUSsaOq0XDw7g@mail.gmail.com>
	<1412191205336-9292.post@n5.nabble.com>
Message-ID: <CAAg5f2QxydDLDO070Muw_0iOKX017amfw2+A696VM=0KeA-ihQ@mail.gmail.com>

On Wednesday, October 1, 2014, jegranado <jegranado at gmail.com> wrote:

> in fact, "does our push plugin work with XDK?" is my real question.


:-)
ok, I miss understood, sorry!


>
> Since they support the plugins that are available at plugins.cordova.io,
> and
> AeroGear Push does, I believe that it should work flawlessly.


would be great to know. if you feel like contributing, we would appreciate
if you give it a shot!

thx,
matthias


>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287p9292.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/20141001/982c881b/attachment.html 

From bruno at abstractj.org  Wed Oct  1 16:52:11 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 01 Oct 2014 20:52:11 +0000
Subject: [aerogear-dev] Invitation: (No Subject) @ Wed Oct 8,
	2014 7am - 8am (Bruno Oliveira)
Message-ID: <001a11c344ca82cbba050462ac18@google.com>

You have been invited to the following event.

Title: (No Subject)
When: Wed Oct 8, 2014 7am - 8am Pacific Time
Where: IRC or maybe hangouts
Video call: https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno  
<https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno?hceid=YnJ1bm9AYWJzdHJhY3RqLm9yZw.tqg1fq3258kkuhuc4o0evpbfss>
Calendar: Bruno Oliveira
Who:
     * Bruno Oliveira - organizer
     * aerogear-dev at lists.jboss.org

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en

Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account  
aerogear-dev at lists.jboss.org because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/d056ef1c/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1048 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/d056ef1c/attachment-0002.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 1076 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/d056ef1c/attachment-0003.bin 

From bruno at abstractj.org  Wed Oct  1 16:52:27 2014
From: bruno at abstractj.org (bruno at abstractj.org)
Date: Wed, 01 Oct 2014 20:52:27 +0000
Subject: [aerogear-dev] Updated Invitation: Security Meeting @ Wed Oct 8,
 2014 7am - 8am (Bruno Oliveira)
Message-ID: <089e013d1d547a57f2050462ad98@google.com>

This event has been changed.

Title: Security Meeting (changed)
When: Wed Oct 8, 2014 7am - 8am Pacific Time
Where: IRC or maybe hangouts
Video call: https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno  
<https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno?hceid=YnJ1bm9AYWJzdHJhY3RqLm9yZw.tqg1fq3258kkuhuc4o0evpbfss>
Calendar: Bruno Oliveira
Who:
     * Bruno Oliveira - organizer
     * aerogear-dev at lists.jboss.org

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en

Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account  
aerogear-dev at lists.jboss.org because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/76aaeff2/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1064 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/76aaeff2/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 1092 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141001/76aaeff2/attachment-0001.bin 

From bruno at abstractj.org  Wed Oct  1 16:56:00 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 1 Oct 2014 13:56:00 -0700
Subject: [aerogear-dev] Security meeting next week?
In-Reply-To: <C7974766-21CA-4612-992F-B439C51B8ABE@redhat.com>
References: <20140930231258.GB26685@abstractj.org>
	<C7974766-21CA-4612-992F-B439C51B8ABE@redhat.com>
Message-ID: <20141001205600.GA37513@abstractj.org>

Thank you very much guys, I sent an invitation to the mailing
list. Feel free to join if you want to:

This is the clap for the meeting: http://oksoclap.com/p/b6eJqTG5ia

On 2014-10-01, Jay Balunas wrote:
> +1 I should be able to attend
>
> On Sep 30, 2014, at 7:12 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Good morning guys, I would like to set up a meeting Wednesday next week
> > (same time of our official meeting) if possible.
> >
> > Only to stay up to date with what you have been doing/planning. I can
> > dig into repositories but not into your brain :).
> >
> > Also, plan the next steps for security.
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



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


--

abstractj
PGP: 0x84DC9914

From lukas.fryc at gmail.com  Thu Oct  2 02:15:20 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 2 Oct 2014 08:15:20 +0200
Subject: [aerogear-dev] Invitation: (No Subject) @ Wed Oct 8,
 2014 7am - 8am (Bruno Oliveira)
In-Reply-To: <001a11c344ca82cbba050462ac18@google.com>
References: <001a11c344ca82cbba050462ac18@google.com>
Message-ID: <CAEroY35959G05wm14LUiTzyhKnk+iLnP2pQaGb2MpjX6hpxKbg@mail.gmail.com>

Hey Bruno,

it seems I can't simply join the meeting:

Google Calendar invitations cannot be forwarded via email. This event
belongs to aerogear-dev at lists.jboss.org and you are logged in as
lukas at fryc.eu. Please ask the meeting organizer to add you to the event
from Google Calendar.

Could you please add me (and other people that were interested)?

Or maybe opening/sharing the meeting to public would help (not sure Google
Calendar supports that).

~ Lukas


On Wed, Oct 1, 2014 at 10:52 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> more details ?
> <https://www.google.com/calendar/event?action=VIEW&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
> (No Subject)
> *When*
> Wed Oct 8, 2014 7am ? 8am Pacific Time
> *Where*
> IRC or maybe hangouts (map
> <https://maps.google.com/maps?q=IRC+or+maybe+hangouts&hl=en>)
> *Video call*
> https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno
> <https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno?hceid=YnJ1bm9AYWJzdHJhY3RqLm9yZw.tqg1fq3258kkuhuc4o0evpbfss>
> *Calendar*
> Bruno Oliveira
> *Who*
> ?
> Bruno Oliveira - organizer
> ?
> aerogear-dev at lists.jboss.org
>
> Going?   *Yes
> <https://www.google.com/calendar/event?action=RESPOND&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&rst=1&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
> - Maybe
> <https://www.google.com/calendar/event?action=RESPOND&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&rst=3&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
> - No
> <https://www.google.com/calendar/event?action=RESPOND&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&rst=2&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>*
>     more options ?
> <https://www.google.com/calendar/event?action=VIEW&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
>
> Invitation from Google Calendar <https://www.google.com/calendar/>
>
> You are receiving this courtesy email at the account
> aerogear-dev at lists.jboss.org because you are an attendee of this event.
>
> To stop receiving future notifications for this event, decline this event.
> Alternatively you can sign up for a Google account at
> https://www.google.com/calendar/ and control your notification settings
> for your entire calendar.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141002/2def442f/attachment-0001.html 

From matzew at apache.org  Thu Oct  2 04:50:14 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 2 Oct 2014 10:50:14 +0200
Subject: [aerogear-dev] Windows Client Push SDK
Message-ID: <CAAg5f2RAysk=ckbiaCTBSfYA4c0rOb+tPhpAqPS+gn+TrfPUXQ@mail.gmail.com>

Hello,

Erik was/is working on Windows Push support for UPS. Some changes have been
pushed to the MASTER branch of UPS (1.1.0-SNAPSHOT)

As of now his client SDK is also part of the AeroGear organization on
Github.

https://github.com/aerogear/aerogear-windows-push/

Cheers,
Matthias

-- 
Matthias Wessendorf

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

From corinnekrych at gmail.com  Fri Oct  3 11:27:19 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 3 Oct 2014 17:27:19 +0200
Subject: [aerogear-dev] iOS meeting
In-Reply-To: <CAKVvow_DP-JuO7X64RDKew-Evb0+-AsKkqGDj9V3x+w8fPD2vA@mail.gmail.com>
References: <731050CF-DEDB-4A4A-B835-1EC606CD35B1@gmail.com>
	<CAKVvow_DP-JuO7X64RDKew-Evb0+-AsKkqGDj9V3x+w8fPD2vA@mail.gmail.com>
Message-ID: <7F5C0D31-D3E6-4210-91C3-56074D5CE5A9@gmail.com>

Hello,

Time for another iOS meeting, main topic will be about 2.0 to be released next week. 
Meeting will be Tuesday 7 October at 2pm (CEST - UTC + 2hours)

Agenda is under progress and can be found:
http://oksoclap.com/p/aerogear_ios_meeting_7thOctober2014

++
Corinne

On 16 Sep 2014, at 14:18, Christos Vasilakis <cvasilak at gmail.com> wrote:

> fyi,
> 
> meeting minutes:
> 
> <jbott>	 Meeting ended Tue Sep 16 12:04:44 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-09-16-12.00.html
> <jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.txt
> <jbott>	 Log:               http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.log.html
> 
> 
> On Tue, Sep 9, 2014 at 11:51 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
> Hello Swifter and iOS lovers,
> 
> 
> Here is the proposed agenda of our next meeting which will take place Tuesday 16 September at 2pm (CEST - UTC + 2hours)
> soclap.com/p/aerogear_ios_meeting_11sept2014
> 
> Feel free to add topics to it and join us if you want to discuss with us next 2.0 iOS release.
> 
> ++
> Corinne
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From jegranado at gmail.com  Fri Oct  3 16:16:11 2014
From: jegranado at gmail.com (jegranado)
Date: Fri, 3 Oct 2014 13:16:11 -0700 (PDT)
Subject: [aerogear-dev] Intel XDK - Cordova plugin integration
In-Reply-To: <CAAg5f2QxydDLDO070Muw_0iOKX017amfw2+A696VM=0KeA-ihQ@mail.gmail.com>
References: <1412179208281-9287.post@n5.nabble.com>
	<CAAg5f2QfCEnPxv5H=d0Fkz-ncHivnzmthN7RJ+OyA5zmVAhP=w@mail.gmail.com>
	<1412185777867-9289.post@n5.nabble.com>
	<CAAg5f2QuzQ+AzykVVwG7aSaULK3TMCDvJV0ygCUSsaOq0XDw7g@mail.gmail.com>
	<1412191205336-9292.post@n5.nabble.com>
	<CAAg5f2QxydDLDO070Muw_0iOKX017amfw2+A696VM=0KeA-ihQ@mail.gmail.com>
Message-ID: <1412367371256-9300.post@n5.nabble.com>

Hello, Matthias!I'm glad to say that it *works*!In the end, XDK build servers
were down and thats why I didn't got it working on the first try.Just need
to make sure that you are using* Cordova >=3.4*, and everything should run
great!!It's never late to say thank you for the team's awesome work on the
whole AeroGear environment!Regards,Jeff



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Intel-XDK-Cordova-plugin-integration-tp9287p9300.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/20141003/81fb3d53/attachment.html 

From vivek.pandey at pinelabs.com  Mon Oct  6 01:40:38 2014
From: vivek.pandey at pinelabs.com (Vivek Pandey)
Date: Mon, 6 Oct 2014 11:10:38 +0530
Subject: [aerogear-dev] Error while upgrading to UPS 1.0.1
Message-ID: <001f01cfe128$0f50aac0$2df20040$@pinelabs.com>

UPS team,

 

I was trying to upgrade to UPS 1.0.0 to UPS 1.0.1. When I started jboss
after upgrading the wars, I found following errors in log

 

11:00:06,999 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/auth]]
(MSC service thread 1-4) Servlet /auth threw load() exception:
java.lang.IllegalArgumentException: Can not set boolean field
org.keycloak.models.jpa.entities.RealmEntity.eventsEnabled to null value

        at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeF
ieldAccessorImpl.java:164) [rt.jar:1.7.0_51]

 

It seems that I missed some database migration script. Can you point me to
that script?

 

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/20141006/56635c49/attachment.html 

From daniel.bevenius at gmail.com  Mon Oct  6 02:56:49 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 6 Oct 2014 08:56:49 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3G=PfPWMq=eL_9eBK4nU7H1==b2fUgDZBU=86xFqFUv5Q@mail.gmail.com>

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

From matzew at apache.org  Mon Oct  6 04:41:13 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 6 Oct 2014 10:41:13 +0200
Subject: [aerogear-dev] Error while upgrading to UPS 1.0.1
In-Reply-To: <001f01cfe128$0f50aac0$2df20040$@pinelabs.com>
References: <001f01cfe128$0f50aac0$2df20040$@pinelabs.com>
Message-ID: <CAAg5f2QiahZq+gQp364NEn6W7KTZgmb0urNd24awBVhWghyUAg@mail.gmail.com>

Hello Vivek,

looks like a database migration problem from our Keycloak SSO layer. I will
follow up with them.

That said, sounds like we may also have some higher priority for an export
of the device metadata (and perhaps apps/variants), to allow an import on
newer versions

-Matthias

On Mon, Oct 6, 2014 at 7:40 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
wrote:

> UPS team,
>
>
>
> I was trying to upgrade to UPS 1.0.0 to UPS 1.0.1. When I started jboss
> after upgrading the wars, I found following errors in log
>
>
>
> 11:00:06,999 ERROR
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/auth]]
> (MSC service thread 1-4) Servlet /auth threw load() exception:
> java.lang.IllegalArgumentException: Can not set boolean field
> org.keycloak.models.jpa.entities.RealmEntity.eventsEnabled to null value
>
>         at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
> [rt.jar:1.7.0_51]
>
>
>
> It seems that I missed some database migration script. Can you point me to
> that script?
>
>
>
> Thanks,
>
> Vivek
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Mon Oct  6 05:34:20 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 6 Oct 2014 11:34:20 +0200
Subject: [aerogear-dev] Error while upgrading to UPS 1.0.1
In-Reply-To: <CAAg5f2QiahZq+gQp364NEn6W7KTZgmb0urNd24awBVhWghyUAg@mail.gmail.com>
References: <001f01cfe128$0f50aac0$2df20040$@pinelabs.com>
	<CAAg5f2QiahZq+gQp364NEn6W7KTZgmb0urNd24awBVhWghyUAg@mail.gmail.com>
Message-ID: <CAD_dpu23L2m_vKb8_5XtSmdjX5-hP5xBj9tdX4KVrMxD-K9u-g@mail.gmail.com>

On Mon, Oct 6, 2014 at 10:41 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello Vivek,
>
> looks like a database migration problem from our Keycloak SSO layer. I
> will follow up with them.
>
> That said, sounds like we may also have some higher priority for an export
> of the device metadata (and perhaps apps/variants), to allow an import on
> newer versions
>
+1 and indeed maybe consider apps/variants as well
We have a ticket for that https://issues.jboss.org/browse/AGPUSH-978

@vivek In the mean time, I will ping the Keycloak team to see if they have
some kind of migration script available or tips.


>
> -Matthias
>
> On Mon, Oct 6, 2014 at 7:40 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
> wrote:
>
>> UPS team,
>>
>>
>>
>> I was trying to upgrade to UPS 1.0.0 to UPS 1.0.1. When I started jboss
>> after upgrading the wars, I found following errors in log
>>
>>
>>
>> 11:00:06,999 ERROR
>> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/auth]]
>> (MSC service thread 1-4) Servlet /auth threw load() exception:
>> java.lang.IllegalArgumentException: Can not set boolean field
>> org.keycloak.models.jpa.entities.RealmEntity.eventsEnabled to null value
>>
>>         at
>> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
>> [rt.jar:1.7.0_51]
>>
>>
>>
>> It seems that I missed some database migration script. Can you point me
>> to that script?
>>
>>
>>
>> Thanks,
>>
>> Vivek
>>
>> ------------------------------
>> This message may contain privileged and confidential information and is
>> solely for the use of intended recipient. The views expressed in this email
>> are those of the sender and not of Pine Labs. The recipient should check
>> this email and attachments for the presence of viruses / malwares etc. Pine
>> Labs accepts no liability for any damage caused by any virus transmitted by
>> this email. Pine Labs may monitor and record all emails.
>> ------------------------------
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/11fd1fc5/attachment-0001.html 

From corinnekrych at gmail.com  Mon Oct  6 05:45:27 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 6 Oct 2014 11:45:27 +0200
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
Message-ID: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>

Hello Guys,

Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a backend to demo Keycloak too.

Main idea is that for OAuth2 we demo external providers: Google, Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it with a web-app too. So that?s once the photo get uploaded you can view on desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js adapter). See backend demo [1]

@summers, passos: It would be nice to have an Android similar demo, wdyt?
@lfryc @lholmquist should we use keyclaok.js only or is there a way to use ag.js? btw, your review is welcome on the js-angular part.

++
Corinne 

[1] https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md

PS: do you like kittens?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/6872390d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Shoot_web-app2.png
Type: image/png
Size: 111801 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/6872390d/attachment-0001.png 

From lholmqui at redhat.com  Mon Oct  6 08:47:04 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 6 Oct 2014 08:47:04 -0400
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
Message-ID: <F03A1FAC-B835-4FEC-8A5D-D1E8B675B7AE@redhat.com>


On Oct 6, 2014, at 5:45 AM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello Guys,
> 
> Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a backend to demo Keycloak too.
> 
> Main idea is that for OAuth2 we demo external providers: Google, Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it with a web-app too. So that?s once the photo get uploaded you can view on desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js adapter). See backend demo [1]
> 
> @summers, passos: It would be nice to have an Android similar demo, wdyt?
> @lfryc @lholmquist should we use keyclaok.js only or is there a way to use ag.js? btw, your review is welcome on the js-angular part.
I think you?ll need to stick with the keycloack.js for interacting with keycloack since it they do not support the implicit grant OAuth2 flow.  which is a bummer

> 
> ++
> Corinne 
> 
> [1] https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
> 
> PS: do you like kittens?
> <Shoot_web-app2.png>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From lholmqui at redhat.com  Mon Oct  6 08:47:33 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 6 Oct 2014 08:47:33 -0400
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
Message-ID: <8B1BADE1-5C23-4D03-B0D2-23EE8A4E7307@redhat.com>


On Oct 6, 2014, at 5:45 AM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello Guys,
> 
> Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a backend to demo Keycloak too.
> 
> Main idea is that for OAuth2 we demo external providers: Google, Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it with a web-app too. So that?s once the photo get uploaded you can view on desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js adapter). See backend demo [1]
> 
> @summers, passos: It would be nice to have an Android similar demo, wdyt?
> @lfryc @lholmquist should we use keyclaok.js only or is there a way to use ag.js? btw, your review is welcome on the js-angular part.
> 
> ++
> Corinne 
> 
> [1] https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
> 
> PS: do you like kittens?

also, i do like kittens

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/62214aef/attachment.html 

From supittma at redhat.com  Mon Oct  6 09:27:11 2014
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 06 Oct 2014 09:27:11 -0400
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
Message-ID: <543298AF.7060201@redhat.com>

On 10/06/2014 05:45 AM, Corinne Krych wrote:
> Hello Guys,
>
> Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we 
> worked on an OAuth2 demo. We actually reuse Shoot app and extend it 
> with a backend to demo Keycloak too.
>
> Main idea is that for OAuth2 we demo external providers: Google, 
> Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced 
> it with a web-app too. So that?s once the photo get uploaded you can 
> view on desktop web-app. It?s nice to demo the 2 keyclaok adapters 
> (wildfly and js adapter). See backend demo [1]
>
> @summers, passos: It would be nice to have an Android similar demo, wdyt?
Shouldn't be a problem :)  More demos are always fun and will be a good 
thing to give the 2.0 code a in use test.
> @lfryc @lholmquist should we use keyclaok.js only or is there a way to 
> use ag.js? btw, your review is welcome on the js-angular part.
>
> ++
> Corinne
>
> [1] 
> https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
>
> PS: do you like kittens?
>
>
> _______________________________________________
> 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/20141006/c76db266/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 111801 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/c76db266/attachment-0001.png 

From scm.blanc at gmail.com  Mon Oct  6 09:42:02 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 6 Oct 2014 15:42:02 +0200
Subject: [aerogear-dev] Error while upgrading to UPS 1.0.1
In-Reply-To: <CAD_dpu23L2m_vKb8_5XtSmdjX5-hP5xBj9tdX4KVrMxD-K9u-g@mail.gmail.com>
References: <001f01cfe128$0f50aac0$2df20040$@pinelabs.com>
	<CAAg5f2QiahZq+gQp364NEn6W7KTZgmb0urNd24awBVhWghyUAg@mail.gmail.com>
	<CAD_dpu23L2m_vKb8_5XtSmdjX5-hP5xBj9tdX4KVrMxD-K9u-g@mail.gmail.com>
Message-ID: <CAD_dpu1JBkL9VN2GEpuxTO5Mtp-+Tk+nv0=BWGodhgVbcRW+BQ@mail.gmail.com>

Hi Vivek !
The KeyCloak jsut gave me some directions for the migration, I copy paste
it here :

Make sure Keycloak 1.0.0.RC1 is not running and run:

 # bin/standalone.sh -Dkeycloak.migration.action=export
-Dkeycloak.migration.provider=singleFile
-Dkeycloak.migration.file=<ADD A NAME FOR THE EXPORT FILE>

Then you need to manually edit the exported file:

1. Rename "auditEnabled" to "eventsEnabled"
2. Rename "auditExpiration" to "eventsExpiration"
3. Rename "auditListeners" to "eventsListeners"
4. Under "master" realm to all applications that ends with "-realm"
add roles "view-events" and "manage-events" (you don't need to specify
an id)
5. To "admin" composite role in master realm add "view-events" and
"manage-events"
6. For each additional realm to "realm-management" application add
roles "view-events" and "manage-events"
7. To "realm-admin" composite role in other realms add "view-events"
and "manage-events"

Steps 1-3 are required, otherwise the import will fail. If steps 4-7
are not done Keycloak will throw a NPE if you try to access events log
through the admin console, you can also do these steps afterwards
through the admin console.

Before starting Keycloak 1.0.1.Final clear the database, then run:

 # bin/standalone.sh -Dkeycloak.migration.action=import
-Dkeycloak.migration.provider=singleFile
-Dkeycloak.migration.file=<PATH TO ABOVE EXPORT FILE>


Please let us know if that helps.


Sebi


On Mon, Oct 6, 2014 at 11:34 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> On Mon, Oct 6, 2014 at 10:41 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hello Vivek,
>>
>> looks like a database migration problem from our Keycloak SSO layer. I
>> will follow up with them.
>>
>> That said, sounds like we may also have some higher priority for an
>> export of the device metadata (and perhaps apps/variants), to allow an
>> import on newer versions
>>
> +1 and indeed maybe consider apps/variants as well
> We have a ticket for that https://issues.jboss.org/browse/AGPUSH-978
>
> @vivek In the mean time, I will ping the Keycloak team to see if they have
> some kind of migration script available or tips.
>
>
>>
>> -Matthias
>>
>> On Mon, Oct 6, 2014 at 7:40 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
>> wrote:
>>
>>> UPS team,
>>>
>>>
>>>
>>> I was trying to upgrade to UPS 1.0.0 to UPS 1.0.1. When I started jboss
>>> after upgrading the wars, I found following errors in log
>>>
>>>
>>>
>>> 11:00:06,999 ERROR
>>> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/auth]]
>>> (MSC service thread 1-4) Servlet /auth threw load() exception:
>>> java.lang.IllegalArgumentException: Can not set boolean field
>>> org.keycloak.models.jpa.entities.RealmEntity.eventsEnabled to null value
>>>
>>>         at
>>> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
>>> [rt.jar:1.7.0_51]
>>>
>>>
>>>
>>> It seems that I missed some database migration script. Can you point me
>>> to that script?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Vivek
>>>
>>> ------------------------------
>>> This message may contain privileged and confidential information and is
>>> solely for the use of intended recipient. The views expressed in this email
>>> are those of the sender and not of Pine Labs. The recipient should check
>>> this email and attachments for the presence of viruses / malwares etc. Pine
>>> Labs accepts no liability for any damage caused by any virus transmitted by
>>> this email. Pine Labs may monitor and record all emails.
>>> ------------------------------
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/810e8894/attachment.html 

From cvasilak at gmail.com  Mon Oct  6 10:09:08 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 6 Oct 2014 17:09:08 +0300
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3G=PfPWMq=eL_9eBK4nU7H1==b2fUgDZBU=86xFqFUv5Q@mail.gmail.com>
References: <CAFJm-3G=PfPWMq=eL_9eBK4nU7H1==b2fUgDZBU=86xFqFUv5Q@mail.gmail.com>
Message-ID: <DCFA63C6-BC92-44DD-A924-0F2CAEAABA5C@gmail.com>

fyi,

meeting minutes:

<jbott>	 Meeting ended Mon Oct  6 14:07:44 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-10-06-14.00.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-06-14.00.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-06-14.00.log.html


On Oct 6, 2014, at 9:56 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/51d4229a/attachment.html 

From edewit at redhat.com  Mon Oct  6 11:48:53 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 6 Oct 2014 17:48:53 +0200
Subject: [aerogear-dev] database migration
Message-ID: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>

Hi,

Now that we have 2 versions out of the door, when we change stuff we need an easy upgrade path. Not only for the API but also for the database. Because we support a couple of them having something of a process would help.

I?ve have used liquibase in the past. You write ?change sets? in yaml, json or if you must in xml, it will create a migration table in the database and execute the changes needed to bring it up to date or you can create a sql script that will do the same. Cool thing about this approach is that it?s independent of the database

http://www.liquibase.org

Another tool I?ve heard about, but also promising is Flyway. It?s supports writing migrations in sql and java comes with it?s own java api. Basically the same idea with regards to this migration table, but here you need to specify your own sql scripts. Or you can write migrations in java where having special named java class gets executed to update/migrate the data.

http://flywaydb.org

WDYT?

Cheers,
	Erik Jan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/09383f8d/attachment.html 

From stian at redhat.com  Mon Oct  6 13:24:19 2014
From: stian at redhat.com (Stian Thorgersen)
Date: Mon, 6 Oct 2014 13:24:19 -0400 (EDT)
Subject: [aerogear-dev] database migration
In-Reply-To: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
Message-ID: <631364897.62320848.1412616259191.JavaMail.zimbra@redhat.com>

We're looking at this for Keycloak atm as well, and those where the two that stood out at first glance. I haven't looked in depth or tried them out yet though.

----- Original Message -----
> From: "Erik Jan de Wit" <edewit at redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Monday, 6 October, 2014 5:48:53 PM
> Subject: [aerogear-dev] database migration
> 
> Hi,
> 
> Now that we have 2 versions out of the door, when we change stuff we need an
> easy upgrade path. Not only for the API but also for the database. Because
> we support a couple of them having something of a process would help.
> 
> I?ve have used liquibase in the past. You write ?change sets? in yaml, json
> or if you must in xml, it will create a migration table in the database and
> execute the changes needed to bring it up to date or you can create a sql
> script that will do the same. Cool thing about this approach is that it?s
> independent of the database
> 
> http://www.liquibase.org
> 
> Another tool I?ve heard about, but also promising is Flyway. It?s supports
> writing migrations in sql and java comes with it?s own java api. Basically
> the same idea with regards to this migration table, but here you need to
> specify your own sql scripts. Or you can write migrations in java where
> having special named java class gets executed to update/migrate the data.
> 
> http://flywaydb.org
> 
> WDYT?
> 
> Cheers,
> Erik Jan
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From daniel at passos.me  Mon Oct  6 17:38:25 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 6 Oct 2014 18:38:25 -0300
Subject: [aerogear-dev] iOS meeting
In-Reply-To: <7F5C0D31-D3E6-4210-91C3-56074D5CE5A9@gmail.com>
References: <731050CF-DEDB-4A4A-B835-1EC606CD35B1@gmail.com>
	<CAKVvow_DP-JuO7X64RDKew-Evb0+-AsKkqGDj9V3x+w8fPD2vA@mail.gmail.com>
	<7F5C0D31-D3E6-4210-91C3-56074D5CE5A9@gmail.com>
Message-ID: <CAKjsGbvjNZtqSow3RcfCLakesFOOPoEBwPrz01hC-PtcqtJt4w@mail.gmail.com>

Hi iOS team,

I'll join on that tomorrow, but I'd like to ask you to use the same time of
our official meeting, because it's too early for me (9AM) and for Summers
(8AM). Wdyt?

-- Passos

On Fri, Oct 3, 2014 at 12:27 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Hello,
>
> Time for another iOS meeting, main topic will be about 2.0 to be released
> next week.
> Meeting will be Tuesday 7 October at 2pm (CEST - UTC + 2hours)
>
> Agenda is under progress and can be found:
> http://oksoclap.com/p/aerogear_ios_meeting_7thOctober2014
>
> ++
> Corinne
>
> On 16 Sep 2014, at 14:18, Christos Vasilakis <cvasilak at gmail.com> wrote:
>
> > fyi,
> >
> > meeting minutes:
> >
> > <jbott>        Meeting ended Tue Sep 16 12:04:44 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-09-16-12.00.html
> > <jbott>        Minutes (text):
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.txt
> > <jbott>        Log:
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.log.html
> >
> >
> > On Tue, Sep 9, 2014 at 11:51 AM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
> > Hello Swifter and iOS lovers,
> >
> >
> > Here is the proposed agenda of our next meeting which will take place
> Tuesday 16 September at 2pm (CEST - UTC + 2hours)
> > soclap.com/p/aerogear_ios_meeting_11sept2014
> >
> > Feel free to add topics to it and join us if you want to discuss with us
> next 2.0 iOS release.
> >
> > ++
> > Corinne
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/5c6c499a/attachment-0001.html 

From daniel at passos.me  Mon Oct  6 18:00:45 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 6 Oct 2014 19:00:45 -0300
Subject: [aerogear-dev] database migration
In-Reply-To: <631364897.62320848.1412616259191.JavaMail.zimbra@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<631364897.62320848.1412616259191.JavaMail.zimbra@redhat.com>
Message-ID: <CAKjsGbucBgAfCgGynJn6iWH0K3SeXHWMjy-5uY4cs9_t45Tu0A@mail.gmail.com>

I've never played with liquibase. but +1 for start using migrations

-- Passos

On Mon, Oct 6, 2014 at 2:24 PM, Stian Thorgersen <stian at redhat.com> wrote:

> We're looking at this for Keycloak atm as well, and those where the two
> that stood out at first glance. I haven't looked in depth or tried them out
> yet though.
>
> ----- Original Message -----
> > From: "Erik Jan de Wit" <edewit at redhat.com>
> > To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> > Sent: Monday, 6 October, 2014 5:48:53 PM
> > Subject: [aerogear-dev] database migration
> >
> > Hi,
> >
> > Now that we have 2 versions out of the door, when we change stuff we
> need an
> > easy upgrade path. Not only for the API but also for the database.
> Because
> > we support a couple of them having something of a process would help.
> >
> > I?ve have used liquibase in the past. You write ?change sets? in yaml,
> json
> > or if you must in xml, it will create a migration table in the database
> and
> > execute the changes needed to bring it up to date or you can create a sql
> > script that will do the same. Cool thing about this approach is that it?s
> > independent of the database
> >
> > http://www.liquibase.org
> >
> > Another tool I?ve heard about, but also promising is Flyway. It?s
> supports
> > writing migrations in sql and java comes with it?s own java api.
> Basically
> > the same idea with regards to this migration table, but here you need to
> > specify your own sql scripts. Or you can write migrations in java where
> > having special named java class gets executed to update/migrate the data.
> >
> > http://flywaydb.org
> >
> > WDYT?
> >
> > Cheers,
> > Erik Jan
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/d246a417/attachment.html 

From daniel at passos.me  Mon Oct  6 18:06:17 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 6 Oct 2014 19:06:17 -0300
Subject: [aerogear-dev] some cookbook recipes need some backend
In-Reply-To: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
References: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
Message-ID: <CAKjsGbtj+xtPECChrO8wbArkc8wDgxLnjNwXDM4G=rRf7P2xqg@mail.gmail.com>

Hey Corrine,

Sorry for my delay in replay that.

As we talked on IRC, Summers and I are trying to use always as possible an
endpoint on internet instead of create our own backend project to that.
But, +1 for that in cases we really need create one.

-- Passos


On Thu, Sep 18, 2014 at 12:30 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Hello Guys
>
> To complete our cookbook repositories: iOS, web, android and cordova
> (still under eric private repo), I?d like to have a
> aerogear-backend-cookbook. We already have some demos which requires
> backend. I?ve put them together in:
>
> https://github.com/corinnekrych/aerogear-backend-cookbook
>
> Each app has a separate build and is independent. For new I?ve put
> together:
> AeroDoc
> PushQuickstart (as submodules)
> Buddies
> ProductInventory (oauth2 keycloak) kind of helloWorld app, very simple
>
> Next addition, I?m thinking to do a Shoot?nShare file upload Server using
> Keycloak. So we can have a more complete demo of AeroGear OAuth2 and
> Keycloak.
>
> Thoughts?
>
> ++
> Corinne
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/50462f25/attachment.html 

From bruno at abstractj.org  Mon Oct  6 18:19:20 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 06 Oct 2014 15:19:20 -0700 (PDT)
Subject: [aerogear-dev] iOS meeting
In-Reply-To: <CAKjsGbvjNZtqSow3RcfCLakesFOOPoEBwPrz01hC-PtcqtJt4w@mail.gmail.com>
References: <CAKjsGbvjNZtqSow3RcfCLakesFOOPoEBwPrz01hC-PtcqtJt4w@mail.gmail.com>
Message-ID: <1412633959146.74ead688@Nodemailer>

Please!

?
Sent from Mailbox

On Mon, Oct 6, 2014 at 6:38 PM, Daniel Passos <daniel at passos.me> wrote:

> Hi iOS team,
> I'll join on that tomorrow, but I'd like to ask you to use the same time of
> our official meeting, because it's too early for me (9AM) and for Summers
> (8AM). Wdyt?
> -- Passos
> On Fri, Oct 3, 2014 at 12:27 PM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
>> Hello,
>>
>> Time for another iOS meeting, main topic will be about 2.0 to be released
>> next week.
>> Meeting will be Tuesday 7 October at 2pm (CEST - UTC + 2hours)
>>
>> Agenda is under progress and can be found:
>> http://oksoclap.com/p/aerogear_ios_meeting_7thOctober2014
>>
>> ++
>> Corinne
>>
>> On 16 Sep 2014, at 14:18, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>
>> > fyi,
>> >
>> > meeting minutes:
>> >
>> > <jbott>        Meeting ended Tue Sep 16 12:04:44 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-09-16-12.00.html
>> > <jbott>        Minutes (text):
>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.txt
>> > <jbott>        Log:
>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.log.html
>> >
>> >
>> > On Tue, Sep 9, 2014 at 11:51 AM, Corinne Krych <corinnekrych at gmail.com>
>> wrote:
>> > Hello Swifter and iOS lovers,
>> >
>> >
>> > Here is the proposed agenda of our next meeting which will take place
>> Tuesday 16 September at 2pm (CEST - UTC + 2hours)
>> > soclap.com/p/aerogear_ios_meeting_11sept2014
>> >
>> > Feel free to add topics to it and join us if you want to discuss with us
>> next 2.0 iOS release.
>> >
>> > ++
>> > Corinne
>> >
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/cbd5b0c9/attachment.html 

From bruno at abstractj.org  Mon Oct  6 18:40:07 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 06 Oct 2014 15:40:07 -0700 (PDT)
Subject: [aerogear-dev] Invitation: (No Subject) @ Wed Oct 8,
 2014 7am - 8am (Bruno Oliveira)
In-Reply-To: <CAEroY35959G05wm14LUiTzyhKnk+iLnP2pQaGb2MpjX6hpxKbg@mail.gmail.com>
References: <CAEroY35959G05wm14LUiTzyhKnk+iLnP2pQaGb2MpjX6hpxKbg@mail.gmail.com>
Message-ID: <1412635206386.86908c6c@Nodemailer>

I sent the invitation only as a reminder. I don't to spam the mailing list with calendar updates.

?
Sent from Mailbox

On Thu, Oct 2, 2014 at 3:15 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hey Bruno,
> it seems I can't simply join the meeting:
> Google Calendar invitations cannot be forwarded via email. This event
> belongs to aerogear-dev at lists.jboss.org and you are logged in as
> lukas at fryc.eu. Please ask the meeting organizer to add you to the event
> from Google Calendar.
> Could you please add me (and other people that were interested)?
> Or maybe opening/sharing the meeting to public would help (not sure Google
> Calendar supports that).
> ~ Lukas
> On Wed, Oct 1, 2014 at 10:52 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>> more details ?
>> <https://www.google.com/calendar/event?action=VIEW&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
>> (No Subject)
>> *When*
>> Wed Oct 8, 2014 7am ? 8am Pacific Time
>> *Where*
>> IRC or maybe hangouts (map
>> <https://maps.google.com/maps?q=IRC+or+maybe+hangouts&hl=en>)
>> *Video call*
>> https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno
>> <https://plus.google.com/hangouts/_/abstractj.org/aerogear-bruno?hceid=YnJ1bm9AYWJzdHJhY3RqLm9yZw.tqg1fq3258kkuhuc4o0evpbfss>
>> *Calendar*
>> Bruno Oliveira
>> *Who*
>> ?
>> Bruno Oliveira - organizer
>> ?
>> aerogear-dev at lists.jboss.org
>>
>> Going?   *Yes
>> <https://www.google.com/calendar/event?action=RESPOND&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&rst=1&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
>> - Maybe
>> <https://www.google.com/calendar/event?action=RESPOND&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&rst=3&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
>> - No
>> <https://www.google.com/calendar/event?action=RESPOND&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&rst=2&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>*
>>     more options ?
>> <https://www.google.com/calendar/event?action=VIEW&eid=dHFnMWZxMzI1OGtrdWh1YzRvMGV2cGJmc3MgYWVyb2dlYXItZGV2QGxpc3RzLmpib3NzLm9yZw&tok=MTkjYnJ1bm9AYWJzdHJhY3RqLm9yZ2RmOTNlN2QyNzI5NGU1Y2YxN2Q4MTc2YjM3ZWE3MmJjNTZiMWM4MTY&ctz=America/Los_Angeles&hl=en>
>>
>> Invitation from Google Calendar <https://www.google.com/calendar/>
>>
>> You are receiving this courtesy email at the account
>> aerogear-dev at lists.jboss.org because you are an attendee of this event.
>>
>> To stop receiving future notifications for this event, decline this event.
>> Alternatively you can sign up for a Google account at
>> https://www.google.com/calendar/ and control your notification settings
>> for your entire calendar.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141006/c93984ab/attachment-0001.html 

From corinnekrych at gmail.com  Mon Oct  6 18:42:35 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 7 Oct 2014 00:42:35 +0200
Subject: [aerogear-dev] iOS meeting
In-Reply-To: <1412633959146.74ead688@Nodemailer>
References: <CAKjsGbvjNZtqSow3RcfCLakesFOOPoEBwPrz01hC-PtcqtJt4w@mail.gmail.com>
	<1412633959146.74ead688@Nodemailer>
Message-ID: <CAL8vO=cwmJ=289YzTuGuyWMw3U_9eJ-wL6=93XovA4404Wp9jA@mail.gmail.com>

No worries let's target 4pm!

On Tuesday, October 7, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:

> Please!
> ?
> Sent from Mailbox <https://www.dropbox.com/mailbox>
>
>
> On Mon, Oct 6, 2014 at 6:38 PM, Daniel Passos <daniel at passos.me
> <javascript:_e(%7B%7D,'cvml','daniel at passos.me');>> wrote:
>
>>  Hi iOS team,
>>
>> I'll join on that tomorrow, but I'd like to ask you to use the same time
>> of our official meeting, because it's too early for me (9AM) and for
>> Summers (8AM). Wdyt?
>>
>> -- Passos
>>
>> On Fri, Oct 3, 2014 at 12:27 PM, Corinne Krych <corinnekrych at gmail.com
>> <javascript:_e(%7B%7D,'cvml','corinnekrych at gmail.com');>> wrote:
>>
>>> Hello,
>>>
>>> Time for another iOS meeting, main topic will be about 2.0 to be
>>> released next week.
>>> Meeting will be Tuesday 7 October at 2pm (CEST - UTC + 2hours)
>>>
>>> Agenda is under progress and can be found:
>>> http://oksoclap.com/p/aerogear_ios_meeting_7thOctober2014
>>>
>>> ++
>>> Corinne
>>>
>>> On 16 Sep 2014, at 14:18, Christos Vasilakis <cvasilak at gmail.com
>>> <javascript:_e(%7B%7D,'cvml','cvasilak at gmail.com');>> wrote:
>>>
>>> > fyi,
>>> >
>>> > meeting minutes:
>>> >
>>> > <jbott>        Meeting ended Tue Sep 16 12:04:44 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-09-16-12.00.html
>>> > <jbott>        Minutes (text):
>>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.txt
>>> > <jbott>        Log:
>>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-09-16-12.00.log.html
>>> >
>>> >
>>> > On Tue, Sep 9, 2014 at 11:51 AM, Corinne Krych <corinnekrych at gmail.com
>>> <javascript:_e(%7B%7D,'cvml','corinnekrych at gmail.com');>> wrote:
>>> > Hello Swifter and iOS lovers,
>>> >
>>> >
>>> > Here is the proposed agenda of our next meeting which will take place
>>> Tuesday 16 September at 2pm (CEST - UTC + 2hours)
>>> > soclap.com/p/aerogear_ios_meeting_11sept2014
>>> >
>>> > Feel free to add topics to it and join us if you want to discuss with
>>> us next 2.0 iOS release.
>>> >
>>> > ++
>>> > Corinne
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/cacf59cc/attachment.html 

From cvasilak at gmail.com  Tue Oct  7 02:32:48 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 7 Oct 2014 09:32:48 +0300
Subject: [aerogear-dev] database migration
In-Reply-To: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
Message-ID: <637559D1-DA24-43E7-889D-658CC52C1F3F@gmail.com>

sounds reasonable and if it eases the pain I am +1 on it.

let me know how can I help on it.


-
Christos

On Oct 6, 2014, at 6:48 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
> 
> Now that we have 2 versions out of the door, when we change stuff we need an easy upgrade path. Not only for the API but also for the database. Because we support a couple of them having something of a process would help.
> 
> I?ve have used liquibase in the past. You write ?change sets? in yaml, json or if you must in xml, it will create a migration table in the database and execute the changes needed to bring it up to date or you can create a sql script that will do the same. Cool thing about this approach is that it?s independent of the database
> 
> http://www.liquibase.org
> 
> Another tool I?ve heard about, but also promising is Flyway. It?s supports writing migrations in sql and java comes with it?s own java api. Basically the same idea with regards to this migration table, but here you need to specify your own sql scripts. Or you can write migrations in java where having special named java class gets executed to update/migrate the data.
> 
> http://flywaydb.org
> 
> WDYT?
> 
> Cheers,
> 	Erik Jan
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/7f03cd88/attachment.html 

From daniel.bevenius at gmail.com  Tue Oct  7 02:38:05 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 7 Oct 2014 08:38:05 +0200
Subject: [aerogear-dev] database migration
In-Reply-To: <637559D1-DA24-43E7-889D-658CC52C1F3F@gmail.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<637559D1-DA24-43E7-889D-658CC52C1F3F@gmail.com>
Message-ID: <CAFJm-3G6FZ88GD6bzNGWyqUCgX-qSwz2CWvCUxJpVyM_5C9t1A@mail.gmail.com>

+1 Sounds good to me.

On 7 October 2014 08:32, Christos Vasilakis <cvasilak at gmail.com> wrote:

> sounds reasonable and if it eases the pain I am +1 on it.
>
> let me know how can I help on it.
>
>
> -
> Christos
>
> On Oct 6, 2014, at 6:48 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>
> Hi,
>
> Now that we have 2 versions out of the door, when we change stuff we need
> an easy upgrade path. Not only for the API but also for the database.
> Because we support a couple of them having something of a process would
> help.
>
> I?ve have used liquibase in the past. You write ?change sets? in yaml,
> json or if you must in xml, it will create a migration table in the
> database and execute the changes needed to bring it up to date or you can
> create a sql script that will do the same. Cool thing about this approach
> is that it?s independent of the database
>
> http://www.liquibase.org
>
> Another tool I?ve heard about, but also promising is Flyway. It?s supports
> writing migrations in sql and java comes with it?s own java api. Basically
> the same idea with regards to this migration table, but here you need to
> specify your own sql scripts. Or you can write migrations in java where
> having special named java class gets executed to update/migrate the data.
>
> http://flywaydb.org
>
> WDYT?
>
> Cheers,
> Erik Jan
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/e770037a/attachment.html 

From matzew at apache.org  Tue Oct  7 03:27:45 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 7 Oct 2014 09:27:45 +0200
Subject: [aerogear-dev] database migration
In-Reply-To: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
Message-ID: <CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>

I have heard about FlywayDB, but from your email liquibase sounds like a
good idea!

Thanks for sharing, Erik!

On Mon, Oct 6, 2014 at 5:48 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> Now that we have 2 versions out of the door, when we change stuff we need
> an easy upgrade path. Not only for the API but also for the database.
> Because we support a couple of them having something of a process would
> help.
>
> I?ve have used liquibase in the past. You write ?change sets? in yaml,
> json or if you must in xml, it will create a migration table in the
> database and execute the changes needed to bring it up to date or you can
> create a sql script that will do the same. Cool thing about this approach
> is that it?s independent of the database
>
> http://www.liquibase.org
>
> Another tool I?ve heard about, but also promising is Flyway. It?s supports
> writing migrations in sql and java comes with it?s own java api. Basically
> the same idea with regards to this migration table, but here you need to
> specify your own sql scripts. Or you can write migrations in java where
> having special named java class gets executed to update/migrate the data.
>
> http://flywaydb.org
>
> WDYT?
>
> Cheers,
> Erik Jan
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Tue Oct  7 03:42:43 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 7 Oct 2014 09:42:43 +0200
Subject: [aerogear-dev] some cookbook recipes need some backend
In-Reply-To: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
References: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
Message-ID: <CAAg5f2T-32Oc=_aybohyak=yqY65iN23797C8uNs+R7HHAAQaw@mail.gmail.com>

On Thu, Sep 18, 2014 at 5:30 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Hello Guys
>
> To complete our cookbook repositories: iOS, web, android and cordova
> (still under eric private repo), I?d like to have a
> aerogear-backend-cookbook. We already have some demos which requires
> backend. I?ve put them together in:
>
> https://github.com/corinnekrych/aerogear-backend-cookbook
>
> Each app has a separate build and is independent. For new I?ve put
> together:
> AeroDoc
> PushQuickstart (as submodules)
> Buddies
> ProductInventory (oauth2 keycloak) kind of helloWorld app, very simple
>
> Next addition, I?m thinking to do a Shoot?nShare file upload Server using
> Keycloak. So we can have a more complete demo of AeroGear OAuth2 and
> Keycloak.
>

sounds great! especially to demo the connection between AG and KC.
The upload part should be pretty darn simple :)


>
> Thoughts?
>
> ++
> Corinne
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141007/a2bd497c/attachment-0001.html 

From stian at redhat.com  Tue Oct  7 03:57:13 2014
From: stian at redhat.com (Stian Thorgersen)
Date: Tue, 7 Oct 2014 03:57:13 -0400 (EDT)
Subject: [aerogear-dev] database migration
In-Reply-To: <CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
Message-ID: <1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>

I've been playing with Liquibase now and it's awesome!

That's what I'd like to use for Keycloak, but I'd also like to use the same as you guys do.

----- Original Message -----
> From: "Matthias Wessendorf" <matzew at apache.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Tuesday, 7 October, 2014 9:27:45 AM
> Subject: Re: [aerogear-dev] database migration
> 
> I have heard about FlywayDB, but from your email liquibase sounds like a good
> idea!
> 
> Thanks for sharing, Erik!
> 
> On Mon, Oct 6, 2014 at 5:48 PM, Erik Jan de Wit < edewit at redhat.com > wrote:
> 
> 
> 
> Hi,
> 
> Now that we have 2 versions out of the door, when we change stuff we need an
> easy upgrade path. Not only for the API but also for the database. Because
> we support a couple of them having something of a process would help.
> 
> I?ve have used liquibase in the past. You write ?change sets? in yaml, json
> or if you must in xml, it will create a migration table in the database and
> execute the changes needed to bring it up to date or you can create a sql
> script that will do the same. Cool thing about this approach is that it?s
> independent of the database
> 
> http://www.liquibase.org
> 
> Another tool I?ve heard about, but also promising is Flyway. It?s supports
> writing migrations in sql and java comes with it?s own java api. Basically
> the same idea with regards to this migration table, but here you need to
> specify your own sql scripts. Or you can write migrations in java where
> having special named java class gets executed to update/migrate the data.
> 
> http://flywaydb.org
> 
> WDYT?
> 
> Cheers,
> Erik Jan
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> --
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From matzew at apache.org  Tue Oct  7 04:58:41 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 7 Oct 2014 10:58:41 +0200
Subject: [aerogear-dev] database migration
In-Reply-To: <1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
Message-ID: <CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>

On Tuesday, October 7, 2014, Stian Thorgersen <stian at redhat.com> wrote:

> I've been playing with Liquibase now and it's awesome!
>
> That's what I'd like to use for Keycloak, but I'd also like to use the
> same as you guys do.


yes! would be great uf our projects use the same.

looks like Liquibase is the way to go?


>
> ----- Original Message -----
> > From: "Matthias Wessendorf" <matzew at apache.org <javascript:;>>
> > To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org
> <javascript:;>>
> > Sent: Tuesday, 7 October, 2014 9:27:45 AM
> > Subject: Re: [aerogear-dev] database migration
> >
> > I have heard about FlywayDB, but from your email liquibase sounds like a
> good
> > idea!
> >
> > Thanks for sharing, Erik!
> >
> > On Mon, Oct 6, 2014 at 5:48 PM, Erik Jan de Wit < edewit at redhat.com
> <javascript:;> > wrote:
> >
> >
> >
> > Hi,
> >
> > Now that we have 2 versions out of the door, when we change stuff we
> need an
> > easy upgrade path. Not only for the API but also for the database.
> Because
> > we support a couple of them having something of a process would help.
> >
> > I?ve have used liquibase in the past. You write ?change sets? in yaml,
> json
> > or if you must in xml, it will create a migration table in the database
> and
> > execute the changes needed to bring it up to date or you can create a sql
> > script that will do the same. Cool thing about this approach is that it?s
> > independent of the database
> >
> > http://www.liquibase.org
> >
> > Another tool I?ve heard about, but also promising is Flyway. It?s
> supports
> > writing migrations in sql and java comes with it?s own java api.
> Basically
> > the same idea with regards to this migration table, but here you need to
> > specify your own sql scripts. Or you can write migrations in java where
> > having special named java class gets executed to update/migrate the data.
> >
> > http://flywaydb.org
> >
> > WDYT?
> >
> > Cheers,
> > Erik Jan
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org <javascript:;>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://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/20141007/7e171fa9/attachment.html 

From cvasilak at gmail.com  Tue Oct  7 08:49:04 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 7 Oct 2014 15:49:04 +0300
Subject: [aerogear-dev] iOS meeting
In-Reply-To: <731050CF-DEDB-4A4A-B835-1EC606CD35B1@gmail.com>
References: <731050CF-DEDB-4A4A-B835-1EC606CD35B1@gmail.com>
Message-ID: <B97D0EB9-E4C2-463C-B774-52771144FE30@gmail.com>

fyi,

meeting minutes:

<jbott>	 Meeting ended Tue Oct  7 12:46:38 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-10-07-12.08.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-07-12.08.txt
 <jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-07-12.08.log.html

On Sep 9, 2014, at 11:51 AM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello Swifter and iOS lovers,
> 
> 
> Here is the proposed agenda of our next meeting which will take place Tuesday 16 September at 2pm (CEST - UTC + 2hours)
> soclap.com/p/aerogear_ios_meeting_11sept2014
> 
> Feel free to add topics to it and join us if you want to discuss with us next 2.0 iOS release.
> 
> ++
> Corinne
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From stian at redhat.com  Tue Oct  7 08:59:23 2014
From: stian at redhat.com (Stian Thorgersen)
Date: Tue, 7 Oct 2014 08:59:23 -0400 (EDT)
Subject: [aerogear-dev] database migration
In-Reply-To: <CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
	<CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
Message-ID: <1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Matthias Wessendorf" <matzew at apache.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Tuesday, 7 October, 2014 10:58:41 AM
> Subject: Re: [aerogear-dev] database migration
> 
> 
> 
> On Tuesday, October 7, 2014, Stian Thorgersen < stian at redhat.com > wrote:
> 
> 
> I've been playing with Liquibase now and it's awesome!
> 
> That's what I'd like to use for Keycloak, but I'd also like to use the same
> as you guys do.
> 
> yes! would be great uf our projects use the same.
> 
> looks like Liquibase is the way to go?

+1

FlywayDB uses SQL directly, so we have to deal with differences between databases ourselves. IMO that renders it useless!

> 
> 
> 
> ----- Original Message -----
> > From: "Matthias Wessendorf" < matzew at apache.org >
> > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> > Sent: Tuesday, 7 October, 2014 9:27:45 AM
> > Subject: Re: [aerogear-dev] database migration
> > 
> > I have heard about FlywayDB, but from your email liquibase sounds like a
> > good
> > idea!
> > 
> > Thanks for sharing, Erik!
> > 
> > On Mon, Oct 6, 2014 at 5:48 PM, Erik Jan de Wit < edewit at redhat.com >
> > wrote:
> > 
> > 
> > 
> > Hi,
> > 
> > Now that we have 2 versions out of the door, when we change stuff we need
> > an
> > easy upgrade path. Not only for the API but also for the database. Because
> > we support a couple of them having something of a process would help.
> > 
> > I?ve have used liquibase in the past. You write ?change sets? in yaml, json
> > or if you must in xml, it will create a migration table in the database and
> > execute the changes needed to bring it up to date or you can create a sql
> > script that will do the same. Cool thing about this approach is that it?s
> > independent of the database
> > 
> > http://www.liquibase.org
> > 
> > Another tool I?ve heard about, but also promising is Flyway. It?s supports
> > writing migrations in sql and java comes with it?s own java api. Basically
> > the same idea with regards to this migration table, but here you need to
> > specify your own sql scripts. Or you can write migrations in java where
> > having special named java class gets executed to update/migrate the data.
> > 
> > http://flywaydb.org
> > 
> > WDYT?
> > 
> > Cheers,
> > Erik Jan
> > 
> > 
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > 
> > 
> > 
> > --
> > Matthias Wessendorf
> > 
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> > 
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.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
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From edewit at redhat.com  Tue Oct  7 09:02:59 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 7 Oct 2014 15:02:59 +0200
Subject: [aerogear-dev] database migration
In-Reply-To: <1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
	<CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
	<1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>
Message-ID: <DBBFE1C0-DDBC-43E1-BC86-1B60F4CFA174@redhat.com>

>> 
>> looks like Liquibase is the way to go?
> 
> +1
> 
> FlywayDB uses SQL directly, so we have to deal with differences between databases ourselves. IMO that renders it useless!

liquibase it is, and let?s not use xml for the change sets ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/3355a51d/attachment.html 

From stian at redhat.com  Tue Oct  7 09:11:58 2014
From: stian at redhat.com (Stian Thorgersen)
Date: Tue, 7 Oct 2014 09:11:58 -0400 (EDT)
Subject: [aerogear-dev] database migration
In-Reply-To: <DBBFE1C0-DDBC-43E1-BC86-1B60F4CFA174@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
	<CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
	<1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>
	<DBBFE1C0-DDBC-43E1-BC86-1B60F4CFA174@redhat.com>
Message-ID: <1862184835.63049258.1412687518710.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Erik Jan de Wit" <edewit at redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Tuesday, 7 October, 2014 3:02:59 PM
> Subject: Re: [aerogear-dev] database migration
> 
> 
> 
> 
> 
> 
> 
> looks like Liquibase is the way to go?
> 
> +1
> 
> FlywayDB uses SQL directly, so we have to deal with differences between
> databases ourselves. IMO that renders it useless!
> 
> liquibase it is, and let?s not use xml for the change sets ;)

Why not XML?

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


From edewit at redhat.com  Tue Oct  7 09:20:19 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 7 Oct 2014 15:20:19 +0200
Subject: [aerogear-dev] database migration
In-Reply-To: <1862184835.63049258.1412687518710.JavaMail.zimbra@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
	<CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
	<1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>
	<DBBFE1C0-DDBC-43E1-BC86-1B60F4CFA174@redhat.com>
	<1862184835.63049258.1412687518710.JavaMail.zimbra@redhat.com>
Message-ID: <91B9B026-7646-4C4B-928D-93FC2E4FED25@redhat.com>

On 7 Oct,2014, at 15:11 , Stian Thorgersen <stian at redhat.com> wrote:

>> FlywayDB uses SQL directly, so we have to deal with differences between
>> databases ourselves. IMO that renders it useless!
>> 
>> liquibase it is, and let?s not use xml for the change sets ;)
> 
> Why not XML?
> 

We hate XML



From cvasilak at gmail.com  Tue Oct  7 09:21:42 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 7 Oct 2014 16:21:42 +0300
Subject: [aerogear-dev] Handling 1.x repositories
Message-ID: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>

Hi all,

as we approach 2.0 releases in iOS we are evaluating the faith of our 1.x repository [1]. Currently the functionality has been splitted in separate  repositories[2][3] with more to come in subsequent releases . Since other platforms follow  the same approach of separation, would like to get your view on how you will handle the ?1.x? repo?

We were thinking to:

a) promote the master repo to an '1.x branch?  and update the repos README.md to be clear that is our 1.x branch
b) use the ?master? branch with just a single README.md that provides links to the different repos.


Wdyth?


-
Christos


[1] https://github.com/aerogear/aerogear-ios
[2] https://github.com/aerogear/aerogear-ios-http
[3] https://github.com/aerogear/aerogear-ios-oauth2



From matzew at apache.org  Tue Oct  7 10:07:42 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 7 Oct 2014 16:07:42 +0200
Subject: [aerogear-dev] Handling 1.x repositories
In-Reply-To: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>
References: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>
Message-ID: <CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>

On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak at gmail.com>
wrote:

> Hi all,
>
> as we approach 2.0 releases in iOS we are evaluating the faith of our 1.x
> repository [1]. Currently the functionality has been splitted in separate
> repositories[2][3] with more to come in subsequent releases . Since other
> platforms follow  the same approach of separation, would like to get your
> view on how you will handle the ?1.x? repo?
>
> We were thinking to:
>
> a) promote the master repo to an '1.x branch?  and update the repos
> README.md to be clear that is our 1.x branch
> b) use the ?master? branch with just a single README.md that provides
> links to the different repos.
>

Do you mean, the repo in [1] will be just a readme, linking to all the
different 'modules'? If so, +1 on that


>
>
> Wdyth?
>
>
> -
> Christos
>
>
> [1] https://github.com/aerogear/aerogear-ios
> [2] https://github.com/aerogear/aerogear-ios-http
> [3] https://github.com/aerogear/aerogear-ios-oauth2
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From corinnekrych at gmail.com  Tue Oct  7 11:02:45 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 7 Oct 2014 17:02:45 +0200
Subject: [aerogear-dev] Handling 1.x repositories
In-Reply-To: <CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>
References: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>
	<CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>
Message-ID: <CAL8vO=cXBpgkNX55UhOPbhFm_a91CZ8g+BCcwSvR-uJpS5=AAQ@mail.gmail.com>

+1 on having aerogear-ios be our umbrella repo.

Master to list our different 2.0 repos maybe to start with just README.
Once we've got cocopoads we can think of some think like a subpod.

Another topic is to switch 'swift' branch to master and create a 'obj-c'
branch with obj-c code for repo like ios-push, ios-cookbook,

Do we all agree on that?

++
Corinne


On 7 October 2014 16:07, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
> On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak at gmail.com>
> wrote:
>
>> Hi all,
>>
>> as we approach 2.0 releases in iOS we are evaluating the faith of our 1.x
>> repository [1]. Currently the functionality has been splitted in separate
>> repositories[2][3] with more to come in subsequent releases . Since other
>> platforms follow  the same approach of separation, would like to get your
>> view on how you will handle the ?1.x? repo?
>>
>> We were thinking to:
>>
>> a) promote the master repo to an '1.x branch?  and update the repos
>> README.md to be clear that is our 1.x branch
>> b) use the ?master? branch with just a single README.md that provides
>> links to the different repos.
>>
>
> Do you mean, the repo in [1] will be just a readme, linking to all the
> different 'modules'? If so, +1 on that
>
>
>>
>>
>> Wdyth?
>>
>>
>> -
>> Christos
>>
>>
>> [1] https://github.com/aerogear/aerogear-ios
>> [2] https://github.com/aerogear/aerogear-ios-http
>> [3] https://github.com/aerogear/aerogear-ios-oauth2
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/b9f5b808/attachment.html 

From lholmqui at redhat.com  Tue Oct  7 11:06:59 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 7 Oct 2014 11:06:59 -0400
Subject: [aerogear-dev] Handling 1.x repositories
In-Reply-To: <CAL8vO=cXBpgkNX55UhOPbhFm_a91CZ8g+BCcwSvR-uJpS5=AAQ@mail.gmail.com>
References: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>
	<CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>
	<CAL8vO=cXBpgkNX55UhOPbhFm_a91CZ8g+BCcwSvR-uJpS5=AAQ@mail.gmail.com>
Message-ID: <89948577-BB7A-4ED2-88AA-BA57E02036EE@redhat.com>


On Oct 7, 2014, at 11:02 AM, Corinne Krych <corinnekrych at gmail.com> wrote:

> +1 on having aerogear-ios be our umbrella repo.
> 
> Master to list our different 2.0 repos maybe to start with just README. Once we've got cocopoads we can think of some think like a subpod.
> 
> Another topic is to switch 'swift' branch to master and create a 'obj-c' branch with obj-c code for repo like ios-push, ios-cookbook,
that probably makes sense.  did apple announce yet that all new apps need to be for iOS8 :)

> 
> Do we all agree on that?
> 
> ++
> Corinne
> 
> 
> On 7 October 2014 16:07, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak at gmail.com> wrote:
> Hi all,
> 
> as we approach 2.0 releases in iOS we are evaluating the faith of our 1.x repository [1]. Currently the functionality has been splitted in separate  repositories[2][3] with more to come in subsequent releases . Since other platforms follow  the same approach of separation, would like to get your view on how you will handle the ?1.x? repo?
> 
> We were thinking to:
> 
> a) promote the master repo to an '1.x branch?  and update the repos README.md to be clear that is our 1.x branch
> b) use the ?master? branch with just a single README.md that provides links to the different repos.
> 
> Do you mean, the repo in [1] will be just a readme, linking to all the different 'modules'? If so, +1 on that
>  
> 
> 
> Wdyth?
> 
> 
> -
> Christos
> 
> 
> [1] https://github.com/aerogear/aerogear-ios
> [2] https://github.com/aerogear/aerogear-ios-http
> [3] https://github.com/aerogear/aerogear-ios-oauth2
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141007/60c31980/attachment.html 

From cvasilak at gmail.com  Tue Oct  7 11:09:56 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 7 Oct 2014 18:09:56 +0300
Subject: [aerogear-dev] Handling 1.x repositories
In-Reply-To: <CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>
References: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>
	<CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>
Message-ID: <D8DD0D80-E825-465B-AA12-8A3254049D83@gmail.com>


On Oct 7, 2014, at 5:07 PM, Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak at gmail.com> wrote:
> Hi all,
> 
> as we approach 2.0 releases in iOS we are evaluating the faith of our 1.x repository [1]. Currently the functionality has been splitted in separate  repositories[2][3] with more to come in subsequent releases . Since other platforms follow  the same approach of separation, would like to get your view on how you will handle the ?1.x? repo?
> 
> We were thinking to:
> 
> a) promote the master repo to an '1.x branch?  and update the repos README.md to be clear that is our 1.x branch
> b) use the ?master? branch with just a single README.md that provides links to the different repos.
> 
> Do you mean, the repo in [1] will be just a readme, linking to all the different 'modules'? If so, +1 on that

meant exactly that yes

-
Christos



>  
> 
> 
> Wdyth?
> 
> 
> -
> Christos
> 
> 
> [1] https://github.com/aerogear/aerogear-ios
> [2] https://github.com/aerogear/aerogear-ios-http
> [3] https://github.com/aerogear/aerogear-ios-oauth2
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From matzew at apache.org  Tue Oct  7 11:14:50 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 7 Oct 2014 17:14:50 +0200
Subject: [aerogear-dev] Handling 1.x repositories
In-Reply-To: <CAL8vO=cXBpgkNX55UhOPbhFm_a91CZ8g+BCcwSvR-uJpS5=AAQ@mail.gmail.com>
References: <F263F428-8D52-4630-8D83-4BB80160824E@gmail.com>
	<CAAg5f2R50a2R+D9tD2xJwdnBHJvKfjovtK-0vs8S1XYWHO4pfw@mail.gmail.com>
	<CAL8vO=cXBpgkNX55UhOPbhFm_a91CZ8g+BCcwSvR-uJpS5=AAQ@mail.gmail.com>
Message-ID: <CAAg5f2QMnRS0gKc7sTeLPL_3srYdfR-+EXnnJBYByvgD-ZKP=Q@mail.gmail.com>

On Tue, Oct 7, 2014 at 5:02 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> +1 on having aerogear-ios be our umbrella repo.
>
> Master to list our different 2.0 repos maybe to start with just README.
>
+1


> Once we've got cocopoads we can think of some think like a subpod.
>

not sure :) but if the community goes w/ that, let's do what's natural there


>
> Another topic is to switch 'swift' branch to master and create a 'obj-c'
> branch with obj-c code for repo like ios-push, ios-cookbook,
>

+1 on Swift going to master

and have 1.x.y branches and.... for maintenance let's do objc branch(es) as
well


>
> Do we all agree on that?
>
> ++
> Corinne
>
>
> On 7 October 2014 16:07, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>> On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak at gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> as we approach 2.0 releases in iOS we are evaluating the faith of our
>>> 1.x repository [1]. Currently the functionality has been splitted in
>>> separate  repositories[2][3] with more to come in subsequent releases .
>>> Since other platforms follow  the same approach of separation, would like
>>> to get your view on how you will handle the ?1.x? repo?
>>>
>>> We were thinking to:
>>>
>>> a) promote the master repo to an '1.x branch?  and update the repos
>>> README.md to be clear that is our 1.x branch
>>> b) use the ?master? branch with just a single README.md that provides
>>> links to the different repos.
>>>
>>
>> Do you mean, the repo in [1] will be just a readme, linking to all the
>> different 'modules'? If so, +1 on that
>>
>>
>>>
>>>
>>> Wdyth?
>>>
>>>
>>> -
>>> Christos
>>>
>>>
>>> [1] https://github.com/aerogear/aerogear-ios
>>> [2] https://github.com/aerogear/aerogear-ios-http
>>> [3] https://github.com/aerogear/aerogear-ios-oauth2
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141007/e9807477/attachment.html 

From matzew at apache.org  Wed Oct  8 06:16:48 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 8 Oct 2014 12:16:48 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
Message-ID: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>

Hi,

as of today, we have a single user (admin), to revisit that we have
AGPUSH-697 (see [1]).

Based on changes over the months (e.g new UI and being based on Keycloak),
I have updated our old spec/gist:
https://gist.github.com/matzew/ed0055000a8347488a37

Greetings,
Matthias

[1] https://issues.jboss.org/browse/AGPUSH-697

-- 
Matthias Wessendorf

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

From lukas.fryc at gmail.com  Wed Oct  8 06:40:38 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Wed, 8 Oct 2014 12:40:38 +0200
Subject: [aerogear-dev] some cookbook recipes need some backend
In-Reply-To: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
References: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
Message-ID: <CAEroY37H5xcTTr17i0dV+era2MmaL44r6TUNdmF55Z6yePJGbw@mail.gmail.com>

Nice job, Corinne.

In terms of AngularJS usage, everything seems nice.

I just wondered why you haven't placed application right under the root of
the webapp (it's under /photos contextPath)?
It would be easier for the user to find it imo.

Cheers!

~ Lukas

On Thu, Sep 18, 2014 at 5:30 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Hello Guys
>
> To complete our cookbook repositories: iOS, web, android and cordova
> (still under eric private repo), I?d like to have a
> aerogear-backend-cookbook. We already have some demos which requires
> backend. I?ve put them together in:
>
> https://github.com/corinnekrych/aerogear-backend-cookbook
>
> Each app has a separate build and is independent. For new I?ve put
> together:
> AeroDoc
> PushQuickstart (as submodules)
> Buddies
> ProductInventory (oauth2 keycloak) kind of helloWorld app, very simple
>
> Next addition, I?m thinking to do a Shoot?nShare file upload Server using
> Keycloak. So we can have a more complete demo of AeroGear OAuth2 and
> Keycloak.
>
> Thoughts?
>
> ++
> Corinne
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141008/d2d6f584/attachment.html 

From corinnekrych at gmail.com  Wed Oct  8 09:09:20 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Wed, 8 Oct 2014 15:09:20 +0200
Subject: [aerogear-dev] some cookbook recipes need some backend
In-Reply-To: <CAEroY37H5xcTTr17i0dV+era2MmaL44r6TUNdmF55Z6yePJGbw@mail.gmail.com>
References: <ED0D19F2-29D8-4A1D-BA9B-201A10CF7435@gmail.com>
	<CAEroY37H5xcTTr17i0dV+era2MmaL44r6TUNdmF55Z6yePJGbw@mail.gmail.com>
Message-ID: <CAL8vO=cJFEijR04OLWYLPWZrwRM62_4otW8Cuf=N4vDFi8yQYw@mail.gmail.com>

Good point, let's move... it's more a standard to find it at root level.
++
Corinne

On 8 October 2014 12:40, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Nice job, Corinne.
>
> In terms of AngularJS usage, everything seems nice.
>
> I just wondered why you haven't placed application right under the root of
> the webapp (it's under /photos contextPath)?
> It would be easier for the user to find it imo.
>
> Cheers!
>
> ~ Lukas
>
> On Thu, Sep 18, 2014 at 5:30 PM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
>
>> Hello Guys
>>
>> To complete our cookbook repositories: iOS, web, android and cordova
>> (still under eric private repo), I?d like to have a
>> aerogear-backend-cookbook. We already have some demos which requires
>> backend. I?ve put them together in:
>>
>> https://github.com/corinnekrych/aerogear-backend-cookbook
>>
>> Each app has a separate build and is independent. For new I?ve put
>> together:
>> AeroDoc
>> PushQuickstart (as submodules)
>> Buddies
>> ProductInventory (oauth2 keycloak) kind of helloWorld app, very simple
>>
>> Next addition, I?m thinking to do a Shoot?nShare file upload Server using
>> Keycloak. So we can have a more complete demo of AeroGear OAuth2 and
>> Keycloak.
>>
>> Thoughts?
>>
>> ++
>> Corinne
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141008/59a88eb6/attachment.html 

From bruno at abstractj.org  Wed Oct  8 10:48:35 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 11:48:35 -0300
Subject: [aerogear-dev] Security - Meeting minutes
Message-ID: <20141008144835.GA60902@abstractj.org>

[11:47:07] jbott:	 Meeting ended Wed Oct  8 14:46:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[11:47:07] jbott:	 Minutes:        http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
[11:47:07] jbott:	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.txt
[11:47:08] jbott:	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.log.html

--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Wed Oct  8 11:32:02 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 8 Oct 2014 17:32:02 +0200
Subject: [aerogear-dev] Releasing new parent (0.2.7)
Message-ID: <CAAg5f2R2Rwj-4QAZC_pdw3X2ywUQ+9aT0ZeSTzOqQ5Y5AOR7VQ@mail.gmail.com>

Hi,

I'd like to run a new release of our parent. Since the last 0.2.6 release
there were some changes related to newer versions:

* Added AngularJS extension, updated Selenium version
* Removal of unexisting dependency
* Moved declaration of org.slf4j dependencies to aerogear-test-bom, as they
are now used only in test profiles
* Upgrade Keycloak to final 1.0.1.Final
* Removed scope from aerogear-bom
* using latest greatest of OpenEJB for tests


The staging repo is here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3991/

Let me know about the release by Friday, so we can upload the bits to maven
central over the weekend.

Thanks,
Matthias

-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Wed Oct  8 11:34:49 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 12:34:49 -0300
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
Message-ID: <20141008153449.GA56284@abstractj.org>

If I understood correctly what we want to achieve tl;dr is:

- Include a JPA query on UPS to list all app/variants on UPS
- Introduce fine grained permissions for this query. Into this way we
  can differentiate admin from developers[1]
- Create an interface on UPS to the admin, otherwise the whole
  implementation is useless.

>From my understanding, Keycloak will just manage these users and unless
something has changed, we provide the fine grained authorization model on UPS. Like
we did in the past.

Am I correct?

[1] - http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html

On 2014-10-08, Matthias Wessendorf wrote:
> Hi,
>
> as of today, we have a single user (admin), to revisit that we have
> AGPUSH-697 (see [1]).
>
> Based on changes over the months (e.g new UI and being based on Keycloak),
> I have updated our old spec/gist:
> https://gist.github.com/matzew/ed0055000a8347488a37
>
> Greetings,
> Matthias
>
> [1] https://issues.jboss.org/browse/AGPUSH-697
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Wed Oct  8 11:34:59 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 8 Oct 2014 17:34:59 +0200
Subject: [aerogear-dev] [AeroGear Push] Update our openshift cartridge to
	WildFly
Message-ID: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>

Hello,

as of today, we are using JBoss AS 7.1.1 as our main runtime for the
AeroGear Push cartridge:
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push

I'd like to rename this to -jboss7

and make the wildfly cartrige our default. Currently it is located here:
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push-wildfly

To effectively take this up, the repo will be renamed to "
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push"

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/20141008/8b6f6c2a/attachment.html 

From matzew at apache.org  Wed Oct  8 11:40:32 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 8 Oct 2014 17:40:32 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <20141008153449.GA56284@abstractj.org>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
Message-ID: <CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>

On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> If I understood correctly what we want to achieve tl;dr is:
>
> - Include a JPA query on UPS to list all app/variants on UPS
>

yes


> - Introduce fine grained permissions for this query. Into this way we
>   can differentiate admin from developers[1]
>

the 'how' is tbd;
today we query for the user's own apps/variant:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88

One (simple) option is: the underlying service could do a "select *
from..." if the role is 'admin'


> - Create an interface on UPS to the admin, otherwise the whole
>   implementation is useless.
>

what do you mean ?


>
> >From my understanding, Keycloak will just manage these users and unless
> something has changed, we provide the fine grained authorization model on
> UPS. Like
> we did in the past.
>

yeah, the users live in Keycloak - we somehow differentiate on the
role/user if we do a "select all" or just those for the specific user


>
> Am I correct?
>
> [1] - http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
>
> On 2014-10-08, Matthias Wessendorf wrote:
> > Hi,
> >
> > as of today, we have a single user (admin), to revisit that we have
> > AGPUSH-697 (see [1]).
> >
> > Based on changes over the months (e.g new UI and being based on
> Keycloak),
> > I have updated our old spec/gist:
> > https://gist.github.com/matzew/ed0055000a8347488a37
> >
> > Greetings,
> > Matthias
> >
> > [1] https://issues.jboss.org/browse/AGPUSH-697
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From kpiwko at redhat.com  Wed Oct  8 11:57:48 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 08 Oct 2014 17:57:48 +0200
Subject: [aerogear-dev] Releasing new parent (0.2.7)
In-Reply-To: <CAAg5f2R2Rwj-4QAZC_pdw3X2ywUQ+9aT0ZeSTzOqQ5Y5AOR7VQ@mail.gmail.com>
References: <CAAg5f2R2Rwj-4QAZC_pdw3X2ywUQ+9aT0ZeSTzOqQ5Y5AOR7VQ@mail.gmail.com>
Message-ID: <1412783868.14539.13.camel@kpiwko-x220>

Sounds good! We'll update to newer test-bom tomorrow to check the
content.

Thanks for this release!

Karel

On Wed, 2014-10-08 at 17:32 +0200, Matthias Wessendorf wrote:
> Hi,
> 
> I'd like to run a new release of our parent. Since the last 0.2.6 release
> there were some changes related to newer versions:
> 
> * Added AngularJS extension, updated Selenium version
> * Removal of unexisting dependency
> * Moved declaration of org.slf4j dependencies to aerogear-test-bom, as they
> are now used only in test profiles
> * Upgrade Keycloak to final 1.0.1.Final
> * Removed scope from aerogear-bom
> * using latest greatest of OpenEJB for tests
> 
> 
> The staging repo is here:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3991/
> 
> Let me know about the release by Friday, so we can upload the bits to maven
> central over the weekend.
> 
> Thanks,
> Matthias
> 
> _______________________________________________
> 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 Oct  8 11:59:48 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 8 Oct 2014 17:59:48 +0200
Subject: [aerogear-dev] [AeroGear Push] Update our openshift cartridge
	to WildFly
In-Reply-To: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
References: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
Message-ID: <CAD_dpu1FYuKbozWstoTVLay_eQT0sS2rDmEhdvBLyO+_86XCkA@mail.gmail.com>

go for it !

On Wed, Oct 8, 2014 at 5:34 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello,
>
> as of today, we are using JBoss AS 7.1.1 as our main runtime for the
> AeroGear Push cartridge:
> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push
>
> I'd like to rename this to -jboss7
>
> and make the wildfly cartrige our default. Currently it is located here:
>
> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push-wildfly
>
> To effectively take this up, the repo will be renamed to "
> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push"
>
> 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/20141008/0dde1042/attachment-0001.html 

From bruno at abstractj.org  Wed Oct  8 12:25:55 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 13:25:55 -0300
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
Message-ID: <20141008162555.GC56284@abstractj.org>

On 2014-10-08, Matthias Wessendorf wrote:
> On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > If I understood correctly what we want to achieve tl;dr is:
> >
> > - Include a JPA query on UPS to list all app/variants on UPS
> >
>
> yes
>
>
> > - Introduce fine grained permissions for this query. Into this way we
> >   can differentiate admin from developers[1]
> >
>
> the 'how' is tbd;

I just want to check if my reading is correct and we can start to work
on the "how" with Jiras. If you are fine with it.

> today we query for the user's own apps/variant:
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
>
> One (simple) option is: the underlying service could do a "select *
> from..." if the role is 'admin'

Alright. But the query must display that some app "golum" belongs to
"abstractj" and another app with the same name, belongs to matzew.
Because is pretty likely to happen naming duplication.

>
>
> > - Create an interface on UPS to the admin, otherwise the whole
> >   implementation is useless.
> >
>
> what do you mean ?

If you query the database for all apps created. How do you delete the
application "golum" created by bruno if I have 10 apps named "golum" in
my database?

That's why I think the mininum for the UPS admin interface must be defined, right
now, before start the whole implementation. What would you expect to see
when you query the whole database?

>
>
> >
> > >From my understanding, Keycloak will just manage these users and unless
> > something has changed, we provide the fine grained authorization model on
> > UPS. Like
> > we did in the past.
> >
>
> yeah, the users live in Keycloak - we somehow differentiate on the
> role/user if we do a "select all" or just those for the specific user
>
>
> >
> > Am I correct?
> >
> > [1] - http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> >
> > On 2014-10-08, Matthias Wessendorf wrote:
> > > Hi,
> > >
> > > as of today, we have a single user (admin), to revisit that we have
> > > AGPUSH-697 (see [1]).
> > >
> > > Based on changes over the months (e.g new UI and being based on
> > Keycloak),
> > > I have updated our old spec/gist:
> > > https://gist.github.com/matzew/ed0055000a8347488a37
> > >
> > > Greetings,
> > > Matthias
> > >
> > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct  8 12:39:12 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 13:39:12 -0300
Subject: [aerogear-dev] [AeroGear Push] Update our openshift cartridge
 to WildFly
In-Reply-To: <CAD_dpu1FYuKbozWstoTVLay_eQT0sS2rDmEhdvBLyO+_86XCkA@mail.gmail.com>
References: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
	<CAD_dpu1FYuKbozWstoTVLay_eQT0sS2rDmEhdvBLyO+_86XCkA@mail.gmail.com>
Message-ID: <20141008163912.GE56284@abstractj.org>

+1

On 2014-10-08, Sebastien Blanc wrote:
> go for it !
>
> On Wed, Oct 8, 2014 at 5:34 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> > Hello,
> >
> > as of today, we are using JBoss AS 7.1.1 as our main runtime for the
> > AeroGear Push cartridge:
> > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push
> >
> > I'd like to rename this to -jboss7
> >
> > and make the wildfly cartrige our default. Currently it is located here:
> >
> > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push-wildfly
> >
> > To effectively take this up, the repo will be renamed to "
> > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push"
> >
> > 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
PGP: 0x84DC9914

From daniel at passos.me  Wed Oct  8 13:33:03 2014
From: daniel at passos.me (Daniel Passos)
Date: Wed, 8 Oct 2014 14:33:03 -0300
Subject: [aerogear-dev] [AeroGear Push] Update our openshift cartridge
	to WildFly
In-Reply-To: <20141008163912.GE56284@abstractj.org>
References: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
	<CAD_dpu1FYuKbozWstoTVLay_eQT0sS2rDmEhdvBLyO+_86XCkA@mail.gmail.com>
	<20141008163912.GE56284@abstractj.org>
Message-ID: <CAKjsGbuGeZFwbSY9fRG3htx14gs2S6BkCcYD9fViLvKZkXSB7A@mail.gmail.com>

+1

On Wed, Oct 8, 2014 at 1:39 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> +1
>
> On 2014-10-08, Sebastien Blanc wrote:
> > go for it !
> >
> > On Wed, Oct 8, 2014 at 5:34 PM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> > > Hello,
> > >
> > > as of today, we are using JBoss AS 7.1.1 as our main runtime for the
> > > AeroGear Push cartridge:
> > > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push
> > >
> > > I'd like to rename this to -jboss7
> > >
> > > and make the wildfly cartrige our default. Currently it is located
> here:
> > >
> > >
> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push-wildfly
> > >
> > > To effectively take this up, the repo will be renamed to "
> > > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push"
> > >
> > > 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
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141008/88577e54/attachment.html 

From matzew at apache.org  Wed Oct  8 13:49:34 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 8 Oct 2014 19:49:34 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <20141008162555.GC56284@abstractj.org>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
Message-ID: <CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>

On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-10-08, Matthias Wessendorf wrote:
> > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > If I understood correctly what we want to achieve tl;dr is:
> > >
> > > - Include a JPA query on UPS to list all app/variants on UPS
> > >
> >
> > yes
> >
> >
> > > - Introduce fine grained permissions for this query. Into this way we
> > >   can differentiate admin from developers[1]
> > >
> >
> > the 'how' is tbd;
>
> I just want to check if my reading is correct and we can start to work
> on the "how" with Jiras. If you are fine with it.
>
> > today we query for the user's own apps/variant:
> >
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
> >
> > One (simple) option is: the underlying service could do a "select *
> > from..." if the role is 'admin'
>
> Alright. But the query must display that some app "golum" belongs to
> "abstractj" and another app with the same name, belongs to matzew.
> Because is pretty likely to happen naming duplication.
>

yeah, sure. That info is already present on the PushApplication - currently
that is just not displayed.


>
> >
> >
> > > - Create an interface on UPS to the admin, otherwise the whole
> > >   implementation is useless.
> > >
> >
> > what do you mean ?
>
> If you query the database for all apps created. How do you delete the
> application "golum" created by bruno if I have 10 apps named "golum" in
> my database?
>

Ah, ok. I was wondering you wanted to define some completely new UI :)

I had something like this in mind (yes, I am not a designer :))
http://people.apache.org/~matzew/AdminViewOnApps.png

That's just one initial thought. Once we agree on this overall feature, I
think we will nail the details of the 'how' in the relevant JIRA subtasks
of AGPUSH-697.
However I fully agree that we need to apply some tweaks to the existing UI,
so that the owner name is visible when the 'admin' is looking at the
"application overview" page, like in the screenshot.


>
> That's why I think the mininum for the UPS admin interface must be
> defined, right
> now, before start the whole implementation. What would you expect to see
> when you query the whole database?
>

I thought about adding 'pagination' on the "application overview" page,
similar like we do on the installations.

-Matthias



>
> >
> >
> > >
> > > >From my understanding, Keycloak will just manage these users and
> unless
> > > something has changed, we provide the fine grained authorization model
> on
> > > UPS. Like
> > > we did in the past.
> > >
> >
> > yeah, the users live in Keycloak - we somehow differentiate on the
> > role/user if we do a "select all" or just those for the specific user
> >
> >
> > >
> > > Am I correct?
> > >
> > > [1] -
> http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> > >
> > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > Hi,
> > > >
> > > > as of today, we have a single user (admin), to revisit that we have
> > > > AGPUSH-697 (see [1]).
> > > >
> > > > Based on changes over the months (e.g new UI and being based on
> > > Keycloak),
> > > > I have updated our old spec/gist:
> > > > https://gist.github.com/matzew/ed0055000a8347488a37
> > > >
> > > > Greetings,
> > > > Matthias
> > > >
> > > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From qmx at qmx.me  Wed Oct  8 14:01:36 2014
From: qmx at qmx.me (Douglas Campos)
Date: Wed, 8 Oct 2014 15:01:36 -0300
Subject: [aerogear-dev] [AeroGear Push] Update our openshift cartridge
 to WildFly
In-Reply-To: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
References: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
Message-ID: <20141008180136.GN5025@darkstar.local>

+1

-- 
qmx

From daniel.bevenius at gmail.com  Wed Oct  8 14:07:41 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Wed, 8 Oct 2014 20:07:41 +0200
Subject: [aerogear-dev] [AeroGear Push] Update our openshift cartridge
	to WildFly
In-Reply-To: <20141008180136.GN5025@darkstar.local>
References: <CAAg5f2TsJO60bS5-AzAqV=gVzSaC4V5tCDHLyQ_1Lf8JB8+wRg@mail.gmail.com>
	<20141008180136.GN5025@darkstar.local>
Message-ID: <CAFJm-3EBssCm20zAKOAcZ5Qcj3d9TFc6GCW2rhuAKGoq_UM=8g@mail.gmail.com>

+1

onsdag 8 oktober 2014 skrev Douglas Campos <qmx at qmx.me>:

> +1
>
> --
> qmx
> _______________________________________________
> 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/20141008/cd61d4bd/attachment.html 

From bruno at abstractj.com  Wed Oct  8 16:23:53 2014
From: bruno at abstractj.com (Bruno Oliveira)
Date: Wed, 8 Oct 2014 17:23:53 -0300
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
Message-ID: <20141008202353.GA64806@abstractj.com>

On 2014-10-08, Matthias Wessendorf wrote:
> On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-10-08, Matthias Wessendorf wrote:
> > > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >
> > > > If I understood correctly what we want to achieve tl;dr is:
> > > >
> > > > - Include a JPA query on UPS to list all app/variants on UPS
> > > >
> > >
> > > yes
> > >
> > >
> > > > - Introduce fine grained permissions for this query. Into this way we
> > > >   can differentiate admin from developers[1]
> > > >
> > >
> > > the 'how' is tbd;
> >
> > I just want to check if my reading is correct and we can start to work
> > on the "how" with Jiras. If you are fine with it.
> >
> > > today we query for the user's own apps/variant:
> > >
> > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
> > >
> > > One (simple) option is: the underlying service could do a "select *
> > > from..." if the role is 'admin'
> >
> > Alright. But the query must display that some app "golum" belongs to
> > "abstractj" and another app with the same name, belongs to matzew.
> > Because is pretty likely to happen naming duplication.
> >
>
> yeah, sure. That info is already present on the PushApplication - currently
> that is just not displayed.
>
>
> >
> > >
> > >
> > > > - Create an interface on UPS to the admin, otherwise the whole
> > > >   implementation is useless.
> > > >
> > >
> > > what do you mean ?
> >
> > If you query the database for all apps created. How do you delete the
> > application "golum" created by bruno if I have 10 apps named "golum" in
> > my database?
> >
>
> Ah, ok. I was wondering you wanted to define some completely new UI :)
>
> I had something like this in mind (yes, I am not a designer :))
> http://people.apache.org/~matzew/AdminViewOnApps.png

The interface design is not a big deal. Would be nice to add some
filtering to the search:

- search by owner
- search by variant
- search by app name


>
> That's just one initial thought. Once we agree on this overall feature, I
> think we will nail the details of the 'how' in the relevant JIRA subtasks
> of AGPUSH-697.
> However I fully agree that we need to apply some tweaks to the existing UI,
> so that the owner name is visible when the 'admin' is looking at the
> "application overview" page, like in the screenshot.

Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697


>
>
> >
> > That's why I think the mininum for the UPS admin interface must be
> > defined, right
> > now, before start the whole implementation. What would you expect to see
> > when you query the whole database?
> >
>
> I thought about adding 'pagination' on the "application overview" page,
> similar like we do on the installations.
>
> -Matthias
>
>
>
> >
> > >
> > >
> > > >
> > > > >From my understanding, Keycloak will just manage these users and
> > unless
> > > > something has changed, we provide the fine grained authorization model
> > on
> > > > UPS. Like
> > > > we did in the past.
> > > >
> > >
> > > yeah, the users live in Keycloak - we somehow differentiate on the
> > > role/user if we do a "select all" or just those for the specific user
> > >
> > >
> > > >
> > > > Am I correct?
> > > >
> > > > [1] -
> > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> > > >
> > > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > > Hi,
> > > > >
> > > > > as of today, we have a single user (admin), to revisit that we have
> > > > > AGPUSH-697 (see [1]).
> > > > >
> > > > > Based on changes over the months (e.g new UI and being based on
> > > > Keycloak),
> > > > > I have updated our old spec/gist:
> > > > > https://gist.github.com/matzew/ed0055000a8347488a37
> > > > >
> > > > > Greetings,
> > > > > Matthias
> > > > >
> > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > twitter: http://twitter.com/mwessendorf
> > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > >
> > > > --
> > > >
> > > > abstractj
> > > > PGP: 0x84DC9914
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct  8 16:26:53 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 17:26:53 -0300
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
Message-ID: <20141008202653.GA70029@abstractj.org>

On 2014-10-08, Matthias Wessendorf wrote:
> On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-10-08, Matthias Wessendorf wrote:
> > > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >
> > > > If I understood correctly what we want to achieve tl;dr is:
> > > >
> > > > - Include a JPA query on UPS to list all app/variants on UPS
> > > >
> > >
> > > yes
> > >
> > >
> > > > - Introduce fine grained permissions for this query. Into this way we
> > > >   can differentiate admin from developers[1]
> > > >
> > >
> > > the 'how' is tbd;
> >
> > I just want to check if my reading is correct and we can start to work
> > on the "how" with Jiras. If you are fine with it.
> >
> > > today we query for the user's own apps/variant:
> > >
> > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
> > >
> > > One (simple) option is: the underlying service could do a "select *
> > > from..." if the role is 'admin'
> >
> > Alright. But the query must display that some app "golum" belongs to
> > "abstractj" and another app with the same name, belongs to matzew.
> > Because is pretty likely to happen naming duplication.
> >
>
> yeah, sure. That info is already present on the PushApplication - currently
> that is just not displayed.
>
>
> >
> > >
> > >
> > > > - Create an interface on UPS to the admin, otherwise the whole
> > > >   implementation is useless.
> > > >
> > >
> > > what do you mean ?
> >
> > If you query the database for all apps created. How do you delete the
> > application "golum" created by bruno if I have 10 apps named "golum" in
> > my database?
> >
>
> Ah, ok. I was wondering you wanted to define some completely new UI :)
>
> I had something like this in mind (yes, I am not a designer :))
> http://people.apache.org/~matzew/AdminViewOnApps.png

The interface design is not a big deal. Would be nice to add some
filtering to the search:

- search by owner
- search by variant
- search by app name


>
> That's just one initial thought. Once we agree on this overall feature, I
> think we will nail the details of the 'how' in the relevant JIRA subtasks
> of AGPUSH-697.
> However I fully agree that we need to apply some tweaks to the existing UI,
> so that the owner name is visible when the 'admin' is looking at the
> "application overview" page, like in the screenshot.

Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697


>
>
> >
> > That's why I think the mininum for the UPS admin interface must be
> > defined, right
> > now, before start the whole implementation. What would you expect to see
> > when you query the whole database?
> >
>
> I thought about adding 'pagination' on the "application overview" page,
> similar like we do on the installations.
>
> -Matthias
>
>
>
> >
> > >
> > >
> > > >
> > > > >From my understanding, Keycloak will just manage these users and
> > unless
> > > > something has changed, we provide the fine grained authorization model
> > on
> > > > UPS. Like
> > > > we did in the past.
> > > >
> > >
> > > yeah, the users live in Keycloak - we somehow differentiate on the
> > > role/user if we do a "select all" or just those for the specific user
> > >
> > >
> > > >
> > > > Am I correct?
> > > >
> > > > [1] -
> > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> > > >
> > > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > > Hi,
> > > > >
> > > > > as of today, we have a single user (admin), to revisit that we have
> > > > > AGPUSH-697 (see [1]).
> > > > >
> > > > > Based on changes over the months (e.g new UI and being based on
> > > > Keycloak),
> > > > > I have updated our old spec/gist:
> > > > > https://gist.github.com/matzew/ed0055000a8347488a37
> > > > >
> > > > > Greetings,
> > > > > Matthias
> > > > >
> > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > twitter: http://twitter.com/mwessendorf
> > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > >
> > > > --
> > > >
> > > > abstractj
> > > > PGP: 0x84DC9914
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914



From bruno at abstractj.org  Wed Oct  8 22:49:21 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 23:49:21 -0300
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
Message-ID: <20141009024921.GA70897@abstractj.org>

Good morning,

Today we had a meeting to discuss some of the priorities for security on
AeroGear[1]. One of the items is OAuth2 support. Currently we have
several great examples and implementations for GDrive, flows for
Keycloak and etc.

Although is a bit confuse for developers getting started from scratch.
I would like to keep our libaries aligned, considering the limitations
of each technology of course, as well consolidate each flow[2].

Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
priority at the moment. That said I have some open questions:

- Should we provide separated SDKs for OAuth2? Or let's put everything
into *-auth and break into modules later?

Note: Not only for Keycloak, but also compatible with other technologies
like passport on Node.js. In the end, OAuth2 is just a protocol and
should support other servers.

- Should we provide examples for OpenID connect? Or abstractions?

To track this issue, we have the following Jira[3] and another for
OpenID connect[4]. Fell free to link to your respective project.


[1] -
http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html

[2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1

[3] - https://issues.jboss.org/browse/AGSEC-180

[4] - https://issues.jboss.org/browse/AGSEC-190
--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct  8 22:57:20 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 8 Oct 2014 23:57:20 -0300
Subject: [aerogear-dev] Eating our own dog food, or TOTP demos for AeroGear
Message-ID: <20141009025611.GB70897@abstractj.org>

Good morning,

TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
ago. On conferences most of the developers get amazed with our API.

Although we don't have any app published on Google Play or App Store. I
think it's time to release our demos and get some feedback from our
community.

Into this way we can exercise things like:

- Properly store the shared secret
- Password protection with offline authentication
- If we are very confident, sync the TOTPs across authorized devices

At the moment, we don't need to do so much once most of our demos are
already on GH. I think it's just the matter of release it.

Thoughts?

[1] - https://github.com/aerogear/aerogear-otp-ios-demo
[2] - https://github.com/aerogear/aerogear-otp-android-demo

--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct  9 00:35:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 01:35:32 -0300
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <20141008202353.GA64806@abstractj.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
	<20141008202353.GA64806@abstractj.com>
Message-ID: <20141009043532.GA74934@abstractj.org>

For the fine grained authorization model, Keycloak already implements it
with:

@Path("bananas")
@SecurityDomain("aerogear")
public class BananaService {

    @GET
    @Produces("application/json")
    @RolesAllowed("admin")
    public List<String> getBananas() {
       return something();
    }
}

Is this the correct place to implement the query?
https://github.com/aerogear/aerogear-unifiedpush-server/blob/4641e69362ba677663f56a6c34488b705bac3de9/model/api/src/main/java/org/jboss/aerogear/unifiedpush/dao/PushApplicationDao.java


On 2014-10-08, Bruno Oliveira wrote:
> On 2014-10-08, Matthias Wessendorf wrote:
> > On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org>
> > > wrote:
> > > >
> > > > > If I understood correctly what we want to achieve tl;dr is:
> > > > >
> > > > > - Include a JPA query on UPS to list all app/variants on UPS
> > > > >
> > > >
> > > > yes
> > > >
> > > >
> > > > > - Introduce fine grained permissions for this query. Into this way we
> > > > >   can differentiate admin from developers[1]
> > > > >
> > > >
> > > > the 'how' is tbd;
> > >
> > > I just want to check if my reading is correct and we can start to work
> > > on the "how" with Jiras. If you are fine with it.
> > >
> > > > today we query for the user's own apps/variant:
> > > >
> > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
> > > >
> > > > One (simple) option is: the underlying service could do a "select *
> > > > from..." if the role is 'admin'
> > >
> > > Alright. But the query must display that some app "golum" belongs to
> > > "abstractj" and another app with the same name, belongs to matzew.
> > > Because is pretty likely to happen naming duplication.
> > >
> >
> > yeah, sure. That info is already present on the PushApplication - currently
> > that is just not displayed.
> >
> >
> > >
> > > >
> > > >
> > > > > - Create an interface on UPS to the admin, otherwise the whole
> > > > >   implementation is useless.
> > > > >
> > > >
> > > > what do you mean ?
> > >
> > > If you query the database for all apps created. How do you delete the
> > > application "golum" created by bruno if I have 10 apps named "golum" in
> > > my database?
> > >
> >
> > Ah, ok. I was wondering you wanted to define some completely new UI :)
> >
> > I had something like this in mind (yes, I am not a designer :))
> > http://people.apache.org/~matzew/AdminViewOnApps.png
>
> The interface design is not a big deal. Would be nice to add some
> filtering to the search:
>
> - search by owner
> - search by variant
> - search by app name
>
>
> >
> > That's just one initial thought. Once we agree on this overall feature, I
> > think we will nail the details of the 'how' in the relevant JIRA subtasks
> > of AGPUSH-697.
> > However I fully agree that we need to apply some tweaks to the existing UI,
> > so that the owner name is visible when the 'admin' is looking at the
> > "application overview" page, like in the screenshot.
>
> Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697
>
>
> >
> >
> > >
> > > That's why I think the mininum for the UPS admin interface must be
> > > defined, right
> > > now, before start the whole implementation. What would you expect to see
> > > when you query the whole database?
> > >
> >
> > I thought about adding 'pagination' on the "application overview" page,
> > similar like we do on the installations.
> >
> > -Matthias
> >
> >
> >
> > >
> > > >
> > > >
> > > > >
> > > > > >From my understanding, Keycloak will just manage these users and
> > > unless
> > > > > something has changed, we provide the fine grained authorization model
> > > on
> > > > > UPS. Like
> > > > > we did in the past.
> > > > >
> > > >
> > > > yeah, the users live in Keycloak - we somehow differentiate on the
> > > > role/user if we do a "select all" or just those for the specific user
> > > >
> > > >
> > > > >
> > > > > Am I correct?
> > > > >
> > > > > [1] -
> > > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> > > > >
> > > > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > > > Hi,
> > > > > >
> > > > > > as of today, we have a single user (admin), to revisit that we have
> > > > > > AGPUSH-697 (see [1]).
> > > > > >
> > > > > > Based on changes over the months (e.g new UI and being based on
> > > > > Keycloak),
> > > > > > I have updated our old spec/gist:
> > > > > > https://gist.github.com/matzew/ed0055000a8347488a37
> > > > > >
> > > > > > Greetings,
> > > > > > Matthias
> > > > > >
> > > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > >
> > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > > twitter: http://twitter.com/mwessendorf
> > > > >
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > abstractj
> > > > > PGP: 0x84DC9914
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Thu Oct  9 01:29:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 07:29:24 +0200
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <20141009025611.GB70897@abstractj.org>
References: <20141009025611.GB70897@abstractj.org>
Message-ID: <CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>

On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> ago. On conferences most of the developers get amazed with our API.
>

It's always great feedback when I show the OTP demo. Attendees at
conferences love it!


>
> Although we don't have any app published on Google Play or App Store. I
> think it's time to release our demos and get some feedback from our
> community.
>

with release, what do you mean? Submit to the stores?
On Apple one reason we never submitted anything to their App Store is their
rules clearly indicate no demos are allowed in there.


>
> Into this way we can exercise things like:
>
> - Properly store the shared secret
> - Password protection with offline authentication
> - If we are very confident, sync the TOTPs across authorized devices
>
> At the moment, we don't need to do so much once most of our demos are
> already on GH.


The only thing is perhaps making sure the backend part of our OTP demo is
(always) up :)



> I think it's just the matter of release it.
>
> Thoughts?
>

I like giving these nice demos, and their used AeroGear technology, some
more love and visibility.


>
> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> [2] - https://github.com/aerogear/aerogear-otp-android-demo
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct  9 01:30:12 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 07:30:12 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <20141009043532.GA74934@abstractj.org>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
	<20141008202353.GA64806@abstractj.com>
	<20141009043532.GA74934@abstractj.org>
Message-ID: <CAAg5f2TSmw0wgqvvhnFE-MV49N4=ReWRbwVB6Yb4y29UH3SV5g@mail.gmail.com>

On Thu, Oct 9, 2014 at 6:35 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> For the fine grained authorization model, Keycloak already implements it
> with:
>
> @Path("bananas")
> @SecurityDomain("aerogear")
> public class BananaService {
>
>     @GET
>     @Produces("application/json")
>     @RolesAllowed("admin")
>     public List<String> getBananas() {
>        return something();
>     }
> }
>
> Is this the correct place to implement the query?
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/4641e69362ba677663f56a6c34488b705bac3de9/model/api/src/main/java/org/jboss/aerogear/unifiedpush/dao/PushApplicationDao.java


yes, that is the relevant interface


>
>
>
> On 2014-10-08, Bruno Oliveira wrote:
> > On 2014-10-08, Matthias Wessendorf wrote:
> > > On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> > >
> > > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <
> bruno at abstractj.org>
> > > > wrote:
> > > > >
> > > > > > If I understood correctly what we want to achieve tl;dr is:
> > > > > >
> > > > > > - Include a JPA query on UPS to list all app/variants on UPS
> > > > > >
> > > > >
> > > > > yes
> > > > >
> > > > >
> > > > > > - Introduce fine grained permissions for this query. Into this
> way we
> > > > > >   can differentiate admin from developers[1]
> > > > > >
> > > > >
> > > > > the 'how' is tbd;
> > > >
> > > > I just want to check if my reading is correct and we can start to
> work
> > > > on the "how" with Jiras. If you are fine with it.
> > > >
> > > > > today we query for the user's own apps/variant:
> > > > >
> > > >
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
> > > > >
> > > > > One (simple) option is: the underlying service could do a "select *
> > > > > from..." if the role is 'admin'
> > > >
> > > > Alright. But the query must display that some app "golum" belongs to
> > > > "abstractj" and another app with the same name, belongs to matzew.
> > > > Because is pretty likely to happen naming duplication.
> > > >
> > >
> > > yeah, sure. That info is already present on the PushApplication -
> currently
> > > that is just not displayed.
> > >
> > >
> > > >
> > > > >
> > > > >
> > > > > > - Create an interface on UPS to the admin, otherwise the whole
> > > > > >   implementation is useless.
> > > > > >
> > > > >
> > > > > what do you mean ?
> > > >
> > > > If you query the database for all apps created. How do you delete the
> > > > application "golum" created by bruno if I have 10 apps named "golum"
> in
> > > > my database?
> > > >
> > >
> > > Ah, ok. I was wondering you wanted to define some completely new UI :)
> > >
> > > I had something like this in mind (yes, I am not a designer :))
> > > http://people.apache.org/~matzew/AdminViewOnApps.png
> >
> > The interface design is not a big deal. Would be nice to add some
> > filtering to the search:
> >
> > - search by owner
> > - search by variant
> > - search by app name
> >
> >
> > >
> > > That's just one initial thought. Once we agree on this overall
> feature, I
> > > think we will nail the details of the 'how' in the relevant JIRA
> subtasks
> > > of AGPUSH-697.
> > > However I fully agree that we need to apply some tweaks to the
> existing UI,
> > > so that the owner name is visible when the 'admin' is looking at the
> > > "application overview" page, like in the screenshot.
> >
> > Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697
> >
> >
> > >
> > >
> > > >
> > > > That's why I think the mininum for the UPS admin interface must be
> > > > defined, right
> > > > now, before start the whole implementation. What would you expect to
> see
> > > > when you query the whole database?
> > > >
> > >
> > > I thought about adding 'pagination' on the "application overview" page,
> > > similar like we do on the installations.
> > >
> > > -Matthias
> > >
> > >
> > >
> > > >
> > > > >
> > > > >
> > > > > >
> > > > > > >From my understanding, Keycloak will just manage these users and
> > > > unless
> > > > > > something has changed, we provide the fine grained authorization
> model
> > > > on
> > > > > > UPS. Like
> > > > > > we did in the past.
> > > > > >
> > > > >
> > > > > yeah, the users live in Keycloak - we somehow differentiate on the
> > > > > role/user if we do a "select all" or just those for the specific
> user
> > > > >
> > > > >
> > > > > >
> > > > > > Am I correct?
> > > > > >
> > > > > > [1] -
> > > > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> > > > > >
> > > > > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > as of today, we have a single user (admin), to revisit that we
> have
> > > > > > > AGPUSH-697 (see [1]).
> > > > > > >
> > > > > > > Based on changes over the months (e.g new UI and being based on
> > > > > > Keycloak),
> > > > > > > I have updated our old spec/gist:
> > > > > > > https://gist.github.com/matzew/ed0055000a8347488a37
> > > > > > >
> > > > > > > Greetings,
> > > > > > > Matthias
> > > > > > >
> > > > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > > > > > >
> > > > > > > --
> > > > > > > Matthias Wessendorf
> > > > > > >
> > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > > > twitter: http://twitter.com/mwessendorf
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > aerogear-dev mailing list
> > > > > > > aerogear-dev at lists.jboss.org
> > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > abstractj
> > > > > > PGP: 0x84DC9914
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > twitter: http://twitter.com/mwessendorf
> > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > >
> > > > --
> > > >
> > > > abstractj
> > > > PGP: 0x84DC9914
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct  9 01:34:09 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 07:34:09 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <20141008202353.GA64806@abstractj.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
	<20141008202353.GA64806@abstractj.com>
Message-ID: <CAAg5f2Rk_B2k-q28XkgbuaxhGfRRGQP5SZELAtCFL2+rL0VS2w@mail.gmail.com>

On Wed, Oct 8, 2014 at 10:23 PM, Bruno Oliveira <bruno at abstractj.com> wrote:

> On 2014-10-08, Matthias Wessendorf wrote:
> > On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org>
> > > wrote:
> > > >
> > > > > If I understood correctly what we want to achieve tl;dr is:
> > > > >
> > > > > - Include a JPA query on UPS to list all app/variants on UPS
> > > > >
> > > >
> > > > yes
> > > >
> > > >
> > > > > - Introduce fine grained permissions for this query. Into this way
> we
> > > > >   can differentiate admin from developers[1]
> > > > >
> > > >
> > > > the 'how' is tbd;
> > >
> > > I just want to check if my reading is correct and we can start to work
> > > on the "how" with Jiras. If you are fine with it.
> > >
> > > > today we query for the user's own apps/variant:
> > > >
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
> > > >
> > > > One (simple) option is: the underlying service could do a "select *
> > > > from..." if the role is 'admin'
> > >
> > > Alright. But the query must display that some app "golum" belongs to
> > > "abstractj" and another app with the same name, belongs to matzew.
> > > Because is pretty likely to happen naming duplication.
> > >
> >
> > yeah, sure. That info is already present on the PushApplication -
> currently
> > that is just not displayed.
> >
> >
> > >
> > > >
> > > >
> > > > > - Create an interface on UPS to the admin, otherwise the whole
> > > > >   implementation is useless.
> > > > >
> > > >
> > > > what do you mean ?
> > >
> > > If you query the database for all apps created. How do you delete the
> > > application "golum" created by bruno if I have 10 apps named "golum" in
> > > my database?
> > >
> >
> > Ah, ok. I was wondering you wanted to define some completely new UI :)
> >
> > I had something like this in mind (yes, I am not a designer :))
> > http://people.apache.org/~matzew/AdminViewOnApps.png
>
> The interface design is not a big deal. Would be nice to add some
> filtering to the search:
>
> - search by owner
> - search by variant
> - search by app name
>

regarding the search and filtering, I do see value in it, but - for timing
reasons, let's please do that only once the other stuff is really in, and
works.

I don't expect a gazillion of PushApps on one server instance, so
pagination of a few pages, sorted by "username" should be good enough



>
>
> >
> > That's just one initial thought. Once we agree on this overall feature, I
> > think we will nail the details of the 'how' in the relevant JIRA subtasks
> > of AGPUSH-697.
> > However I fully agree that we need to apply some tweaks to the existing
> UI,
> > so that the owner name is visible when the 'admin' is looking at the
> > "application overview" page, like in the screenshot.
>
> Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697
>
>
> >
> >
> > >
> > > That's why I think the mininum for the UPS admin interface must be
> > > defined, right
> > > now, before start the whole implementation. What would you expect to
> see
> > > when you query the whole database?
> > >
> >
> > I thought about adding 'pagination' on the "application overview" page,
> > similar like we do on the installations.
> >
> > -Matthias
> >
> >
> >
> > >
> > > >
> > > >
> > > > >
> > > > > >From my understanding, Keycloak will just manage these users and
> > > unless
> > > > > something has changed, we provide the fine grained authorization
> model
> > > on
> > > > > UPS. Like
> > > > > we did in the past.
> > > > >
> > > >
> > > > yeah, the users live in Keycloak - we somehow differentiate on the
> > > > role/user if we do a "select all" or just those for the specific user
> > > >
> > > >
> > > > >
> > > > > Am I correct?
> > > > >
> > > > > [1] -
> > > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
> > > > >
> > > > > On 2014-10-08, Matthias Wessendorf wrote:
> > > > > > Hi,
> > > > > >
> > > > > > as of today, we have a single user (admin), to revisit that we
> have
> > > > > > AGPUSH-697 (see [1]).
> > > > > >
> > > > > > Based on changes over the months (e.g new UI and being based on
> > > > > Keycloak),
> > > > > > I have updated our old spec/gist:
> > > > > > https://gist.github.com/matzew/ed0055000a8347488a37
> > > > > >
> > > > > > Greetings,
> > > > > > Matthias
> > > > > >
> > > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > >
> > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > > twitter: http://twitter.com/mwessendorf
> > > > >
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > abstractj
> > > > > PGP: 0x84DC9914
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Thu Oct  9 02:49:31 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 08:49:31 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <CAAg5f2Rk_B2k-q28XkgbuaxhGfRRGQP5SZELAtCFL2+rL0VS2w@mail.gmail.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
	<20141008202353.GA64806@abstractj.com>
	<CAAg5f2Rk_B2k-q28XkgbuaxhGfRRGQP5SZELAtCFL2+rL0VS2w@mail.gmail.com>
Message-ID: <CAD_dpu2L=G1ZvpqhyBcD4m3PuSYvAnJTG40oQ_qFrhX-Pzs91Q@mail.gmail.com>

On Thu, Oct 9, 2014 at 7:34 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Oct 8, 2014 at 10:23 PM, Bruno Oliveira <bruno at abstractj.com>
> wrote:
>
>> On 2014-10-08, Matthias Wessendorf wrote:
>> > On Wed, Oct 8, 2014 at 6:25 PM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>> >
>> > > On 2014-10-08, Matthias Wessendorf wrote:
>> > > > On Wed, Oct 8, 2014 at 5:34 PM, Bruno Oliveira <bruno at abstractj.org
>> >
>> > > wrote:
>> > > >
>> > > > > If I understood correctly what we want to achieve tl;dr is:
>> > > > >
>> > > > > - Include a JPA query on UPS to list all app/variants on UPS
>> > > > >
>> > > >
>> > > > yes
>> > > >
>> > > >
>> > > > > - Introduce fine grained permissions for this query. Into this
>> way we
>> > > > >   can differentiate admin from developers[1]
>> > > > >
>> > > >
>> > > > the 'how' is tbd;
>> > >
>> > > I just want to check if my reading is correct and we can start to work
>> > > on the "how" with Jiras. If you are fine with it.
>> > >
>> > > > today we query for the user's own apps/variant:
>> > > >
>> > >
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java#L88
>> > > >
>> > > > One (simple) option is: the underlying service could do a "select *
>> > > > from..." if the role is 'admin'
>> > >
>> > > Alright. But the query must display that some app "golum" belongs to
>> > > "abstractj" and another app with the same name, belongs to matzew.
>> > > Because is pretty likely to happen naming duplication.
>> > >
>> >
>> > yeah, sure. That info is already present on the PushApplication -
>> currently
>> > that is just not displayed.
>> >
>> >
>> > >
>> > > >
>> > > >
>> > > > > - Create an interface on UPS to the admin, otherwise the whole
>> > > > >   implementation is useless.
>> > > > >
>> > > >
>> > > > what do you mean ?
>> > >
>> > > If you query the database for all apps created. How do you delete the
>> > > application "golum" created by bruno if I have 10 apps named "golum"
>> in
>> > > my database?
>> > >
>> >
>> > Ah, ok. I was wondering you wanted to define some completely new UI :)
>> >
>> > I had something like this in mind (yes, I am not a designer :))
>> > http://people.apache.org/~matzew/AdminViewOnApps.png
>>
>> The interface design is not a big deal. Would be nice to add some
>> filtering to the search:
>>
>> - search by owner
>> - search by variant
>> - search by app name
>>
>
> regarding the search and filtering, I do see value in it, but - for timing
> reasons, let's please do that only once the other stuff is really in, and
> works.
>
> I don't expect a gazillion of PushApps on one server instance, so
> pagination of a few pages, sorted by "username" should be good enough
>

+1 , it's just a matter of adding "ORDER BY developer" and I think we can
reuse our pagination component from the installation page.
But indeed, for the next releases adding some filtering will be nice.

>
>
>
>>
>>
>> >
>> > That's just one initial thought. Once we agree on this overall feature,
>> I
>> > think we will nail the details of the 'how' in the relevant JIRA
>> subtasks
>> > of AGPUSH-697.
>> > However I fully agree that we need to apply some tweaks to the existing
>> UI,
>> > so that the owner name is visible when the 'admin' is looking at the
>> > "application overview" page, like in the screenshot.
>>
>> Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697
>>
>>
>> >
>> >
>> > >
>> > > That's why I think the mininum for the UPS admin interface must be
>> > > defined, right
>> > > now, before start the whole implementation. What would you expect to
>> see
>> > > when you query the whole database?
>> > >
>> >
>> > I thought about adding 'pagination' on the "application overview" page,
>> > similar like we do on the installations.
>> >
>> > -Matthias
>> >
>> >
>> >
>> > >
>> > > >
>> > > >
>> > > > >
>> > > > > >From my understanding, Keycloak will just manage these users and
>> > > unless
>> > > > > something has changed, we provide the fine grained authorization
>> model
>> > > on
>> > > > > UPS. Like
>> > > > > we did in the past.
>> > > > >
>> > > >
>> > > > yeah, the users live in Keycloak - we somehow differentiate on the
>> > > > role/user if we do a "select all" or just those for the specific
>> user
>> > > >
>> > > >
>> > > > >
>> > > > > Am I correct?
>> > > > >
>> > > > > [1] -
>> > > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
>> > > > >
>> > > > > On 2014-10-08, Matthias Wessendorf wrote:
>> > > > > > Hi,
>> > > > > >
>> > > > > > as of today, we have a single user (admin), to revisit that we
>> have
>> > > > > > AGPUSH-697 (see [1]).
>> > > > > >
>> > > > > > Based on changes over the months (e.g new UI and being based on
>> > > > > Keycloak),
>> > > > > > I have updated our old spec/gist:
>> > > > > > https://gist.github.com/matzew/ed0055000a8347488a37
>> > > > > >
>> > > > > > Greetings,
>> > > > > > Matthias
>> > > > > >
>> > > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
>> > > > > >
>> > > > > > --
>> > > > > > Matthias Wessendorf
>> > > > > >
>> > > > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > > > twitter: http://twitter.com/mwessendorf
>> > > > >
>> > > > > > _______________________________________________
>> > > > > > aerogear-dev mailing list
>> > > > > > aerogear-dev at lists.jboss.org
>> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > > > >
>> > > > > --
>> > > > >
>> > > > > abstractj
>> > > > > PGP: 0x84DC9914
>> > > > > _______________________________________________
>> > > > > aerogear-dev mailing list
>> > > > > aerogear-dev at lists.jboss.org
>> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Matthias Wessendorf
>> > > >
>> > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > twitter: http://twitter.com/mwessendorf
>> > >
>> > > > _______________________________________________
>> > > > aerogear-dev mailing list
>> > > > aerogear-dev at lists.jboss.org
>> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> > >
>> > > --
>> > >
>> > > abstractj
>> > > PGP: 0x84DC9914
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141009/55db1ede/attachment-0001.html 

From scm.blanc at gmail.com  Thu Oct  9 02:56:17 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 08:56:17 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
Message-ID: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>

Hi all,
I was thinking of that : as we are adding more and more support for Push
Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration
list is getting longer and longer in the code. What about creating a
separate json file containing this config that the plugin could consume ?

like, pushconfig.json :

 {
      pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
      android: {
        senderID: "313664704978",
        variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
        variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
      },
     ios : {
     ....
     },
     simplePush : {
     ...
     },
     microsoft : {
    ...
      },
     amazon : {
     ...
     }
}

That should not be mandatory as we could still use the "inline" style.

wdyt ?

Sebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141009/92db9b86/attachment.html 

From matzew at apache.org  Thu Oct  9 03:07:30 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 09:07:30 +0200
Subject: [aerogear-dev] Admin and Developer roles for UPS
In-Reply-To: <CAD_dpu2L=G1ZvpqhyBcD4m3PuSYvAnJTG40oQ_qFrhX-Pzs91Q@mail.gmail.com>
References: <CAAg5f2T1TbyxbFTb2uYk6ydcR-K7qEp+5SUnURCcnAoN3rBnRQ@mail.gmail.com>
	<20141008153449.GA56284@abstractj.org>
	<CAAg5f2RYM8haBn-=tA5h5J9r9kKdyUUGRKNSReQJTqJTThhzEQ@mail.gmail.com>
	<20141008162555.GC56284@abstractj.org>
	<CAAg5f2R59Q=1cv=3SByeW1pi4CvoVP4GAjzQaf7ahKvhc32THA@mail.gmail.com>
	<20141008202353.GA64806@abstractj.com>
	<CAAg5f2Rk_B2k-q28XkgbuaxhGfRRGQP5SZELAtCFL2+rL0VS2w@mail.gmail.com>
	<CAD_dpu2L=G1ZvpqhyBcD4m3PuSYvAnJTG40oQ_qFrhX-Pzs91Q@mail.gmail.com>
Message-ID: <CAAg5f2RpT-82UEggQt3AMbEvTjh0CfS9W_+GmVycH_kieEVokQ@mail.gmail.com>

On Thu, Oct 9, 2014 at 8:49 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> The interface design is not a big deal. Would be nice to add some
>>> filtering to the search:
>>>
>>> - search by owner
>>> - search by variant
>>> - search by app name
>>>
>>
>> regarding the search and filtering, I do see value in it, but - for
>> timing reasons, let's please do that only once the other stuff is really
>> in, and works.
>>
>> I don't expect a gazillion of PushApps on one server instance, so
>> pagination of a few pages, sorted by "username" should be good enough
>>
>
> +1 , it's just a matter of adding "ORDER BY developer" and I think we can
> reuse our pagination component from the installation page.
> But indeed, for the next releases adding some filtering will be nice.
>

yep, we had that as a question for 1.0.0 earlier, but agreed to not add
search/filtering due to timing. I'd not like to change that on 1.0.x

-M


>
>>
>>
>>>
>>>
>>> >
>>> > That's just one initial thought. Once we agree on this overall
>>> feature, I
>>> > think we will nail the details of the 'how' in the relevant JIRA
>>> subtasks
>>> > of AGPUSH-697.
>>> > However I fully agree that we need to apply some tweaks to the
>>> existing UI,
>>> > so that the owner name is visible when the 'admin' is looking at the
>>> > "application overview" page, like in the screenshot.
>>>
>>> Subtasks already created: https://issues.jboss.org/browse/AGPUSH-697
>>>
>>>
>>> >
>>> >
>>> > >
>>> > > That's why I think the mininum for the UPS admin interface must be
>>> > > defined, right
>>> > > now, before start the whole implementation. What would you expect to
>>> see
>>> > > when you query the whole database?
>>> > >
>>> >
>>> > I thought about adding 'pagination' on the "application overview" page,
>>> > similar like we do on the installations.
>>> >
>>> > -Matthias
>>> >
>>> >
>>> >
>>> > >
>>> > > >
>>> > > >
>>> > > > >
>>> > > > > >From my understanding, Keycloak will just manage these users and
>>> > > unless
>>> > > > > something has changed, we provide the fine grained authorization
>>> model
>>> > > on
>>> > > > > UPS. Like
>>> > > > > we did in the past.
>>> > > > >
>>> > > >
>>> > > > yeah, the users live in Keycloak - we somehow differentiate on the
>>> > > > role/user if we do a "select all" or just those for the specific
>>> user
>>> > > >
>>> > > >
>>> > > > >
>>> > > > > Am I correct?
>>> > > > >
>>> > > > > [1] -
>>> > > http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
>>> > > > >
>>> > > > > On 2014-10-08, Matthias Wessendorf wrote:
>>> > > > > > Hi,
>>> > > > > >
>>> > > > > > as of today, we have a single user (admin), to revisit that we
>>> have
>>> > > > > > AGPUSH-697 (see [1]).
>>> > > > > >
>>> > > > > > Based on changes over the months (e.g new UI and being based on
>>> > > > > Keycloak),
>>> > > > > > I have updated our old spec/gist:
>>> > > > > > https://gist.github.com/matzew/ed0055000a8347488a37
>>> > > > > >
>>> > > > > > Greetings,
>>> > > > > > Matthias
>>> > > > > >
>>> > > > > > [1] https://issues.jboss.org/browse/AGPUSH-697
>>> > > > > >
>>> > > > > > --
>>> > > > > > Matthias Wessendorf
>>> > > > > >
>>> > > > > > blog: http://matthiaswessendorf.wordpress.com/
>>> > > > > > sessions: http://www.slideshare.net/mwessendorf
>>> > > > > > twitter: http://twitter.com/mwessendorf
>>> > > > >
>>> > > > > > _______________________________________________
>>> > > > > > aerogear-dev mailing list
>>> > > > > > aerogear-dev at lists.jboss.org
>>> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > >
>>> > > > > abstractj
>>> > > > > PGP: 0x84DC9914
>>> > > > > _______________________________________________
>>> > > > > aerogear-dev mailing list
>>> > > > > aerogear-dev at lists.jboss.org
>>> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> > > > >
>>> > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > > Matthias Wessendorf
>>> > > >
>>> > > > blog: http://matthiaswessendorf.wordpress.com/
>>> > > > sessions: http://www.slideshare.net/mwessendorf
>>> > > > twitter: http://twitter.com/mwessendorf
>>> > >
>>> > > > _______________________________________________
>>> > > > aerogear-dev mailing list
>>> > > > aerogear-dev at lists.jboss.org
>>> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> > >
>>> > >
>>> > > --
>>> > >
>>> > > abstractj
>>> > > PGP: 0x84DC9914
>>> > > _______________________________________________
>>> > > aerogear-dev mailing list
>>> > > aerogear-dev at lists.jboss.org
>>> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Matthias Wessendorf
>>> >
>>> > blog: http://matthiaswessendorf.wordpress.com/
>>> > sessions: http://www.slideshare.net/mwessendorf
>>> > twitter: http://twitter.com/mwessendorf
>>>
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> --
>>>
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct  9 03:08:30 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 09:08:30 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
Message-ID: <CAAg5f2QNKBPuTp0hEBv7C999C0LRYCtQago_S94xKVV98i4w7A@mail.gmail.com>

+1000

that also means, every Cordova app, has a specific file to edit the
configuration, instead of open some random JS files

Love the idea

On Thu, Oct 9, 2014 at 8:56 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi all,
> I was thinking of that : as we are adding more and more support for Push
> Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration
> list is getting longer and longer in the code. What about creating a
> separate json file containing this config that the plugin could consume ?
>
> like, pushconfig.json :
>
>  {
>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>       android: {
>         senderID: "313664704978",
>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>       },
>      ios : {
>      ....
>      },
>      simplePush : {
>      ...
>      },
>      microsoft : {
>     ...
>       },
>      amazon : {
>      ...
>      }
> }
>
> That should not be mandatory as we could still use the "inline" style.
>
> wdyt ?
>
> 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/20141009/ac953aa2/attachment-0001.html 

From edewit at redhat.com  Thu Oct  9 03:13:37 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 9 Oct 2014 09:13:37 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
Message-ID: <5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>


Like it.

On 9 Oct,2014, at 8:56 , Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi all,
> I was thinking of that : as we are adding more and more support for Push Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration list is getting longer and longer in the code. What about creating a separate json file containing this config that the plugin could consume ?
> 
> like, pushconfig.json : 
> 
>  {
>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>       android: {
>         senderID: "313664704978",
>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>       },
>      ios : {
>      ....
>      },
>      simplePush : {
>      ...
>      },
>      microsoft : {
>     ...
>       },
>      amazon : {
>      ...
>      }
> }
> 
> That should not be mandatory as we could still use the "inline" style.
> 
> wdyt ? 
> 
> 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/20141009/472c0d16/attachment.html 

From scm.blanc at gmail.com  Thu Oct  9 03:17:12 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 09:17:12 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
Message-ID: <CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>

Cool !
Here we go then https://issues.jboss.org/browse/AGCORDOVA-34



On Thu, Oct 9, 2014 at 9:13 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

>
> Like it.
>
> On 9 Oct,2014, at 8:56 , Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> Hi all,
> I was thinking of that : as we are adding more and more support for Push
> Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration
> list is getting longer and longer in the code. What about creating a
> separate json file containing this config that the plugin could consume ?
>
> like, pushconfig.json :
>
>  {
>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>       android: {
>         senderID: "313664704978",
>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>       },
>      ios : {
>      ....
>      },
>      simplePush : {
>      ...
>      },
>      microsoft : {
>     ...
>       },
>      amazon : {
>      ...
>      }
> }
>
> That should not be mandatory as we could still use the "inline" style.
>
> wdyt ?
>
> 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/20141009/b499eac3/attachment.html 

From lukas.fryc at gmail.com  Thu Oct  9 03:58:23 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 9 Oct 2014 09:58:23 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
Message-ID: <CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>

+1 that would be very useful

We should consider allowing both approaches, in-code and in separated
config file.

On Thu, Oct 9, 2014 at 9:17 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Cool !
> Here we go then https://issues.jboss.org/browse/AGCORDOVA-34
>
>
>
> On Thu, Oct 9, 2014 at 9:13 AM, Erik Jan de Wit <edewit at redhat.com> wrote:
>
>>
>> Like it.
>>
>> On 9 Oct,2014, at 8:56 , Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>> Hi all,
>> I was thinking of that : as we are adding more and more support for Push
>> Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration
>> list is getting longer and longer in the code. What about creating a
>> separate json file containing this config that the plugin could consume ?
>>
>> like, pushconfig.json :
>>
>>  {
>>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>>       android: {
>>         senderID: "313664704978",
>>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>>       },
>>      ios : {
>>      ....
>>      },
>>      simplePush : {
>>      ...
>>      },
>>      microsoft : {
>>     ...
>>       },
>>      amazon : {
>>      ...
>>      }
>> }
>>
>> That should not be mandatory as we could still use the "inline" style.
>>
>> wdyt ?
>>
>> 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/20141009/de541ae7/attachment.html 

From scm.blanc at gmail.com  Thu Oct  9 04:18:25 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 10:18:25 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
Message-ID: <CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>

On Thu, Oct 9, 2014 at 9:58 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> +1 that would be very useful
>
> We should consider allowing both approaches, in-code and in separated
> config file.
>
Yep I mentioned that in the ticket

>
> On Thu, Oct 9, 2014 at 9:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Cool !
>> Here we go then https://issues.jboss.org/browse/AGCORDOVA-34
>>
>>
>>
>> On Thu, Oct 9, 2014 at 9:13 AM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>>
>>> Like it.
>>>
>>> On 9 Oct,2014, at 8:56 , Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>
>>> Hi all,
>>> I was thinking of that : as we are adding more and more support for Push
>>> Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration
>>> list is getting longer and longer in the code. What about creating a
>>> separate json file containing this config that the plugin could consume ?
>>>
>>> like, pushconfig.json :
>>>
>>>  {
>>>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>>>       android: {
>>>         senderID: "313664704978",
>>>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>>>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>>>       },
>>>      ios : {
>>>      ....
>>>      },
>>>      simplePush : {
>>>      ...
>>>      },
>>>      microsoft : {
>>>     ...
>>>       },
>>>      amazon : {
>>>      ...
>>>      }
>>> }
>>>
>>> That should not be mandatory as we could still use the "inline" style.
>>>
>>> wdyt ?
>>>
>>> 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/20141009/4a12e289/attachment-0001.html 

From lukas.fryc at gmail.com  Thu Oct  9 04:24:52 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 9 Oct 2014 10:24:52 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
Message-ID: <CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>

We could also externalize configs not only for Cordova, but for all
supported platforms, and then having just one tab in the UI to generate
sample config (push-config.json) for all platforms.

The location of the config can follow convention-over-configuration in
terms of platform-specific location where it should be placed.

On Thu, Oct 9, 2014 at 10:18 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> On Thu, Oct 9, 2014 at 9:58 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
>> +1 that would be very useful
>>
>> We should consider allowing both approaches, in-code and in separated
>> config file.
>>
> Yep I mentioned that in the ticket
>
>>
>> On Thu, Oct 9, 2014 at 9:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Cool !
>>> Here we go then https://issues.jboss.org/browse/AGCORDOVA-34
>>>
>>>
>>>
>>> On Thu, Oct 9, 2014 at 9:13 AM, Erik Jan de Wit <edewit at redhat.com>
>>> wrote:
>>>
>>>>
>>>> Like it.
>>>>
>>>> On 9 Oct,2014, at 8:56 , Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>>
>>>> Hi all,
>>>> I was thinking of that : as we are adding more and more support for
>>>> Push Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the
>>>> configuration list is getting longer and longer in the code. What about
>>>> creating a separate json file containing this config that the plugin could
>>>> consume ?
>>>>
>>>> like, pushconfig.json :
>>>>
>>>>  {
>>>>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>>>>       android: {
>>>>         senderID: "313664704978",
>>>>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>>>>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>>>>       },
>>>>      ios : {
>>>>      ....
>>>>      },
>>>>      simplePush : {
>>>>      ...
>>>>      },
>>>>      microsoft : {
>>>>     ...
>>>>       },
>>>>      amazon : {
>>>>      ...
>>>>      }
>>>> }
>>>>
>>>> That should not be mandatory as we could still use the "inline" style.
>>>>
>>>> wdyt ?
>>>>
>>>> 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/20141009/b0cf21d0/attachment.html 

From corinnekrych at gmail.com  Thu Oct  9 05:08:02 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 9 Oct 2014 11:08:02 +0200
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <20141009024921.GA70897@abstractj.org>
References: <20141009024921.GA70897@abstractj.org>
Message-ID: <EC4A4359-C481-4D00-9506-292C9952A902@gmail.com>


On 09 Oct 2014, at 04:49, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
> 
> Today we had a meeting to discuss some of the priorities for security on
> AeroGear[1]. One of the items is OAuth2 support. Currently we have
> several great examples and implementations for GDrive, flows for
> Keycloak and etc.
> 
> Although is a bit confuse for developers getting started from scratch.
> I would like to keep our libaries aligned, considering the limitations
> of each technology of course, as well consolidate each flow[2].
> 
> Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
> priority at the moment. That said I have some open questions:
> 
> - Should we provide separated SDKs for OAuth2? Or let's put everything
> into *-auth and break into modules later?

Eventually we plan to split aerogear-ios-oauth2 and remove the providers specific bits either moving it to a aerogear-ios-social with subspec for each providers. 
We?ve implemented with that in mind (it?s decoupled).

But with the reallity of working with Swift right now (lack of cocoa pods support, dynamic fwk issues etc?), we worked with painful github submodules and as Daniel said it all in his readme: "Now, it is even worst that our submodule also contains a submodule (sorry):? in https://github.com/danbev/aerogear-ios-sync-client#prerequisites 
and given each provider implementation is just 1 or classes, I prefer to do the split later. But yeah, planned and designed for it.

> 
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js. In the end, OAuth2 is just a protocol and
> should support other servers.

Not a protocol, a framework, one might argue.
That?s why having different providers helps to make sure we are flexible enough.
See https://tools.ietf.org/html/rfc6749#section-1.8
or http://en.wikipedia.org/wiki/OAuth#Non-interoperability
=> this is my motivation behind implementing google, fb oauth2 providers. Twitter should be next.

> 
> - Should we provide examples for OpenID connect? Or abstractions?

As always I like demos to illustrate use cases. 
Within the shoot suite demos, we have:
-  a Shootn?Share  mobile app to upload picture to Fb, Google and Keycloak, 
-  a SharedShoo web app to see all users shared pictures uploaded to Keycloak. This app required a login.
-  we can add a SharedShoot mobile app with an open id login (3 options: login as Keycloak and eventually as fb, google) to see all users pictures.

Although OpenID Connect flow is really based on Oauth authz code, some extra steps are needed. For ex, decode toke to extract user information. Provide an abstraction around how to get user infer would be nice. I have a ticket for 2.1 (October/November release).

https://issues.jboss.org/browse/AGIOS-282
https://issues.jboss.org/browse/AGIOS-287

On client side what we can also provide is a customized button for login as Facebook etc? For Keycloak it has to be a customizable one.

and? one more thing (apple way)
Do you have any ticket for SSO on native app? I have opened:
https://issues.jboss.org/browse/AGIOS-285

> 
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
> 
> 
> [1] -
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
> 
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
> 
> [3] - https://issues.jboss.org/browse/AGSEC-180
> 
> [4] - https://issues.jboss.org/browse/AGSEC-190
> ?
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From edewit at redhat.com  Thu Oct  9 05:24:09 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 9 Oct 2014 11:24:09 +0200
Subject: [aerogear-dev] hello world branch
Message-ID: <7BD8902D-946E-43F5-9212-C2D8CEB7C58C@redhat.com>

Hi,

As we already added new functionality to the hello world example ( windows support) there is a branch for the 1.0.x version. When you fix some issues be sure to specify in you PR that it should go to the 1.0.x branch as well as master!

Cheers,
	Erik Jan

From pstribny at redhat.com  Thu Oct  9 05:40:29 2014
From: pstribny at redhat.com (Petr Stribny)
Date: Thu, 9 Oct 2014 05:40:29 -0400 (EDT)
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
Message-ID: <52599073.41873004.1412847629262.JavaMail.zimbra@redhat.com>

+1, it would also make testing easier.

----- Original Message -----
From: "Luk?? Fry?" <lukas.fryc at gmail.com>
To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
Sent: Thursday, October 9, 2014 10:24:52 AM
Subject: Re: [aerogear-dev] [cordova] Push Plugin : externalise Push config

We could also externalize configs not only for Cordova, but for all supported platforms, and then having just one tab in the UI to generate sample config (push-config.json) for all platforms. 

The location of the config can follow convention-over-configuration in terms of platform-specific location where it should be placed. 

--Petr


From matzew at apache.org  Thu Oct  9 05:48:46 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 11:48:46 +0200
Subject: [aerogear-dev] [UPS] 0.10.x branches
Message-ID: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>

Hello,

since the 0.10.x series is already out dated, I'd like to kill those
related branches.
Just in case a community member needs a fix on one of the 0.10.x releases,
there are TAGs for each release. They could work on them.

Any concerns I am getting rid of them ?

-M

-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Thu Oct  9 05:53:18 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 11:53:18 +0200
Subject: [aerogear-dev] [UPS] 0.10.x branches
In-Reply-To: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
References: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
Message-ID: <CAD_dpu3-vPUr=gUCjN9Ck6r8ZTJi37Aff1g8fnP65iHaLRXC-A@mail.gmail.com>

Nuke Them !!

On Thu, Oct 9, 2014 at 11:48 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello,
>
> since the 0.10.x series is already out dated, I'd like to kill those
> related branches.
> Just in case a community member needs a fix on one of the 0.10.x releases,
> there are TAGs for each release. They could work on them.
>
> Any concerns I am getting rid of them ?
>
> -M
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20141009/c5b44d24/attachment-0001.html 

From bruno at abstractj.org  Thu Oct  9 06:57:45 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 07:57:45 -0300
Subject: [aerogear-dev] hello world branch
In-Reply-To: <7BD8902D-946E-43F5-9212-C2D8CEB7C58C@redhat.com>
References: <7BD8902D-946E-43F5-9212-C2D8CEB7C58C@redhat.com>
Message-ID: <20141009105745.GA82696@abstractj.org>

+1 with so many repositories, it's easy to skip it and commit mistakes.

More details on pull requests, less problems.

On 2014-10-09, Erik Jan de Wit wrote:
> Hi,
>
> As we already added new functionality to the hello world example ( windows support) there is a branch for the 1.0.x version. When you fix some issues be sure to specify in you PR that it should go to the 1.0.x branch as well as master!
>
> Cheers,
> 	Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Thu Oct  9 07:03:14 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 13:03:14 +0200
Subject: [aerogear-dev] hello world branch
In-Reply-To: <20141009105745.GA82696@abstractj.org>
References: <7BD8902D-946E-43F5-9212-C2D8CEB7C58C@redhat.com>
	<20141009105745.GA82696@abstractj.org>
Message-ID: <CAAg5f2RjOuAwBovgrAPPVzQmgPvZL1562iP16CmZtKb+PjdjsQ@mail.gmail.com>

On Thu, Oct 9, 2014 at 12:57 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> +1 with so many repositories, it's easy to skip it and commit mistakes.
>
> More details on pull requests, less problems.
>

Right! I think generally, we should provide a minimum of description on
each PR. Sometimes there is nothing attached (no text, no JIRA link). Hard
to do guesswork :)


>
> On 2014-10-09, Erik Jan de Wit wrote:
> > Hi,
> >
> > As we already added new functionality to the hello world example (
> windows support) there is a branch for the 1.0.x version. When you fix some
> issues be sure to specify in you PR that it should go to the 1.0.x branch
> as well as master!
> >
> > Cheers,
> >       Erik Jan
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Thu Oct  9 07:14:36 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 08:14:36 -0300
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <EC4A4359-C481-4D00-9506-292C9952A902@gmail.com>
References: <20141009024921.GA70897@abstractj.org>
	<EC4A4359-C481-4D00-9506-292C9952A902@gmail.com>
Message-ID: <20141009111436.GB82696@abstractj.org>

On 2014-10-09, Corinne Krych wrote:
>
> On 09 Oct 2014, at 04:49, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Good morning,
> >
> > Today we had a meeting to discuss some of the priorities for security on
> > AeroGear[1]. One of the items is OAuth2 support. Currently we have
> > several great examples and implementations for GDrive, flows for
> > Keycloak and etc.
> >
> > Although is a bit confuse for developers getting started from scratch.
> > I would like to keep our libaries aligned, considering the limitations
> > of each technology of course, as well consolidate each flow[2].
> >
> > Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
> > priority at the moment. That said I have some open questions:
> >
> > - Should we provide separated SDKs for OAuth2? Or let's put everything
> > into *-auth and break into modules later?
>
> Eventually we plan to split aerogear-ios-oauth2 and remove the providers specific bits either moving it to a aerogear-ios-social with subspec for each providers.
> We?ve implemented with that in mind (it?s decoupled).
>
> But with the reallity of working with Swift right now (lack of cocoa pods support, dynamic fwk issues etc?), we worked with painful github submodules and as Daniel said it all in his readme: "Now, it is even worst that our submodule also contains a submodule (sorry):? in https://github.com/danbev/aerogear-ios-sync-client#prerequisites
> and given each provider implementation is just 1 or classes, I prefer to do the split later. But yeah, planned and designed for it.

+1

>
> >
> > Note: Not only for Keycloak, but also compatible with other technologies
> > like passport on Node.js. In the end, OAuth2 is just a protocol and
> > should support other servers.
>
> Not a protocol, a framework, one might argue.

I bet you got it, to me is still a protocol
(https://tools.ietf.org/html/rfc6749#section-1.2) ;)

> That?s why having different providers helps to make sure we are flexible enough.
> See https://tools.ietf.org/html/rfc6749#section-1.8
> or http://en.wikipedia.org/wiki/OAuth#Non-interoperability
> => this is my motivation behind implementing google, fb oauth2 providers. Twitter should be next.

But social make use of OpenID connect on top of OAuth2, right? I would
like to know if we are done with these workflows
(https://gist.github.com/abstractj/04136c6df85cea5f35d1) for
iOS with Keycloak or passport for example?

I'm a little bit concerned about jump into social, before make our
libraries stable with the basics. Not sure if I'm understanding is
correct.

>
> >
> > - Should we provide examples for OpenID connect? Or abstractions?
>
> As always I like demos to illustrate use cases.
> Within the shoot suite demos, we have:
> -  a Shootn?Share  mobile app to upload picture to Fb, Google and Keycloak,
> -  a SharedShoo web app to see all users shared pictures uploaded to Keycloak. This app required a login.
> -  we can add a SharedShoot mobile app with an open id login (3 options: login as Keycloak and eventually as fb, google) to see all users pictures.

I will try these examples, and if an iOS n00b like me be sucessful. I
think everyone can. Where Shootn'Share is located? I would like to try
all the flows located here
https://gist.github.com/abstractj/04136c6df85cea5f35d1. Are the
cookbooks the right place to look?
http://aerogear.org/docs/guides/iOSCookbook/

>
> Although OpenID Connect flow is really based on Oauth authz code, some extra steps are needed. For ex, decode toke to extract user information. Provide an abstraction around how to get user infer would be nice. I have a ticket for 2.1 (October/November release).
>
> https://issues.jboss.org/browse/AGIOS-282
> https://issues.jboss.org/browse/AGIOS-287
>
> On client side what we can also provide is a customized button for login as Facebook etc? For Keycloak it has to be a customizable one.
>
> and? one more thing (apple way)
> Do you have any ticket for SSO on native app? I have opened:
> https://issues.jboss.org/browse/AGIOS-285

Thanks for all the clarification Corinne.

>
> >
> > To track this issue, we have the following Jira[3] and another for
> > OpenID connect[4]. Fell free to link to your respective project.
> >
> >
> > [1] -
> > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
> >
> > [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
> >
> > [3] - https://issues.jboss.org/browse/AGSEC-180
> >
> > [4] - https://issues.jboss.org/browse/AGSEC-190
> > ?
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From corinnekrych at gmail.com  Thu Oct  9 07:24:26 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 9 Oct 2014 13:24:26 +0200
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <EC4A4359-C481-4D00-9506-292C9952A902@gmail.com>
References: <20141009024921.GA70897@abstractj.org>
	<EC4A4359-C481-4D00-9506-292C9952A902@gmail.com>
Message-ID: <806A0FC6-E0B9-478B-8A16-BA626224A438@gmail.com>

Hi Bruno

I?ve updated your gist with some comments.

For the cookbook the place to look is:
- for iOS client: https://github.com/aerogear/aerogear-ios-cookbook/blob/swift/Shoot/README.md
- for backend: https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md

Indeed we should rename iOScookbook in aerogear.org as it?s not releated to cookbook repo. this page should be removed as it has been replaced by this one:
http://aerogear.org/docs/guides/aerogear-ios/
Let me open a JIRA for cleaning that. 

++
Corinne

On 09 Oct 2014, at 11:08, Corinne Krych <corinnekrych at gmail.com> wrote:

> 
> On 09 Oct 2014, at 04:49, Bruno Oliveira <bruno at abstractj.org> wrote:
> 
>> Good morning,
>> 
>> Today we had a meeting to discuss some of the priorities for security on
>> AeroGear[1]. One of the items is OAuth2 support. Currently we have
>> several great examples and implementations for GDrive, flows for
>> Keycloak and etc.
>> 
>> Although is a bit confuse for developers getting started from scratch.
>> I would like to keep our libaries aligned, considering the limitations
>> of each technology of course, as well consolidate each flow[2].
>> 
>> Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
>> priority at the moment. That said I have some open questions:
>> 
>> - Should we provide separated SDKs for OAuth2? Or let's put everything
>> into *-auth and break into modules later?
> 
> Eventually we plan to split aerogear-ios-oauth2 and remove the providers specific bits either moving it to a aerogear-ios-social with subspec for each providers. 
> We?ve implemented with that in mind (it?s decoupled).
> 
> But with the reallity of working with Swift right now (lack of cocoa pods support, dynamic fwk issues etc?), we worked with painful github submodules and as Daniel said it all in his readme: "Now, it is even worst that our submodule also contains a submodule (sorry):? in https://github.com/danbev/aerogear-ios-sync-client#prerequisites 
> and given each provider implementation is just 1 or classes, I prefer to do the split later. But yeah, planned and designed for it.
> 
>> 
>> Note: Not only for Keycloak, but also compatible with other technologies
>> like passport on Node.js. In the end, OAuth2 is just a protocol and
>> should support other servers.
> 
> Not a protocol, a framework, one might argue.
> That?s why having different providers helps to make sure we are flexible enough.
> See https://tools.ietf.org/html/rfc6749#section-1.8
> or http://en.wikipedia.org/wiki/OAuth#Non-interoperability
> => this is my motivation behind implementing google, fb oauth2 providers. Twitter should be next.
> 
>> 
>> - Should we provide examples for OpenID connect? Or abstractions?
> 
> As always I like demos to illustrate use cases. 
> Within the shoot suite demos, we have:
> -  a Shootn?Share  mobile app to upload picture to Fb, Google and Keycloak, 
> -  a SharedShoo web app to see all users shared pictures uploaded to Keycloak. This app required a login.
> -  we can add a SharedShoot mobile app with an open id login (3 options: login as Keycloak and eventually as fb, google) to see all users pictures.
> 
> Although OpenID Connect flow is really based on Oauth authz code, some extra steps are needed. For ex, decode toke to extract user information. Provide an abstraction around how to get user infer would be nice. I have a ticket for 2.1 (October/November release).
> 
> https://issues.jboss.org/browse/AGIOS-282
> https://issues.jboss.org/browse/AGIOS-287
> 
> On client side what we can also provide is a customized button for login as Facebook etc? For Keycloak it has to be a customizable one.
> 
> and? one more thing (apple way)
> Do you have any ticket for SSO on native app? I have opened:
> https://issues.jboss.org/browse/AGIOS-285
> 
>> 
>> To track this issue, we have the following Jira[3] and another for
>> OpenID connect[4]. Fell free to link to your respective project.
>> 
>> 
>> [1] -
>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>> 
>> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>> 
>> [3] - https://issues.jboss.org/browse/AGSEC-180
>> 
>> [4] - https://issues.jboss.org/browse/AGSEC-190
>> ?
>> 
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From supittma at redhat.com  Thu Oct  9 08:30:04 2014
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 09 Oct 2014 08:30:04 -0400
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <20141009024921.GA70897@abstractj.org>
References: <20141009024921.GA70897@abstractj.org>
Message-ID: <54367FCC.8040809@redhat.com>

On 10/08/2014 10:49 PM, Bruno Oliveira wrote:
> Good morning,
>
> Today we had a meeting to discuss some of the priorities for security on
> AeroGear[1]. One of the items is OAuth2 support. Currently we have
> several great examples and implementations for GDrive, flows for
> Keycloak and etc.
>
> Although is a bit confuse for developers getting started from scratch.
> I would like to keep our libaries aligned, considering the limitations
> of each technology of course, as well consolidate each flow[2].
>
> Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
> priority at the moment. That said I have some open questions:
>
> - Should we provide separated SDKs for OAuth2? Or let's put everything
> into *-auth and break into modules later?
*-auth should, IMHO, contain everything necessary to create an OAuth2 
connection to anything that isn't broken.  However, *-auth-facebook, 
*-auth-google, *-auth-herpDerpDeHur, etc may be useful to be full of 
convenience classes.

ON Android it may even be useful to have a *-auth-accountmanager to make 
working with Androids native token service easier.
>
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js. In the end, OAuth2 is just a protocol and
> should support other servers.
>
> - Should we provide examples for OpenID connect? Or abstractions?
>
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
>
>
> [1] -
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>
> [3] - https://issues.jboss.org/browse/AGSEC-180
>
> [4] - https://issues.jboss.org/browse/AGSEC-190
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> 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  Thu Oct  9 08:51:37 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 09:51:37 -0300
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <806A0FC6-E0B9-478B-8A16-BA626224A438@gmail.com>
References: <20141009024921.GA70897@abstractj.org>
	<EC4A4359-C481-4D00-9506-292C9952A902@gmail.com>
	<806A0FC6-E0B9-478B-8A16-BA626224A438@gmail.com>
Message-ID: <20141009125137.GA84641@abstractj.org>

Thanks a lot Corinne, will try the examples to provide a more accurate
feedback.

On 2014-10-09, Corinne Krych wrote:
> Hi Bruno
>
> I?ve updated your gist with some comments.
>
> For the cookbook the place to look is:
> - for iOS client: https://github.com/aerogear/aerogear-ios-cookbook/blob/swift/Shoot/README.md
> - for backend: https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
>
> Indeed we should rename iOScookbook in aerogear.org as it?s not releated to cookbook repo. this page should be removed as it has been replaced by this one:
> http://aerogear.org/docs/guides/aerogear-ios/
> Let me open a JIRA for cleaning that.
>
> ++
> Corinne
>
> On 09 Oct 2014, at 11:08, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> >
> > On 09 Oct 2014, at 04:49, Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> >> Good morning,
> >>
> >> Today we had a meeting to discuss some of the priorities for security on
> >> AeroGear[1]. One of the items is OAuth2 support. Currently we have
> >> several great examples and implementations for GDrive, flows for
> >> Keycloak and etc.
> >>
> >> Although is a bit confuse for developers getting started from scratch.
> >> I would like to keep our libaries aligned, considering the limitations
> >> of each technology of course, as well consolidate each flow[2].
> >>
> >> Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
> >> priority at the moment. That said I have some open questions:
> >>
> >> - Should we provide separated SDKs for OAuth2? Or let's put everything
> >> into *-auth and break into modules later?
> >
> > Eventually we plan to split aerogear-ios-oauth2 and remove the providers specific bits either moving it to a aerogear-ios-social with subspec for each providers.
> > We?ve implemented with that in mind (it?s decoupled).
> >
> > But with the reallity of working with Swift right now (lack of cocoa pods support, dynamic fwk issues etc?), we worked with painful github submodules and as Daniel said it all in his readme: "Now, it is even worst that our submodule also contains a submodule (sorry):? in https://github.com/danbev/aerogear-ios-sync-client#prerequisites
> > and given each provider implementation is just 1 or classes, I prefer to do the split later. But yeah, planned and designed for it.
> >
> >>
> >> Note: Not only for Keycloak, but also compatible with other technologies
> >> like passport on Node.js. In the end, OAuth2 is just a protocol and
> >> should support other servers.
> >
> > Not a protocol, a framework, one might argue.
> > That?s why having different providers helps to make sure we are flexible enough.
> > See https://tools.ietf.org/html/rfc6749#section-1.8
> > or http://en.wikipedia.org/wiki/OAuth#Non-interoperability
> > => this is my motivation behind implementing google, fb oauth2 providers. Twitter should be next.
> >
> >>
> >> - Should we provide examples for OpenID connect? Or abstractions?
> >
> > As always I like demos to illustrate use cases.
> > Within the shoot suite demos, we have:
> > -  a Shootn?Share  mobile app to upload picture to Fb, Google and Keycloak,
> > -  a SharedShoo web app to see all users shared pictures uploaded to Keycloak. This app required a login.
> > -  we can add a SharedShoot mobile app with an open id login (3 options: login as Keycloak and eventually as fb, google) to see all users pictures.
> >
> > Although OpenID Connect flow is really based on Oauth authz code, some extra steps are needed. For ex, decode toke to extract user information. Provide an abstraction around how to get user infer would be nice. I have a ticket for 2.1 (October/November release).
> >
> > https://issues.jboss.org/browse/AGIOS-282
> > https://issues.jboss.org/browse/AGIOS-287
> >
> > On client side what we can also provide is a customized button for login as Facebook etc? For Keycloak it has to be a customizable one.
> >
> > and? one more thing (apple way)
> > Do you have any ticket for SSO on native app? I have opened:
> > https://issues.jboss.org/browse/AGIOS-285
> >
> >>
> >> To track this issue, we have the following Jira[3] and another for
> >> OpenID connect[4]. Fell free to link to your respective project.
> >>
> >>
> >> [1] -
> >> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
> >>
> >> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
> >>
> >> [3] - https://issues.jboss.org/browse/AGSEC-180
> >>
> >> [4] - https://issues.jboss.org/browse/AGSEC-190
> >> ?
> >>
> >> abstractj
> >> PGP: 0x84DC9914
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct  9 08:55:22 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 09:55:22 -0300
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <54367FCC.8040809@redhat.com>
References: <20141009024921.GA70897@abstractj.org>
	<54367FCC.8040809@redhat.com>
Message-ID: <20141009125522.GB84641@abstractj.org>

On 2014-10-09, Summers Pittman wrote:
> On 10/08/2014 10:49 PM, Bruno Oliveira wrote:
> > Good morning,
> >
> > Today we had a meeting to discuss some of the priorities for security on
> > AeroGear[1]. One of the items is OAuth2 support. Currently we have
> > several great examples and implementations for GDrive, flows for
> > Keycloak and etc.
> >
> > Although is a bit confuse for developers getting started from scratch.
> > I would like to keep our libaries aligned, considering the limitations
> > of each technology of course, as well consolidate each flow[2].
> >
> > Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
> > priority at the moment. That said I have some open questions:
> >
> > - Should we provide separated SDKs for OAuth2? Or let's put everything
> > into *-auth and break into modules later?
> *-auth should, IMHO, contain everything necessary to create an OAuth2
> connection to anything that isn't broken.  However, *-auth-facebook,
> *-auth-google, *-auth-herpDerpDeHur, etc may be useful to be full of
> convenience classes.

I'm cool with that with we agreed on that or maybe extract these classes
later.

>
> ON Android it may even be useful to have a *-auth-accountmanager to make
> working with Androids native token service easier.

Is this something specific for Android or would be possible to have the
same concept (not implementation) on iOS/JS/Cordova?


Don't want to play the agilist here, but would be nice to contextualize
people on AG domain model. And I also understand that not everything must be
the same to all platforms.

> >
> > Note: Not only for Keycloak, but also compatible with other technologies
> > like passport on Node.js. In the end, OAuth2 is just a protocol and
> > should support other servers.
> >
> > - Should we provide examples for OpenID connect? Or abstractions?
> >
> > To track this issue, we have the following Jira[3] and another for
> > OpenID connect[4]. Fell free to link to your respective project.
> >
> >
> > [1] -
> > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
> >
> > [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
> >
> > [3] - https://issues.jboss.org/browse/AGSEC-180
> >
> > [4] - https://issues.jboss.org/browse/AGSEC-190
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > 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
PGP: 0x84DC9914

From scm.blanc at gmail.com  Thu Oct  9 09:32:27 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 15:32:27 +0200
Subject: [aerogear-dev] hello world branch
In-Reply-To: <CAAg5f2RjOuAwBovgrAPPVzQmgPvZL1562iP16CmZtKb+PjdjsQ@mail.gmail.com>
References: <7BD8902D-946E-43F5-9212-C2D8CEB7C58C@redhat.com>
	<20141009105745.GA82696@abstractj.org>
	<CAAg5f2RjOuAwBovgrAPPVzQmgPvZL1562iP16CmZtKb+PjdjsQ@mail.gmail.com>
Message-ID: <CAD_dpu0UChA8S0A3ccxjbk0hSYFw1T4U6aU-Cj=veWXxL-T8_w@mail.gmail.com>

And if the jira is mentioned in the PR (and it always should) a good way
for the merger to confirm where to merge is to check the "fix version"
attribute  values of the ticket. And so for those creating tickets : make
sure to set a fix version(s) :)


On Thu, Oct 9, 2014 at 1:03 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Thu, Oct 9, 2014 at 12:57 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> +1 with so many repositories, it's easy to skip it and commit mistakes.
>>
>> More details on pull requests, less problems.
>>
>
> Right! I think generally, we should provide a minimum of description on
> each PR. Sometimes there is nothing attached (no text, no JIRA link). Hard
> to do guesswork :)
>
>
>>
>> On 2014-10-09, Erik Jan de Wit wrote:
>> > Hi,
>> >
>> > As we already added new functionality to the hello world example (
>> windows support) there is a branch for the 1.0.x version. When you fix some
>> issues be sure to specify in you PR that it should go to the 1.0.x branch
>> as well as master!
>> >
>> > Cheers,
>> >       Erik Jan
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141009/5c0b3cba/attachment.html 

From daniel.bevenius at gmail.com  Thu Oct  9 09:39:42 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Thu, 9 Oct 2014 15:39:42 +0200
Subject: [aerogear-dev] hello world branch
In-Reply-To: <CAD_dpu0UChA8S0A3ccxjbk0hSYFw1T4U6aU-Cj=veWXxL-T8_w@mail.gmail.com>
References: <7BD8902D-946E-43F5-9212-C2D8CEB7C58C@redhat.com>
	<20141009105745.GA82696@abstractj.org>
	<CAAg5f2RjOuAwBovgrAPPVzQmgPvZL1562iP16CmZtKb+PjdjsQ@mail.gmail.com>
	<CAD_dpu0UChA8S0A3ccxjbk0hSYFw1T4U6aU-Cj=veWXxL-T8_w@mail.gmail.com>
Message-ID: <CAFJm-3HprkyTpsJvrpFyB=u2uQM=UsVqM-AqztY6T2b=A-CsCw@mail.gmail.com>

+1

On 9 October 2014 15:32, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> And if the jira is mentioned in the PR (and it always should) a good way
> for the merger to confirm where to merge is to check the "fix version"
> attribute  values of the ticket. And so for those creating tickets : make
> sure to set a fix version(s) :)
>
>
> On Thu, Oct 9, 2014 at 1:03 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Thu, Oct 9, 2014 at 12:57 PM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>>
>>> +1 with so many repositories, it's easy to skip it and commit mistakes.
>>>
>>> More details on pull requests, less problems.
>>>
>>
>> Right! I think generally, we should provide a minimum of description on
>> each PR. Sometimes there is nothing attached (no text, no JIRA link). Hard
>> to do guesswork :)
>>
>>
>>>
>>> On 2014-10-09, Erik Jan de Wit wrote:
>>> > Hi,
>>> >
>>> > As we already added new functionality to the hello world example (
>>> windows support) there is a branch for the 1.0.x version. When you fix some
>>> issues be sure to specify in you PR that it should go to the 1.0.x branch
>>> as well as master!
>>> >
>>> > Cheers,
>>> >       Erik Jan
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> --
>>>
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141009/de2780d6/attachment.html 

From sps.1431990 at gmail.com  Thu Oct  9 09:06:49 2014
From: sps.1431990 at gmail.com (infiniteloop)
Date: Thu, 9 Oct 2014 06:06:49 -0700 (PDT)
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate on remote IP
In-Reply-To: <20141001090408.GA36834@abstractj.org>
References: <1411036049385-9213.post@n5.nabble.com>
	<20141001090408.GA36834@abstractj.org>
Message-ID: <1412860009059-9381.post@n5.nabble.com>

Hi Bruno,

i disabled ssl as of now because i needed to move forward with my project.
However i am encountering a new problem. When i send push from dashboard to
all registrations, i am able to receive notifications on my devices, but
when i specify alias and try to send push, it displays push sent
successfully but push is not received on device. There is no error in the
logcat or in dashboard.

My aliases are of the form: tpal-user-2014109162544623

Can you provide some input in this regard.

Thanks



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unable-to-configure-SSL-by-self-signed-certificate-on-remote-IP-tp9213p9381.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From lholmqui at redhat.com  Thu Oct  9 09:43:52 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 9 Oct 2014 09:43:52 -0400
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
Message-ID: <A4F22873-A330-4022-9EEE-B03540548F74@redhat.com>


On Oct 9, 2014, at 2:56 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi all,
> I was thinking of that : as we are adding more and more support for Push Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration list is getting longer and longer in the code. What about creating a separate json file containing this config that the plugin could consume ?
> 
> like, pushconfig.json : 
> 
>  {
>       pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
>       android: {
>         senderID: "313664704978",
>         variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
>         variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
>       },
>      ios : {
>      ....
>      },
>      simplePush : {
>      ...
>      },
>      microsoft : {
>     ...
>       },
>      amazon : {
>      ...
>      }
> }
> 
> That should not be mandatory as we could still use the "inline" style.
> 
> wdyt ? 
> 
> 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/20141009/ff706005/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.tiff
Type: image/tiff
Size: 209680 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141009/ff706005/attachment-0001.tiff 

From scm.blanc at gmail.com  Thu Oct  9 09:54:56 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 9 Oct 2014 15:54:56 +0200
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate on remote IP
In-Reply-To: <1412860009059-9381.post@n5.nabble.com>
References: <1411036049385-9213.post@n5.nabble.com>
	<20141001090408.GA36834@abstractj.org>
	<1412860009059-9381.post@n5.nabble.com>
Message-ID: <CAD_dpu2mEX+JrTb+iG4BONfwNU-X=F78PPs3YVvELj_WDXcPwQ@mail.gmail.com>

Hi,
In the installations you can see that your device is registered as
"tpal-user-2014109162544623"
, could you also post the raw message that has been sent ? (You can grab it
from the activity panel)
Sebi

On Thu, Oct 9, 2014 at 3:06 PM, infiniteloop <sps.1431990 at gmail.com> wrote:

> Hi Bruno,
>
> i disabled ssl as of now because i needed to move forward with my project.
> However i am encountering a new problem. When i send push from dashboard to
> all registrations, i am able to receive notifications on my devices, but
> when i specify alias and try to send push, it displays push sent
> successfully but push is not received on device. There is no error in the
> logcat or in dashboard.
>
> My aliases are of the form: tpal-user-2014109162544623
>
> Can you provide some input in this regard.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Unable-to-configure-SSL-by-self-signed-certificate-on-remote-IP-tp9213p9381.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/20141009/40d5fe0e/attachment.html 

From bruno at abstractj.org  Thu Oct  9 11:20:21 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 12:20:21 -0300
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate on remote IP
In-Reply-To: <1412860009059-9381.post@n5.nabble.com>
References: <1411036049385-9213.post@n5.nabble.com>
	<20141001090408.GA36834@abstractj.org>
	<1412860009059-9381.post@n5.nabble.com>
Message-ID: <20141009152020.GA87902@abstractj.org>

Regarding the SSL, let me know if you are running on localhost or in a
VPS. Self signed certificates in production are pretty much unsafe,
unless you make sure of the confidentiality between client/server with
certificate pinning.


Regarding your another issue. Please make sure to provide more details
like:

- Application Server running
- Version of UPS
- Database: MySQL, PostgreSQL....
- Steps to reproduce

Might work to open another thread to avoid confusion.

On 2014-10-09, infiniteloop wrote:
> Hi Bruno,
>
> i disabled ssl as of now because i needed to move forward with my project.
> However i am encountering a new problem. When i send push from dashboard to
> all registrations, i am able to receive notifications on my devices, but
> when i specify alias and try to send push, it displays push sent
> successfully but push is not received on device. There is no error in the
> logcat or in dashboard.
>
> My aliases are of the form: tpal-user-2014109162544623
>
> Can you provide some input in this regard.
>
> Thanks
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unable-to-configure-SSL-by-self-signed-certificate-on-remote-IP-tp9213p9381.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
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct  9 11:26:22 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 12:26:22 -0300
Subject: [aerogear-dev] Eating our own dog food,
 or TOTP demos for AeroGear
In-Reply-To: <CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
Message-ID: <20141009152621.GA87979@abstractj.org>

On 2014-10-09, Matthias Wessendorf wrote:
> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Good morning,
> >
> > TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> > ago. On conferences most of the developers get amazed with our API.
> >
>
> It's always great feedback when I show the OTP demo. Attendees at
> conferences love it!
>
>
> >
> > Although we don't have any app published on Google Play or App Store. I
> > think it's time to release our demos and get some feedback from our
> > community.
> >
>
> with release, what do you mean? Submit to the stores?
> On Apple one reason we never submitted anything to their App Store is their
> rules clearly indicate no demos are allowed in there.

I understand, it can be a real and non paid app. Once it does not depends on
internet connection at this moment.

>
>
> >
> > Into this way we can exercise things like:
> >
> > - Properly store the shared secret
> > - Password protection with offline authentication
> > - If we are very confident, sync the TOTPs across authorized devices
> >
> > At the moment, we don't need to do so much once most of our demos are
> > already on GH.
>
>
> The only thing is perhaps making sure the backend part of our OTP demo is
> (always) up :)
>
>
>
> > I think it's just the matter of release it.
> >
> > Thoughts?
> >
>
> I like giving these nice demos, and their used AeroGear technology, some
> more love and visibility.
>
>
> >
> > [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> > [2] - https://github.com/aerogear/aerogear-otp-android-demo
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Thu Oct  9 11:30:27 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 17:30:27 +0200
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <20141009152621.GA87979@abstractj.org>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
Message-ID: <CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>

On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-10-09, Matthias Wessendorf wrote:
> > On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > Good morning,
> > >
> > > TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> > > ago. On conferences most of the developers get amazed with our API.
> > >
> >
> > It's always great feedback when I show the OTP demo. Attendees at
> > conferences love it!
> >
> >
> > >
> > > Although we don't have any app published on Google Play or App Store. I
> > > think it's time to release our demos and get some feedback from our
> > > community.
> > >
> >
> > with release, what do you mean? Submit to the stores?
> > On Apple one reason we never submitted anything to their App Store is
> their
> > rules clearly indicate no demos are allowed in there.
>
> I understand, it can be a real and non paid app. Once it does not depends
> on
> internet connection at this moment.
>

isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?


>
> >
> >
> > >
> > > Into this way we can exercise things like:
> > >
> > > - Properly store the shared secret
> > > - Password protection with offline authentication
> > > - If we are very confident, sync the TOTPs across authorized devices
> > >
> > > At the moment, we don't need to do so much once most of our demos are
> > > already on GH.
> >
> >
> > The only thing is perhaps making sure the backend part of our OTP demo is
> > (always) up :)
> >
> >
> >
> > > I think it's just the matter of release it.
> > >
> > > Thoughts?
> > >
> >
> > I like giving these nice demos, and their used AeroGear technology, some
> > more love and visibility.
> >
> >
> > >
> > > [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> > > [2] - https://github.com/aerogear/aerogear-otp-android-demo
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Thu Oct  9 11:45:44 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 12:45:44 -0300
Subject: [aerogear-dev] Admin endpoints
Message-ID: <20141009154544.GA88134@abstractj.org>

Good morning, moving forward with
https://issues.jboss.org/browse/AGPUSH-1036. What is the most
recommended approach for admin-ui.

Have separated endpoints for the admin like:

1.

@RolesAllowed("admin")
@Path("/admin/applications")
public class AdminApplicationEndpoint extends AbstractBaseEndpoint {

    @GET
    @Produces(MediaType.APPLICATION_JSON)
    public Response listAllPushApplications(){
        //queries
    }
}

Or introduce a new method inside the current PushApplicationEndpoint:

2.

    @GET
    @Produces(MediaType.APPLICATION_JSON)
    @RolesAllowed("admin")
    public Response listAllPushApplications(){
      //queries
    }
    // READ
    @GET
    @Produces(MediaType.APPLICATION_JSON)
    public Response listAllPushApplicationsByUsername(@Context HttpServletRequest request) {
        return Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
    }


If the option 2 is the correct. How the Angular.js service would look
like? Once the username is not informed as argument on
pushApplicationService.js, because for obvious reasons it can be
retrieved with HttpServletRequest.

One of my poor ideas due to my "amazing" Angular skills would be to do
something like:

    @GET
    @Produces(MediaType.APPLICATION_JSON)
    @RolesAllowed("admin")
    @Path("/all")
    public Response listAllPushApplications(){
      //queries
    }

And:

backendMod.factory('pushApplication', function ($resource) {
  return $resource('rest/applications/all/:verb', {
.....


Help?






--

abstractj
PGP: 0x84DC9914

From scm.blanc at gmail.com  Thu Oct  9 12:04:46 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Thu, 9 Oct 2014 18:04:46 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141009154544.GA88134@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
Message-ID: <FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>

Another option could be :
- no change or addition of any endpoint
-no change on the angular side 

Since the result is the same : we want a list of applications (for admin there is just no restriction on developer that owns it)
But in the service layer when retrieving the applications we check the role (do we have a method hasRole(string) ? ) to see if we add the criteria of developer.

Envoy? de mon iPhone

> Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> 
> Good morning, moving forward with
> https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> recommended approach for admin-ui.
> 
> Have separated endpoints for the admin like:
> 
> 1.
> 
> @RolesAllowed("admin")
> @Path("/admin/applications")
> public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> 
>    @GET
>    @Produces(MediaType.APPLICATION_JSON)
>    public Response listAllPushApplications(){
>        //queries
>    }
> }
> 
> Or introduce a new method inside the current PushApplicationEndpoint:
> 
> 2.
> 
>    @GET
>    @Produces(MediaType.APPLICATION_JSON)
>    @RolesAllowed("admin")
>    public Response listAllPushApplications(){
>      //queries
>    }
>    // READ
>    @GET
>    @Produces(MediaType.APPLICATION_JSON)
>    public Response listAllPushApplicationsByUsername(@Context HttpServletRequest request) {
>        return Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
>    }
> 
> 
> If the option 2 is the correct. How the Angular.js service would look
> like? Once the username is not informed as argument on
> pushApplicationService.js, because for obvious reasons it can be
> retrieved with HttpServletRequest.
> 
> One of my poor ideas due to my "amazing" Angular skills would be to do
> something like:
> 
>    @GET
>    @Produces(MediaType.APPLICATION_JSON)
>    @RolesAllowed("admin")
>    @Path("/all")
>    public Response listAllPushApplications(){
>      //queries
>    }
> 
> And:
> 
> backendMod.factory('pushApplication', function ($resource) {
>  return $resource('rest/applications/all/:verb', {
> .....
> 
> 
> Help?
> 
> 
> 
> 
> 
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From sps.1431990 at gmail.com  Thu Oct  9 12:21:34 2014
From: sps.1431990 at gmail.com (infiniteloop)
Date: Thu, 9 Oct 2014 09:21:34 -0700 (PDT)
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate on remote IP
In-Reply-To: <CAD_dpu2mEX+JrTb+iG4BONfwNU-X=F78PPs3YVvELj_WDXcPwQ@mail.gmail.com>
References: <1411036049385-9213.post@n5.nabble.com>
	<20141001090408.GA36834@abstractj.org>
	<1412860009059-9381.post@n5.nabble.com>
	<CAD_dpu2mEX+JrTb+iG4BONfwNU-X=F78PPs3YVvELj_WDXcPwQ@mail.gmail.com>
Message-ID: <1412871694958-9391.post@n5.nabble.com>

Yes i can see the registered devices in installation table.

Raw message:

{
    "ipAddress": "172.21.0.194",
    "clientIdentifier": "AeroGear UnifiedPush Console",
    "simplePush": "null",
    "alert": "hey",
    "action-category": "null",
    "sound": "default",
    "contentAvailable": false,
    "badge": -1,
    "timeToLive": -1,
    "data": {}
}

I sent this message to all the recipients, i received it on only 2/4
devices.
i get this message on console:

*[org.jboss.aerogear.unifiedpush.message.sender.GCMPushNotificationSender]
(EJB default - 7) Could not connect to service, please check!! *



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unable-to-configure-SSL-by-self-signed-certificate-on-remote-IP-tp9213p9391.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From sps.1431990 at gmail.com  Thu Oct  9 12:28:08 2014
From: sps.1431990 at gmail.com (infiniteloop)
Date: Thu, 9 Oct 2014 09:28:08 -0700 (PDT)
Subject: [aerogear-dev] Unable to configure SSL by self signed
 certificate on remote IP
In-Reply-To: <1412871694958-9391.post@n5.nabble.com>
References: <1411036049385-9213.post@n5.nabble.com>
	<20141001090408.GA36834@abstractj.org>
	<1412860009059-9381.post@n5.nabble.com>
	<CAD_dpu2mEX+JrTb+iG4BONfwNU-X=F78PPs3YVvELj_WDXcPwQ@mail.gmail.com>
	<1412871694958-9391.post@n5.nabble.com>
Message-ID: <1412872088897-9392.post@n5.nabble.com>

I am running UPS on wildfly 8 , UPS version: 1.0.0, db:mysql.

I don't exactly know the steps to reproduce the error. This behaviour is
uncertain, message is sent to few devices (Asus Zenfone 5, Moto g-1) but i
am not able to receive it on Nexus-4. However when i had only two devices
registered (Moto-g and Nexus-4), i was able to receive push on both the
devices.



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unable-to-configure-SSL-by-self-signed-certificate-on-remote-IP-tp9213p9392.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Thu Oct  9 12:37:33 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 9 Oct 2014 18:37:33 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
Message-ID: <CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>

On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com> wrote:

> Another option could be :
> - no change or addition of any endpoint
> -no change on the angular side
>
> Since the result is the same : we want a list of applications (for admin
> there is just no restriction on developer that owns it)
> But in the service layer when retrieving the applications we check the
> role (do we have a method hasRole(string) ? ) to see if we add the criteria
> of developer.
>

yeah, that;s what I had in my email from last night as well. the service
returns a list of applications.
Inside we handle the different cases:
- admin
   Select all (e.g. "select pa from PushApplication pa")
-developer
   select 'my apps' (e.g. "select pa from PushApplication pa where
pa.developer = :loginName")


-Matthias





>
> Envoy? de mon iPhone
>
> > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> >
> > Good morning, moving forward with
> > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > recommended approach for admin-ui.
> >
> > Have separated endpoints for the admin like:
> >
> > 1.
> >
> > @RolesAllowed("admin")
> > @Path("/admin/applications")
> > public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> >
> >    @GET
> >    @Produces(MediaType.APPLICATION_JSON)
> >    public Response listAllPushApplications(){
> >        //queries
> >    }
> > }
> >
> > Or introduce a new method inside the current PushApplicationEndpoint:
> >
> > 2.
> >
> >    @GET
> >    @Produces(MediaType.APPLICATION_JSON)
> >    @RolesAllowed("admin")
> >    public Response listAllPushApplications(){
> >      //queries
> >    }
> >    // READ
> >    @GET
> >    @Produces(MediaType.APPLICATION_JSON)
> >    public Response listAllPushApplicationsByUsername(@Context
> HttpServletRequest request) {
> >        return
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> >    }
> >
> >
> > If the option 2 is the correct. How the Angular.js service would look
> > like? Once the username is not informed as argument on
> > pushApplicationService.js, because for obvious reasons it can be
> > retrieved with HttpServletRequest.
> >
> > One of my poor ideas due to my "amazing" Angular skills would be to do
> > something like:
> >
> >    @GET
> >    @Produces(MediaType.APPLICATION_JSON)
> >    @RolesAllowed("admin")
> >    @Path("/all")
> >    public Response listAllPushApplications(){
> >      //queries
> >    }
> >
> > And:
> >
> > backendMod.factory('pushApplication', function ($resource) {
> >  return $resource('rest/applications/all/:verb', {
> > .....
> >
> >
> > Help?
> >
> >
> >
> >
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Thu Oct  9 15:58:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 16:58:32 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
Message-ID: <20141009195832.GC727@abstractj.org>

On 2014-10-09, Matthias Wessendorf wrote:
> On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>
> > Another option could be :
> > - no change or addition of any endpoint
> > -no change on the angular side
> >
> > Since the result is the same : we want a list of applications (for admin
> > there is just no restriction on developer that owns it)
> > But in the service layer when retrieving the applications we check the
> > role (do we have a method hasRole(string) ? ) to see if we add the criteria
> > of developer.
> >
>
> yeah, that;s what I had in my email from last night as well. the service
> returns a list of applications.

I think this is very clear to everyone and the basic principle of this
jira.

> Inside we handle the different cases:
> - admin
>    Select all (e.g. "select pa from PushApplication pa")
> -developer
>    select 'my apps' (e.g. "select pa from PushApplication pa where
> pa.developer = :loginName")

This is the recommendation from KC documentation
http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611.

So what do you guys suggest is: If I have several methods to validate
multiple roles, just add if/else all along the UPS code? And if I have a new
role, include more ifs?

I think it can be done inject the SecurityContext, have to check with
Stian and Bill. But it doesn't seem right.

>
>
> -Matthias
>
>
>
>
>
> >
> > Envoy? de mon iPhone
> >
> > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> > >
> > > Good morning, moving forward with
> > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > recommended approach for admin-ui.
> > >
> > > Have separated endpoints for the admin like:
> > >
> > > 1.
> > >
> > > @RolesAllowed("admin")
> > > @Path("/admin/applications")
> > > public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> > >
> > >    @GET
> > >    @Produces(MediaType.APPLICATION_JSON)
> > >    public Response listAllPushApplications(){
> > >        //queries
> > >    }
> > > }
> > >
> > > Or introduce a new method inside the current PushApplicationEndpoint:
> > >
> > > 2.
> > >
> > >    @GET
> > >    @Produces(MediaType.APPLICATION_JSON)
> > >    @RolesAllowed("admin")
> > >    public Response listAllPushApplications(){
> > >      //queries
> > >    }
> > >    // READ
> > >    @GET
> > >    @Produces(MediaType.APPLICATION_JSON)
> > >    public Response listAllPushApplicationsByUsername(@Context
> > HttpServletRequest request) {
> > >        return
> > Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > >    }
> > >
> > >
> > > If the option 2 is the correct. How the Angular.js service would look
> > > like? Once the username is not informed as argument on
> > > pushApplicationService.js, because for obvious reasons it can be
> > > retrieved with HttpServletRequest.
> > >
> > > One of my poor ideas due to my "amazing" Angular skills would be to do
> > > something like:
> > >
> > >    @GET
> > >    @Produces(MediaType.APPLICATION_JSON)
> > >    @RolesAllowed("admin")
> > >    @Path("/all")
> > >    public Response listAllPushApplications(){
> > >      //queries
> > >    }
> > >
> > > And:
> > >
> > > backendMod.factory('pushApplication', function ($resource) {
> > >  return $resource('rest/applications/all/:verb', {
> > > .....
> > >
> > >
> > > Help?
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct  9 16:42:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 17:42:32 -0300
Subject: [aerogear-dev] Eating our own dog food,
 or TOTP demos for AeroGear
In-Reply-To: <CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
Message-ID: <20141009204232.GA2102@abstractj.org>

No way, Matthias. OTP must be always offline. To retrieve the shared
secret, we scan the QR Code.

Maybe the iOS demo is doing it (have to revisit and confirm)[1].
On Android, I'm pretty much sure that QR Code scanning was already
implemented.

We don't need to be perfect, get what is already done, improve if
possible or release what is already done.

[1] -
https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63


On 2014-10-09, Matthias Wessendorf wrote:

> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-10-09, Matthias Wessendorf wrote:
> > > On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >
> > > > Good morning,
> > > >
> > > > TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> > > > ago. On conferences most of the developers get amazed with our API.
> > > >
> > >
> > > It's always great feedback when I show the OTP demo. Attendees at
> > > conferences love it!
> > >
> > >
> > > >
> > > > Although we don't have any app published on Google Play or App Store. I
> > > > think it's time to release our demos and get some feedback from our
> > > > community.
> > > >
> > >
> > > with release, what do you mean? Submit to the stores?
> > > On Apple one reason we never submitted anything to their App Store is
> > their
> > > rules clearly indicate no demos are allowed in there.
> >
> > I understand, it can be a real and non paid app. Once it does not depends
> > on
> > internet connection at this moment.
> >
>
> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?
>
>
> >
> > >
> > >
> > > >
> > > > Into this way we can exercise things like:
> > > >
> > > > - Properly store the shared secret
> > > > - Password protection with offline authentication
> > > > - If we are very confident, sync the TOTPs across authorized devices
> > > >
> > > > At the moment, we don't need to do so much once most of our demos are
> > > > already on GH.
> > >
> > >
> > > The only thing is perhaps making sure the backend part of our OTP demo is
> > > (always) up :)
> > >
> > >
> > >
> > > > I think it's just the matter of release it.
> > > >
> > > > Thoughts?
> > > >
> > >
> > > I like giving these nice demos, and their used AeroGear technology, some
> > > more love and visibility.
> > >
> > >
> > > >
> > > > [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> > > > [2] - https://github.com/aerogear/aerogear-otp-android-demo
> > > >
> > > > --
> > > >
> > > > abstractj
> > > > PGP: 0x84DC9914
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct  9 16:48:12 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 17:48:12 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141009195832.GC727@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
Message-ID: <20141009204811.GA2226@abstractj.org>

Tested locally here, it's pretty much possible to check the roles
programatically with
http://docs.oracle.com/javaee/6/api/javax/ws/rs/core/SecurityContext.html#isUserInRole(java.lang.String)

I'm just not sure about adding IF's all along the code.

On 2014-10-09, Bruno Oliveira wrote:
> On 2014-10-09, Matthias Wessendorf wrote:
> > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
> >
> > > Another option could be :
> > > - no change or addition of any endpoint
> > > -no change on the angular side
> > >
> > > Since the result is the same : we want a list of applications (for admin
> > > there is just no restriction on developer that owns it)
> > > But in the service layer when retrieving the applications we check the
> > > role (do we have a method hasRole(string) ? ) to see if we add the criteria
> > > of developer.
> > >
> >
> > yeah, that;s what I had in my email from last night as well. the service
> > returns a list of applications.
>
> I think this is very clear to everyone and the basic principle of this
> jira.
>
> > Inside we handle the different cases:
> > - admin
> >    Select all (e.g. "select pa from PushApplication pa")
> > -developer
> >    select 'my apps' (e.g. "select pa from PushApplication pa where
> > pa.developer = :loginName")
>
> This is the recommendation from KC documentation
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611.
>
> So what do you guys suggest is: If I have several methods to validate
> multiple roles, just add if/else all along the UPS code? And if I have a new
> role, include more ifs?
>
> I think it can be done inject the SecurityContext, have to check with
> Stian and Bill. But it doesn't seem right.
>
> >
> >
> > -Matthias
> >
> >
> >
> >
> >
> > >
> > > Envoy? de mon iPhone
> > >
> > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> > > >
> > > > Good morning, moving forward with
> > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > > recommended approach for admin-ui.
> > > >
> > > > Have separated endpoints for the admin like:
> > > >
> > > > 1.
> > > >
> > > > @RolesAllowed("admin")
> > > > @Path("/admin/applications")
> > > > public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> > > >
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    public Response listAllPushApplications(){
> > > >        //queries
> > > >    }
> > > > }
> > > >
> > > > Or introduce a new method inside the current PushApplicationEndpoint:
> > > >
> > > > 2.
> > > >
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    @RolesAllowed("admin")
> > > >    public Response listAllPushApplications(){
> > > >      //queries
> > > >    }
> > > >    // READ
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    public Response listAllPushApplicationsByUsername(@Context
> > > HttpServletRequest request) {
> > > >        return
> > > Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > >    }
> > > >
> > > >
> > > > If the option 2 is the correct. How the Angular.js service would look
> > > > like? Once the username is not informed as argument on
> > > > pushApplicationService.js, because for obvious reasons it can be
> > > > retrieved with HttpServletRequest.
> > > >
> > > > One of my poor ideas due to my "amazing" Angular skills would be to do
> > > > something like:
> > > >
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    @RolesAllowed("admin")
> > > >    @Path("/all")
> > > >    public Response listAllPushApplications(){
> > > >      //queries
> > > >    }
> > > >
> > > > And:
> > > >
> > > > backendMod.factory('pushApplication', function ($resource) {
> > > >  return $resource('rest/applications/all/:verb', {
> > > > .....
> > > >
> > > >
> > > > Help?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > abstractj
> > > > PGP: 0x84DC9914
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914

--

abstractj
PGP: 0x84DC9914

From scm.blanc at gmail.com  Thu Oct  9 16:50:08 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Thu, 9 Oct 2014 22:50:08 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141009195832.GC727@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
Message-ID: <33CDAEF3-C2A3-4D6D-B02B-54E2D0811CB3@gmail.com>



Envoy? de mon iPhone

> Le 9 oct. 2014 ? 21:58, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> 
>> On 2014-10-09, Matthias Wessendorf wrote:
>>> On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>> 
>>> Another option could be :
>>> - no change or addition of any endpoint
>>> -no change on the angular side
>>> 
>>> Since the result is the same : we want a list of applications (for admin
>>> there is just no restriction on developer that owns it)
>>> But in the service layer when retrieving the applications we check the
>>> role (do we have a method hasRole(string) ? ) to see if we add the criteria
>>> of developer.
>> 
>> yeah, that;s what I had in my email from last night as well. the service
>> returns a list of applications.
> 
> I think this is very clear to everyone and the basic principle of this
> jira.
> 
>> Inside we handle the different cases:
>> - admin
>>   Select all (e.g. "select pa from PushApplication pa")
>> -developer
>>   select 'my apps' (e.g. "select pa from PushApplication pa where
>> pa.developer = :loginName")
> 
> This is the recommendation from KC documentation
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611.
> 
> So what do you guys suggest is: If I have several methods to validate
> multiple roles, just add if/else all along the UPS code? And if I have a new
> role, include more ifs?
> 
> I think it can be done inject the SecurityContext, have to check with
> Stian and Bill. But it doesn't seem right.
I agree that our solution implies using some if/else but we have to balance that against having a new method/endpoint for each role + changing the frontend. Don't get me wrong here, I will follow the best practice regarding security/design .
> 
>> 
>> 
>> -Matthias
>> 
>> 
>> 
>> 
>> 
>>> 
>>> Envoy? de mon iPhone
>>> 
>>>> Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
>>>> 
>>>> Good morning, moving forward with
>>>> https://issues.jboss.org/browse/AGPUSH-1036. What is the most
>>>> recommended approach for admin-ui.
>>>> 
>>>> Have separated endpoints for the admin like:
>>>> 
>>>> 1.
>>>> 
>>>> @RolesAllowed("admin")
>>>> @Path("/admin/applications")
>>>> public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
>>>> 
>>>>   @GET
>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>   public Response listAllPushApplications(){
>>>>       //queries
>>>>   }
>>>> }
>>>> 
>>>> Or introduce a new method inside the current PushApplicationEndpoint:
>>>> 
>>>> 2.
>>>> 
>>>>   @GET
>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>   @RolesAllowed("admin")
>>>>   public Response listAllPushApplications(){
>>>>     //queries
>>>>   }
>>>>   // READ
>>>>   @GET
>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>   public Response listAllPushApplicationsByUsername(@Context
>>> HttpServletRequest request) {
>>>>       return
>>> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
>>>>   }
>>>> 
>>>> 
>>>> If the option 2 is the correct. How the Angular.js service would look
>>>> like? Once the username is not informed as argument on
>>>> pushApplicationService.js, because for obvious reasons it can be
>>>> retrieved with HttpServletRequest.
>>>> 
>>>> One of my poor ideas due to my "amazing" Angular skills would be to do
>>>> something like:
>>>> 
>>>>   @GET
>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>   @RolesAllowed("admin")
>>>>   @Path("/all")
>>>>   public Response listAllPushApplications(){
>>>>     //queries
>>>>   }
>>>> 
>>>> And:
>>>> 
>>>> backendMod.factory('pushApplication', function ($resource) {
>>>> return $resource('rest/applications/all/:verb', {
>>>> .....
>>>> 
>>>> 
>>>> Help?
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 
>>>> abstractj
>>>> PGP: 0x84DC9914
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> --
>> Matthias Wessendorf
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From scm.blanc at gmail.com  Thu Oct  9 16:54:41 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Thu, 9 Oct 2014 22:54:41 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141009204811.GA2226@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<20141009204811.GA2226@abstractj.org>
Message-ID: <0A586B1E-4B29-4F2E-9C89-60CD0CB7CA65@gmail.com>



Envoy? de mon iPhone

> Le 9 oct. 2014 ? 22:48, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> 
> Tested locally here, it's pretty much possible to check the roles
> programatically with
> http://docs.oracle.com/javaee/6/api/javax/ws/rs/core/SecurityContext.html#isUserInRole(java.lang.String)
> 
> I'm just not sure about adding IF's all along the code.
Seems we have replied almost synchronously :) . See my previous message , let's see what is the best option and I  would love to hear more opinions about this .
> 
>> On 2014-10-09, Bruno Oliveira wrote:
>>> On 2014-10-09, Matthias Wessendorf wrote:
>>>> On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>> 
>>>> Another option could be :
>>>> - no change or addition of any endpoint
>>>> -no change on the angular side
>>>> 
>>>> Since the result is the same : we want a list of applications (for admin
>>>> there is just no restriction on developer that owns it)
>>>> But in the service layer when retrieving the applications we check the
>>>> role (do we have a method hasRole(string) ? ) to see if we add the criteria
>>>> of developer.
>>> 
>>> yeah, that;s what I had in my email from last night as well. the service
>>> returns a list of applications.
>> 
>> I think this is very clear to everyone and the basic principle of this
>> jira.
>> 
>>> Inside we handle the different cases:
>>> - admin
>>>   Select all (e.g. "select pa from PushApplication pa")
>>> -developer
>>>   select 'my apps' (e.g. "select pa from PushApplication pa where
>>> pa.developer = :loginName")
>> 
>> This is the recommendation from KC documentation
>> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611.
>> 
>> So what do you guys suggest is: If I have several methods to validate
>> multiple roles, just add if/else all along the UPS code? And if I have a new
>> role, include more ifs?
>> 
>> I think it can be done inject the SecurityContext, have to check with
>> Stian and Bill. But it doesn't seem right.
>> 
>>> 
>>> 
>>> -Matthias
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> 
>>>> Envoy? de mon iPhone
>>>> 
>>>>> Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
>>>>> 
>>>>> Good morning, moving forward with
>>>>> https://issues.jboss.org/browse/AGPUSH-1036. What is the most
>>>>> recommended approach for admin-ui.
>>>>> 
>>>>> Have separated endpoints for the admin like:
>>>>> 
>>>>> 1.
>>>>> 
>>>>> @RolesAllowed("admin")
>>>>> @Path("/admin/applications")
>>>>> public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
>>>>> 
>>>>>   @GET
>>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>>   public Response listAllPushApplications(){
>>>>>       //queries
>>>>>   }
>>>>> }
>>>>> 
>>>>> Or introduce a new method inside the current PushApplicationEndpoint:
>>>>> 
>>>>> 2.
>>>>> 
>>>>>   @GET
>>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>>   @RolesAllowed("admin")
>>>>>   public Response listAllPushApplications(){
>>>>>     //queries
>>>>>   }
>>>>>   // READ
>>>>>   @GET
>>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>>   public Response listAllPushApplicationsByUsername(@Context
>>>> HttpServletRequest request) {
>>>>>       return
>>>> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
>>>>>   }
>>>>> 
>>>>> 
>>>>> If the option 2 is the correct. How the Angular.js service would look
>>>>> like? Once the username is not informed as argument on
>>>>> pushApplicationService.js, because for obvious reasons it can be
>>>>> retrieved with HttpServletRequest.
>>>>> 
>>>>> One of my poor ideas due to my "amazing" Angular skills would be to do
>>>>> something like:
>>>>> 
>>>>>   @GET
>>>>>   @Produces(MediaType.APPLICATION_JSON)
>>>>>   @RolesAllowed("admin")
>>>>>   @Path("/all")
>>>>>   public Response listAllPushApplications(){
>>>>>     //queries
>>>>>   }
>>>>> 
>>>>> And:
>>>>> 
>>>>> backendMod.factory('pushApplication', function ($resource) {
>>>>> return $resource('rest/applications/all/:verb', {
>>>>> .....
>>>>> 
>>>>> 
>>>>> Help?
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 
>>>>> abstractj
>>>>> PGP: 0x84DC9914
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> --
>>> Matthias Wessendorf
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> --
>> 
>> abstractj
>> PGP: 0x84DC9914
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From bruno at abstractj.org  Thu Oct  9 18:55:36 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 9 Oct 2014 19:55:36 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <33CDAEF3-C2A3-4D6D-B02B-54E2D0811CB3@gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<33CDAEF3-C2A3-4D6D-B02B-54E2D0811CB3@gmail.com>
Message-ID: <20141009225536.GA6030@abstractj.org>

Let's do a quick hangout tomorrow to discuss if possible.

On 2014-10-09, S?bastien Blanc wrote:
>
>
> Envoy? de mon iPhone
>
> > Le 9 oct. 2014 ? 21:58, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> >
> >> On 2014-10-09, Matthias Wessendorf wrote:
> >>> On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
> >>>
> >>> Another option could be :
> >>> - no change or addition of any endpoint
> >>> -no change on the angular side
> >>>
> >>> Since the result is the same : we want a list of applications (for admin
> >>> there is just no restriction on developer that owns it)
> >>> But in the service layer when retrieving the applications we check the
> >>> role (do we have a method hasRole(string) ? ) to see if we add the criteria
> >>> of developer.
> >>
> >> yeah, that;s what I had in my email from last night as well. the service
> >> returns a list of applications.
> >
> > I think this is very clear to everyone and the basic principle of this
> > jira.
> >
> >> Inside we handle the different cases:
> >> - admin
> >>   Select all (e.g. "select pa from PushApplication pa")
> >> -developer
> >>   select 'my apps' (e.g. "select pa from PushApplication pa where
> >> pa.developer = :loginName")
> >
> > This is the recommendation from KC documentation
> > http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611.
> >
> > So what do you guys suggest is: If I have several methods to validate
> > multiple roles, just add if/else all along the UPS code? And if I have a new
> > role, include more ifs?
> >
> > I think it can be done inject the SecurityContext, have to check with
> > Stian and Bill. But it doesn't seem right.
> I agree that our solution implies using some if/else but we have to balance that against having a new method/endpoint for each role + changing the frontend. Don't get me wrong here, I will follow the best practice regarding security/design .
> >
> >>
> >>
> >> -Matthias
> >>
> >>
> >>
> >>
> >>
> >>>
> >>> Envoy? de mon iPhone
> >>>
> >>>> Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a ?crit :
> >>>>
> >>>> Good morning, moving forward with
> >>>> https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> >>>> recommended approach for admin-ui.
> >>>>
> >>>> Have separated endpoints for the admin like:
> >>>>
> >>>> 1.
> >>>>
> >>>> @RolesAllowed("admin")
> >>>> @Path("/admin/applications")
> >>>> public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> >>>>
> >>>>   @GET
> >>>>   @Produces(MediaType.APPLICATION_JSON)
> >>>>   public Response listAllPushApplications(){
> >>>>       //queries
> >>>>   }
> >>>> }
> >>>>
> >>>> Or introduce a new method inside the current PushApplicationEndpoint:
> >>>>
> >>>> 2.
> >>>>
> >>>>   @GET
> >>>>   @Produces(MediaType.APPLICATION_JSON)
> >>>>   @RolesAllowed("admin")
> >>>>   public Response listAllPushApplications(){
> >>>>     //queries
> >>>>   }
> >>>>   // READ
> >>>>   @GET
> >>>>   @Produces(MediaType.APPLICATION_JSON)
> >>>>   public Response listAllPushApplicationsByUsername(@Context
> >>> HttpServletRequest request) {
> >>>>       return
> >>> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> >>>>   }
> >>>>
> >>>>
> >>>> If the option 2 is the correct. How the Angular.js service would look
> >>>> like? Once the username is not informed as argument on
> >>>> pushApplicationService.js, because for obvious reasons it can be
> >>>> retrieved with HttpServletRequest.
> >>>>
> >>>> One of my poor ideas due to my "amazing" Angular skills would be to do
> >>>> something like:
> >>>>
> >>>>   @GET
> >>>>   @Produces(MediaType.APPLICATION_JSON)
> >>>>   @RolesAllowed("admin")
> >>>>   @Path("/all")
> >>>>   public Response listAllPushApplications(){
> >>>>     //queries
> >>>>   }
> >>>>
> >>>> And:
> >>>>
> >>>> backendMod.factory('pushApplication', function ($resource) {
> >>>> return $resource('rest/applications/all/:verb', {
> >>>> .....
> >>>>
> >>>>
> >>>> Help?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> abstractj
> >>>> PGP: 0x84DC9914
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From cvasilak at gmail.com  Fri Oct 10 02:48:01 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Fri, 10 Oct 2014 09:48:01 +0300
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <20141009204232.GA2102@abstractj.org>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
Message-ID: <76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>

Hi,

answers inline

On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> No way, Matthias. OTP must be always offline. To retrieve the shared
> secret, we scan the QR Code.
> 
> Maybe the iOS demo is doing it (have to revisit and confirm)[1].
> On Android, I'm pretty much sure that QR Code scanning was already
> implemented.
> 

revisiting this, I can see indeed on iOS the shared secret is retrieved from the server and that is only the option offered. Our Android example offers both options, either from server, or using QR code scanning, so implementing the latter on our iOS demo need to be also done.

created to track it :
 https://issues.jboss.org/browse/AGIOS-289

> We don't need to be perfect, get what is already done, improve if
> possible or release what is already done.

+1 for releasing on the app store. My fear is, as Matthias said earlier, the ?demo? aspect, but with a nice description/walkthrough submission details, maybe there is chance.. and tbh I have seen far far simplest apps accepted on their store.


-
Christos



> 
> [1] -
> https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
> 
> 
> On 2014-10-09, Matthias Wessendorf wrote:
> 
>> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>> 
>>> On 2014-10-09, Matthias Wessendorf wrote:
>>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
>>> wrote:
>>>> 
>>>>> Good morning,
>>>>> 
>>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
>>>>> ago. On conferences most of the developers get amazed with our API.
>>>>> 
>>>> 
>>>> It's always great feedback when I show the OTP demo. Attendees at
>>>> conferences love it!
>>>> 
>>>> 
>>>>> 
>>>>> Although we don't have any app published on Google Play or App Store. I
>>>>> think it's time to release our demos and get some feedback from our
>>>>> community.
>>>>> 
>>>> 
>>>> with release, what do you mean? Submit to the stores?
>>>> On Apple one reason we never submitted anything to their App Store is
>>> their
>>>> rules clearly indicate no demos are allowed in there.
>>> 
>>> I understand, it can be a real and non paid app. Once it does not depends
>>> on
>>> internet connection at this moment.
>>> 
>> 
>> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?
>> 
>> 
>>> 
>>>> 
>>>> 
>>>>> 
>>>>> Into this way we can exercise things like:
>>>>> 
>>>>> - Properly store the shared secret
>>>>> - Password protection with offline authentication
>>>>> - If we are very confident, sync the TOTPs across authorized devices
>>>>> 
>>>>> At the moment, we don't need to do so much once most of our demos are
>>>>> already on GH.
>>>> 
>>>> 
>>>> The only thing is perhaps making sure the backend part of our OTP demo is
>>>> (always) up :)
>>>> 
>>>> 
>>>> 
>>>>> I think it's just the matter of release it.
>>>>> 
>>>>> Thoughts?
>>>>> 
>>>> 
>>>> I like giving these nice demos, and their used AeroGear technology, some
>>>> more love and visibility.
>>>> 
>>>> 
>>>>> 
>>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
>>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
>>>>> 
>>>>> --
>>>>> 
>>>>> abstractj
>>>>> PGP: 0x84DC9914
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Matthias Wessendorf
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> --
>>> 
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>> 
>> 
>> 
>> --
>> Matthias Wessendorf
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From corinnekrych at gmail.com  Fri Oct 10 03:00:31 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 10 Oct 2014 09:00:31 +0200
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
Message-ID: <CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>

Same here Bruno I would like to publish Shoot, in its Swift version to
apple store.
We have a ticket to enhance it with an iOS photo sharing dialog. Once this
one is done, let's submit.
For the app store I might limit it to Facebook and Google+, to start with.

++
Corinne

On 10 October 2014 08:48, Christos Vasilakis <cvasilak at gmail.com> wrote:

> Hi,
>
> answers inline
>
> On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > No way, Matthias. OTP must be always offline. To retrieve the shared
> > secret, we scan the QR Code.
> >
> > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
> > On Android, I'm pretty much sure that QR Code scanning was already
> > implemented.
> >
>
> revisiting this, I can see indeed on iOS the shared secret is retrieved
> from the server and that is only the option offered. Our Android example
> offers both options, either from server, or using QR code scanning, so
> implementing the latter on our iOS demo need to be also done.
>
> created to track it :
>  https://issues.jboss.org/browse/AGIOS-289
>
> > We don't need to be perfect, get what is already done, improve if
> > possible or release what is already done.
>
> +1 for releasing on the app store. My fear is, as Matthias said earlier,
> the ?demo? aspect, but with a nice description/walkthrough submission
> details, maybe there is chance.. and tbh I have seen far far simplest apps
> accepted on their store.
>
>
> -
> Christos
>
>
>
> >
> > [1] -
> >
> https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
> >
> >
> > On 2014-10-09, Matthias Wessendorf wrote:
> >
> >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >>
> >>> On 2014-10-09, Matthias Wessendorf wrote:
> >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
> >>> wrote:
> >>>>
> >>>>> Good morning,
> >>>>>
> >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> >>>>> ago. On conferences most of the developers get amazed with our API.
> >>>>>
> >>>>
> >>>> It's always great feedback when I show the OTP demo. Attendees at
> >>>> conferences love it!
> >>>>
> >>>>
> >>>>>
> >>>>> Although we don't have any app published on Google Play or App
> Store. I
> >>>>> think it's time to release our demos and get some feedback from our
> >>>>> community.
> >>>>>
> >>>>
> >>>> with release, what do you mean? Submit to the stores?
> >>>> On Apple one reason we never submitted anything to their App Store is
> >>> their
> >>>> rules clearly indicate no demos are allowed in there.
> >>>
> >>> I understand, it can be a real and non paid app. Once it does not
> depends
> >>> on
> >>> internet connection at this moment.
> >>>
> >>
> >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?
> >>
> >>
> >>>
> >>>>
> >>>>
> >>>>>
> >>>>> Into this way we can exercise things like:
> >>>>>
> >>>>> - Properly store the shared secret
> >>>>> - Password protection with offline authentication
> >>>>> - If we are very confident, sync the TOTPs across authorized devices
> >>>>>
> >>>>> At the moment, we don't need to do so much once most of our demos are
> >>>>> already on GH.
> >>>>
> >>>>
> >>>> The only thing is perhaps making sure the backend part of our OTP
> demo is
> >>>> (always) up :)
> >>>>
> >>>>
> >>>>
> >>>>> I think it's just the matter of release it.
> >>>>>
> >>>>> Thoughts?
> >>>>>
> >>>>
> >>>> I like giving these nice demos, and their used AeroGear technology,
> some
> >>>> more love and visibility.
> >>>>
> >>>>
> >>>>>
> >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
> >>>>>
> >>>>> --
> >>>>>
> >>>>> abstractj
> >>>>> PGP: 0x84DC9914
> >>>>> _______________________________________________
> >>>>> aerogear-dev mailing list
> >>>>> aerogear-dev at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Matthias Wessendorf
> >>>>
> >>>> blog: http://matthiaswessendorf.wordpress.com/
> >>>> sessions: http://www.slideshare.net/mwessendorf
> >>>> twitter: http://twitter.com/mwessendorf
> >>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>> --
> >>>
> >>> abstractj
> >>> PGP: 0x84DC9914
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141010/8dfdf5d1/attachment-0001.html 

From scm.blanc at gmail.com  Fri Oct 10 03:01:41 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 10 Oct 2014 09:01:41 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
Message-ID: <CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>

Hi,

Since the API Version PR  [1] has been merged we can start the work on
AGPUSH-534 to change the format of the Push message. There has been some
discussions on this thread and this gist
https://gist.github.com/sebastienblanc/8897596
Just want to be sure everyone is okay or have remarks before starting
implementing this.

Questions ?

Sebi

[1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
[2] https://issues.jboss.org/browse/AGPUSH-534

On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
>>
>>
>>
>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> here is the current format for comparison
>>>
>>> https://gist.github.com/lholmquist/8915817
>>>
>>> +1 to being more structured.
>>>
>>> one thing though,  in the current format, simplePush is not part of the
>>> message, but it's own thing
>>>
>> Yeah, that's why I put it in the config section in my first version but
>> Matzew suggested it was more part of the message payload
>>
>
>
> Nope to config; should stay its own, does not (IMO) make sense to include
> in tve message for richer platforms like Android/iOS
>
>
>>
>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>>
>>
>>
>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>
>>
>>
>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>> Hi,
>> I was looking at our current Push Message Format[1] and I was wonderimg
>> if you should not add some more structure to it, decoupling config,
>> criterias and the message itself :
>>
>>
>> {
>>   "config" : {
>>
>>      "ttl" : 3600,
>>      "content-available" : true,
>>
>>
>>
>>
>>      "simple-push": "version=123"
>>
>>   },
>>   "criteria" : {
>>
>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>
>>
>>
>>
>>       "categories" : ["someCategory", "otherCategory"],
>>
>>
>>
>>
>>       "deviceType" : ["iPad", "AndroidTablet"],
>>
>>
>>
>>
>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>
>>
>>
>>
>>   }
>>   ,
>>   "message": {
>>     "alert":"HELLO!",
>>     "sound":"default",
>>     "badge":7,
>>
>>     "someKey":"some value",
>>
>>     "anotherCustomKey":"some other value"
>>
>>   },
>>   }
>>
>> wdyt ?
>>
>>
>> interesting idea - it looks better structured.
>>
>> Re
>>
>>
>>
>
> --
> 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/20141010/852cb65c/attachment.html 

From scm.blanc at gmail.com  Fri Oct 10 03:14:29 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 10 Oct 2014 09:14:29 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
Message-ID: <CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>

Here a first question :
Do we want to change also how the Java Sender construct its message ?
Now we have a "plain" builder pattern, do we want now
message.criteria.alias("fdfd") ?
I'm not sure
Sebi


On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hi,
>
> Since the API Version PR  [1] has been merged we can start the work on
> AGPUSH-534 to change the format of the Push message. There has been some
> discussions on this thread and this gist
> https://gist.github.com/sebastienblanc/8897596
> Just want to be sure everyone is okay or have remarks before starting
> implementing this.
>
> Questions ?
>
> Sebi
>
> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
> [2] https://issues.jboss.org/browse/AGPUSH-534
>
> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>>
>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> here is the current format for comparison
>>>>
>>>> https://gist.github.com/lholmquist/8915817
>>>>
>>>> +1 to being more structured.
>>>>
>>>> one thing though,  in the current format, simplePush is not part of the
>>>> message, but it's own thing
>>>>
>>> Yeah, that's why I put it in the config section in my first version but
>>> Matzew suggested it was more part of the message payload
>>>
>>
>>
>> Nope to config; should stay its own, does not (IMO) make sense to
>> include in tve message for richer platforms like Android/iOS
>>
>>
>>>
>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>
>>>
>>>
>>>
>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>
>>>
>>>
>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>> Hi,
>>> I was looking at our current Push Message Format[1] and I was wonderimg
>>> if you should not add some more structure to it, decoupling config,
>>> criterias and the message itself :
>>>
>>>
>>> {
>>>   "config" : {
>>>
>>>      "ttl" : 3600,
>>>      "content-available" : true,
>>>
>>>
>>>
>>>
>>>      "simple-push": "version=123"
>>>
>>>   },
>>>   "criteria" : {
>>>
>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>
>>>
>>>
>>>
>>>       "categories" : ["someCategory", "otherCategory"],
>>>
>>>
>>>
>>>
>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>
>>>
>>>
>>>
>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>
>>>
>>>
>>>
>>>   }
>>>   ,
>>>   "message": {
>>>     "alert":"HELLO!",
>>>     "sound":"default",
>>>     "badge":7,
>>>
>>>     "someKey":"some value",
>>>
>>>     "anotherCustomKey":"some other value"
>>>
>>>   },
>>>   }
>>>
>>> wdyt ?
>>>
>>>
>>> interesting idea - it looks better structured.
>>>
>>> Re
>>>
>>>
>>>
>>
>> --
>> 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/20141010/a00facbd/attachment.html 

From corinnekrych at gmail.com  Fri Oct 10 03:24:56 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 10 Oct 2014 09:24:56 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
Message-ID: <39C2F10C-45B3-409A-83DD-72CE93F9DE69@gmail.com>


On 10 Oct 2014, at 09:14, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Here a first question :
> Do we want to change also how the Java Sender construct its message ?


We started a discussion here:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-message-format-change-proposal-td8977.html#a8980

Since we?re goign to issue a new version it worth thinking carefully about it and made the right changes.
@Matthias wdyt? 

> Now we have a "plain" builder pattern, do we want now   message.criteria.alias("fdfd") ? 
> I'm not sure
> Sebi
> 
> 
> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> Hi,
> 
> Since the API Version PR  [1] has been merged we can start the work on AGPUSH-534 to change the format of the Push message. There has been some discussions on this thread and this gist https://gist.github.com/sebastienblanc/8897596 
> Just want to be sure everyone is okay or have remarks before starting implementing this.
> 
> Questions ? 
> 
> Sebi
> 
> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
> [2] https://issues.jboss.org/browse/AGPUSH-534
> 
> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> 
> 
> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> here is the current format for comparison
> 
> https://gist.github.com/lholmquist/8915817
> 
> +1 to being more structured.
> 
> one thing though,  in the current format, simplePush is not part of the message, but it's own thing
> Yeah, that's why I put it in the config section in my first version but Matzew suggested it was more part of the message payload  
> 
> 
> Nope to config; should stay its own, does not (IMO) make sense to include in tve message for richer platforms like Android/iOS
>  
> 
> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
>> 
>> 
>> 
>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>> 
>> 
>> 
>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>> Hi,
>> I was looking at our current Push Message Format[1] and I was wonderimg if you should not add some more structure to it, decoupling config, criterias and the message itself : 
>> 
>> 
>> 
>> {
>>   "config" : {
>> 
>>      
>> "ttl" : 3600,
>>      "content-available" : true,
>> 
>> 
>> 
>> 
>> 
>> 
>>      "simple-push": "version=123"
>> 
>>   
>> },
>>   "criteria" : {
>> 
>>       
>> "alias" : ["user at account.com", "someone at aerogear.org", ....],
>> 
>> 
>> 
>> 
>> 
>> 
>>       "categories" : ["someCategory", "otherCategory"],
>> 
>> 
>> 
>> 
>> 
>> 
>>       "deviceType" : ["iPad", "AndroidTablet"],
>> 
>> 
>> 
>> 
>> 
>> 
>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"] 
>> 
>> 
>> 
>> 
>> 
>> 
>>   }
>>   ,
>>   "message": {
>> 
>>     "alert":"HELLO!",
>> 
>>     "sound":"default",
>> 
>>     "badge":7,
>> 
>>     
>> "someKey":"some value",
>> 
>>     
>> "anotherCustomKey":"some other value"
>> 
>>   
>> },
>>   
>> }
>> 
>> 
>> wdyt ? 
>> 
>> interesting idea - it looks better structured. 
>> 
>> Re
> 
> 
> 
> -- 
> Sent from Gmail Mobile
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From matzew at apache.org  Fri Oct 10 03:31:44 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 09:31:44 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141009195832.GC727@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
Message-ID: <CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>

On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-10-09, Matthias Wessendorf wrote:
> > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com>
> wrote:
> >
> > > Another option could be :
> > > - no change or addition of any endpoint
> > > -no change on the angular side
> > >
> > > Since the result is the same : we want a list of applications (for
> admin
> > > there is just no restriction on developer that owns it)
> > > But in the service layer when retrieving the applications we check the
> > > role (do we have a method hasRole(string) ? ) to see if we add the
> criteria
> > > of developer.
> > >
> >
> > yeah, that;s what I had in my email from last night as well. the service
> > returns a list of applications.
>
> I think this is very clear to everyone and the basic principle of this
> jira.
>
> > Inside we handle the different cases:
> > - admin
> >    Select all (e.g. "select pa from PushApplication pa")
> > -developer
> >    select 'my apps' (e.g. "select pa from PushApplication pa where
> > pa.developer = :loginName")
>
> This is the recommendation from KC documentation
>
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> .
>

I understand their example, but we don't really (within UPS) have a
completely different UI between "admin" and "developer" roles.


>
> So what do you guys suggest is: If I have several methods to validate
> multiple roles, just add if/else all along the UPS code? And if I have a
> new
> role, include more ifs?
>
> I think it can be done inject the SecurityContext, have to check with
> Stian and Bill. But it doesn't seem right.
>

might not be the most elegant, but looks like it avoids adding too much new
code. Especially since the UI for 'admin' and 'developer' is pretty much
the same.


>
> >
> >
> > -Matthias
> >
> >
> >
> >
> >
> > >
> > > Envoy? de mon iPhone
> > >
> > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
> ?crit :
> > > >
> > > > Good morning, moving forward with
> > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > > recommended approach for admin-ui.
> > > >
> > > > Have separated endpoints for the admin like:
> > > >
> > > > 1.
> > > >
> > > > @RolesAllowed("admin")
> > > > @Path("/admin/applications")
> > > > public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> > > >
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    public Response listAllPushApplications(){
> > > >        //queries
> > > >    }
> > > > }
> > > >
> > > > Or introduce a new method inside the current PushApplicationEndpoint:
> > > >
> > > > 2.
> > > >
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    @RolesAllowed("admin")
> > > >    public Response listAllPushApplications(){
> > > >      //queries
> > > >    }
> > > >    // READ
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    public Response listAllPushApplicationsByUsername(@Context
> > > HttpServletRequest request) {
> > > >        return
> > >
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > >    }
> > > >
> > > >
> > > > If the option 2 is the correct. How the Angular.js service would look
> > > > like? Once the username is not informed as argument on
> > > > pushApplicationService.js, because for obvious reasons it can be
> > > > retrieved with HttpServletRequest.
> > > >
> > > > One of my poor ideas due to my "amazing" Angular skills would be to
> do
> > > > something like:
> > > >
> > > >    @GET
> > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >    @RolesAllowed("admin")
> > > >    @Path("/all")
> > > >    public Response listAllPushApplications(){
> > > >      //queries
> > > >    }
> > > >
> > > > And:
> > > >
> > > > backendMod.factory('pushApplication', function ($resource) {
> > > >  return $resource('rest/applications/all/:verb', {
> > > > .....
> > > >
> > > >
> > > > Help?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > abstractj
> > > > PGP: 0x84DC9914
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Fri Oct 10 03:47:34 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 09:47:34 +0200
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
	<CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
Message-ID: <CAAg5f2TtG7MNOgX-YJNNDt5YeUbcJXjnR_BwYA+XzQOftJORmg@mail.gmail.com>

On Fri, Oct 10, 2014 at 9:00 AM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Same here Bruno I would like to publish Shoot, in its Swift version to
> apple store.
>

+1 that is even useful :)
so not a "demo" at all.

Great idea!


> We have a ticket to enhance it with an iOS photo sharing dialog. Once this
> one is done, let's submit.
> For the app store I might limit it to Facebook and Google+, to start with.
>
> ++
> Corinne
>
> On 10 October 2014 08:48, Christos Vasilakis <cvasilak at gmail.com> wrote:
>
>> Hi,
>>
>> answers inline
>>
>> On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>>
>> > No way, Matthias. OTP must be always offline. To retrieve the shared
>> > secret, we scan the QR Code.
>> >
>> > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
>> > On Android, I'm pretty much sure that QR Code scanning was already
>> > implemented.
>> >
>>
>> revisiting this, I can see indeed on iOS the shared secret is retrieved
>> from the server and that is only the option offered. Our Android example
>> offers both options, either from server, or using QR code scanning, so
>> implementing the latter on our iOS demo need to be also done.
>>
>> created to track it :
>>  https://issues.jboss.org/browse/AGIOS-289
>>
>> > We don't need to be perfect, get what is already done, improve if
>> > possible or release what is already done.
>>
>> +1 for releasing on the app store. My fear is, as Matthias said earlier,
>> the ?demo? aspect, but with a nice description/walkthrough submission
>> details, maybe there is chance.. and tbh I have seen far far simplest apps
>> accepted on their store.
>>
>>
>> -
>> Christos
>>
>>
>>
>> >
>> > [1] -
>> >
>> https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
>> >
>> >
>> > On 2014-10-09, Matthias Wessendorf wrote:
>> >
>> >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>> >>
>> >>> On 2014-10-09, Matthias Wessendorf wrote:
>> >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
>> >>> wrote:
>> >>>>
>> >>>>> Good morning,
>> >>>>>
>> >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
>> >>>>> ago. On conferences most of the developers get amazed with our API.
>> >>>>>
>> >>>>
>> >>>> It's always great feedback when I show the OTP demo. Attendees at
>> >>>> conferences love it!
>> >>>>
>> >>>>
>> >>>>>
>> >>>>> Although we don't have any app published on Google Play or App
>> Store. I
>> >>>>> think it's time to release our demos and get some feedback from our
>> >>>>> community.
>> >>>>>
>> >>>>
>> >>>> with release, what do you mean? Submit to the stores?
>> >>>> On Apple one reason we never submitted anything to their App Store is
>> >>> their
>> >>>> rules clearly indicate no demos are allowed in there.
>> >>>
>> >>> I understand, it can be a real and non paid app. Once it does not
>> depends
>> >>> on
>> >>> internet connection at this moment.
>> >>>
>> >>
>> >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?
>> >>
>> >>
>> >>>
>> >>>>
>> >>>>
>> >>>>>
>> >>>>> Into this way we can exercise things like:
>> >>>>>
>> >>>>> - Properly store the shared secret
>> >>>>> - Password protection with offline authentication
>> >>>>> - If we are very confident, sync the TOTPs across authorized devices
>> >>>>>
>> >>>>> At the moment, we don't need to do so much once most of our demos
>> are
>> >>>>> already on GH.
>> >>>>
>> >>>>
>> >>>> The only thing is perhaps making sure the backend part of our OTP
>> demo is
>> >>>> (always) up :)
>> >>>>
>> >>>>
>> >>>>
>> >>>>> I think it's just the matter of release it.
>> >>>>>
>> >>>>> Thoughts?
>> >>>>>
>> >>>>
>> >>>> I like giving these nice demos, and their used AeroGear technology,
>> some
>> >>>> more love and visibility.
>> >>>>
>> >>>>
>> >>>>>
>> >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
>> >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>> abstractj
>> >>>>> PGP: 0x84DC9914
>> >>>>> _______________________________________________
>> >>>>> aerogear-dev mailing list
>> >>>>> aerogear-dev at lists.jboss.org
>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Matthias Wessendorf
>> >>>>
>> >>>> blog: http://matthiaswessendorf.wordpress.com/
>> >>>> sessions: http://www.slideshare.net/mwessendorf
>> >>>> twitter: http://twitter.com/mwessendorf
>> >>>
>> >>>> _______________________________________________
>> >>>> aerogear-dev mailing list
>> >>>> aerogear-dev at lists.jboss.org
>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >>>
>> >>> --
>> >>>
>> >>> abstractj
>> >>> PGP: 0x84DC9914
>> >>> _______________________________________________
>> >>> aerogear-dev mailing list
>> >>> aerogear-dev at lists.jboss.org
>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Matthias Wessendorf
>> >>
>> >> blog: http://matthiaswessendorf.wordpress.com/
>> >> sessions: http://www.slideshare.net/mwessendorf
>> >> twitter: http://twitter.com/mwessendorf
>> >
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> > --
>> >
>> > abstractj
>> > PGP: 0x84DC9914
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From edewit at redhat.com  Fri Oct 10 07:57:19 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 10 Oct 2014 13:57:19 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
Message-ID: <C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>

On 9 Oct,2014, at 10:24 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> We could also externalize configs not only for Cordova, but for all supported platforms, and then having just one tab in the UI to generate sample config (push-config.json) for all platforms.
> 
> The location of the config can follow convention-over-configuration in terms of platform-specific location where it should be placed.

Yeah, I like that idea, having configuration like this in a separate file would be convenient for instance to test, and easily switch between a production UPS and the development instance.



From daniel.bevenius at gmail.com  Fri Oct 10 07:58:17 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 10 Oct 2014 13:58:17 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
	<C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>
Message-ID: <CAFJm-3E+-2Caz9QPkVQ=zqOGL8HU8P2y80yv=DV7mhjxAN_90g@mail.gmail.com>

+1

On 10 October 2014 13:57, Erik Jan de Wit <edewit at redhat.com> wrote:

> On 9 Oct,2014, at 10:24 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
> > We could also externalize configs not only for Cordova, but for all
> supported platforms, and then having just one tab in the UI to generate
> sample config (push-config.json) for all platforms.
> >
> > The location of the config can follow convention-over-configuration in
> terms of platform-specific location where it should be placed.
>
> Yeah, I like that idea, having configuration like this in a separate file
> would be convenient for instance to test, and easily switch between a
> production UPS and the development instance.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141010/48a19da3/attachment.html 

From corinnekrych at gmail.com  Fri Oct 10 07:59:56 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 10 Oct 2014 13:59:56 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAFJm-3E+-2Caz9QPkVQ=zqOGL8HU8P2y80yv=DV7mhjxAN_90g@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
	<C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>
	<CAFJm-3E+-2Caz9QPkVQ=zqOGL8HU8P2y80yv=DV7mhjxAN_90g@mail.gmail.com>
Message-ID: <F72CA7A9-50BD-44D3-9B4B-6D60B33896EB@gmail.com>

Dan, it reminds me what you did for contact app
https://github.com/aerogear/aerogear-push-quickstarts/blob/swift/client/contacts-mobile-ios-client-swift/Contacts/Info.plist#L12

It?s nice too to embrace platform specific config file format.
++
Corinne

On 10 Oct 2014, at 13:58, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> +1
> 
> On 10 October 2014 13:57, Erik Jan de Wit <edewit at redhat.com> wrote:
> On 9 Oct,2014, at 10:24 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> 
> > We could also externalize configs not only for Cordova, but for all supported platforms, and then having just one tab in the UI to generate sample config (push-config.json) for all platforms.
> >
> > The location of the config can follow convention-over-configuration in terms of platform-specific location where it should be placed.
> 
> Yeah, I like that idea, having configuration like this in a separate file would be convenient for instance to test, and easily switch between a production UPS and the development instance.
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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 Oct 10 08:02:14 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 10 Oct 2014 14:02:14 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <F72CA7A9-50BD-44D3-9B4B-6D60B33896EB@gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
	<C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>
	<CAFJm-3E+-2Caz9QPkVQ=zqOGL8HU8P2y80yv=DV7mhjxAN_90g@mail.gmail.com>
	<F72CA7A9-50BD-44D3-9B4B-6D60B33896EB@gmail.com>
Message-ID: <CAFJm-3ENT-Gx3QjQ4frwT5tpnwLHx9_-uCJT181LgyN5izc5Wg@mail.gmail.com>

>It?s nice too to embrace platform specific config file format.
Yep, I agree with that.

On 10 October 2014 13:59, Corinne Krych <corinnekrych at gmail.com> wrote:

> Dan, it reminds me what you did for contact app
>
> https://github.com/aerogear/aerogear-push-quickstarts/blob/swift/client/contacts-mobile-ios-client-swift/Contacts/Info.plist#L12
>
> It?s nice too to embrace platform specific config file format.
> ++
> Corinne
>
> On 10 Oct 2014, at 13:58, Daniel Bevenius <daniel.bevenius at gmail.com>
> wrote:
>
> > +1
> >
> > On 10 October 2014 13:57, Erik Jan de Wit <edewit at redhat.com> wrote:
> > On 9 Oct,2014, at 10:24 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> >
> > > We could also externalize configs not only for Cordova, but for all
> supported platforms, and then having just one tab in the UI to generate
> sample config (push-config.json) for all platforms.
> > >
> > > The location of the config can follow convention-over-configuration in
> terms of platform-specific location where it should be placed.
> >
> > Yeah, I like that idea, having configuration like this in a separate
> file would be convenient for instance to test, and easily switch between a
> production UPS and the development instance.
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.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/20141010/42b2e49f/attachment.html 

From edewit at redhat.com  Fri Oct 10 08:07:06 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 10 Oct 2014 14:07:06 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <F72CA7A9-50BD-44D3-9B4B-6D60B33896EB@gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
	<C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>
	<CAFJm-3E+-2Caz9QPkVQ=zqOGL8HU8P2y80yv=DV7mhjxAN_90g@mail.gmail.com>
	<F72CA7A9-50BD-44D3-9B4B-6D60B33896EB@gmail.com>
Message-ID: <8DB73CD2-DE0E-4ABC-9896-35EF3C91C56C@redhat.com>

> Dan, it reminds me what you did for contact app
> https://github.com/aerogear/aerogear-push-quickstarts/blob/swift/client/contacts-mobile-ios-client-swift/Contacts/Info.plist#L12
> 
> It?s nice too to embrace platform specific config file format.

Sure that makes perfect sense, as long as the setting is externalised so it?s easy to modify without rebuilding.



From matzew at apache.org  Fri Oct 10 08:07:33 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 14:07:33 +0200
Subject: [aerogear-dev] [cordova] Push Plugin : externalise Push config
In-Reply-To: <CAFJm-3ENT-Gx3QjQ4frwT5tpnwLHx9_-uCJT181LgyN5izc5Wg@mail.gmail.com>
References: <CAD_dpu2AYtOKGMgBiieGcUdXQDLWfCkVfgi5=NH0mPa96Yi2rQ@mail.gmail.com>
	<5EBB57D7-2C13-4503-8E8D-561A556BB32C@redhat.com>
	<CAD_dpu1FTihzd00QCKwJMGrcz5MkWn6SxPU8KfcgQVCiqusfpg@mail.gmail.com>
	<CAEroY35eet3A3Nybx2fU-BO_fccjDXX_rPwtP7X5NThpKh=SrQ@mail.gmail.com>
	<CAD_dpu3thT3UCQgetiB0V56+WcNnC1iY2oN-0t5TJck4o7zsBw@mail.gmail.com>
	<CAEroY34+mDU96VDAGjsFrg9GUMbi=5wVPsg9TrE2=Hgxe3Ez+w@mail.gmail.com>
	<C971D181-FFFE-43BF-A8D9-C1EAE250A826@redhat.com>
	<CAFJm-3E+-2Caz9QPkVQ=zqOGL8HU8P2y80yv=DV7mhjxAN_90g@mail.gmail.com>
	<F72CA7A9-50BD-44D3-9B4B-6D60B33896EB@gmail.com>
	<CAFJm-3ENT-Gx3QjQ4frwT5tpnwLHx9_-uCJT181LgyN5izc5Wg@mail.gmail.com>
Message-ID: <CAAg5f2T7EgQrpt0hqg1bO0uws+HVaZQfkZh77EFNvNwGqcK7sA@mail.gmail.com>

On Fri, Oct 10, 2014 at 2:02 PM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> >It?s nice too to embrace platform specific config file format.
> Yep, I agree with that.
>

nice!

PLIST for iOS and ... XML for Android ? :)


>
> On 10 October 2014 13:59, Corinne Krych <corinnekrych at gmail.com> wrote:
>
>> Dan, it reminds me what you did for contact app
>>
>> https://github.com/aerogear/aerogear-push-quickstarts/blob/swift/client/contacts-mobile-ios-client-swift/Contacts/Info.plist#L12
>>
>> It?s nice too to embrace platform specific config file format.
>> ++
>> Corinne
>>
>> On 10 Oct 2014, at 13:58, Daniel Bevenius <daniel.bevenius at gmail.com>
>> wrote:
>>
>> > +1
>> >
>> > On 10 October 2014 13:57, Erik Jan de Wit <edewit at redhat.com> wrote:
>> > On 9 Oct,2014, at 10:24 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>> >
>> > > We could also externalize configs not only for Cordova, but for all
>> supported platforms, and then having just one tab in the UI to generate
>> sample config (push-config.json) for all platforms.
>> > >
>> > > The location of the config can follow convention-over-configuration
>> in terms of platform-specific location where it should be placed.
>> >
>> > Yeah, I like that idea, having configuration like this in a separate
>> file would be convenient for instance to test, and easily switch between a
>> production UPS and the development instance.
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141010/2fa8d8fa/attachment-0001.html 

From daniel at passos.me  Fri Oct 10 08:18:49 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 10 Oct 2014 09:18:49 -0300
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <CAAg5f2TtG7MNOgX-YJNNDt5YeUbcJXjnR_BwYA+XzQOftJORmg@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
	<CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
	<CAAg5f2TtG7MNOgX-YJNNDt5YeUbcJXjnR_BwYA+XzQOftJORmg@mail.gmail.com>
Message-ID: <CAKjsGbv6+Y+skSpQNJ5n6XATtu8kMLNvfUWRBCXF7J1ZsLkN3Q@mail.gmail.com>

Hi guys,

Yep, In Android land we have secret request and qrcode scan.

1) May be is a good idea remove the secret request?

2) In related news, today we not store the secret. I think store that
before publish is a good thing to do

-- Passos


On Fri, Oct 10, 2014 at 4:47 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Fri, Oct 10, 2014 at 9:00 AM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
>
>> Same here Bruno I would like to publish Shoot, in its Swift version to
>> apple store.
>>
>
> +1 that is even useful :)
> so not a "demo" at all.
>
> Great idea!
>
>
>> We have a ticket to enhance it with an iOS photo sharing dialog. Once
>> this one is done, let's submit.
>> For the app store I might limit it to Facebook and Google+, to start with.
>>
>> ++
>> Corinne
>>
>> On 10 October 2014 08:48, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> answers inline
>>>
>>> On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>>>
>>> > No way, Matthias. OTP must be always offline. To retrieve the shared
>>> > secret, we scan the QR Code.
>>> >
>>> > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
>>> > On Android, I'm pretty much sure that QR Code scanning was already
>>> > implemented.
>>> >
>>>
>>> revisiting this, I can see indeed on iOS the shared secret is retrieved
>>> from the server and that is only the option offered. Our Android example
>>> offers both options, either from server, or using QR code scanning, so
>>> implementing the latter on our iOS demo need to be also done.
>>>
>>> created to track it :
>>>  https://issues.jboss.org/browse/AGIOS-289
>>>
>>> > We don't need to be perfect, get what is already done, improve if
>>> > possible or release what is already done.
>>>
>>> +1 for releasing on the app store. My fear is, as Matthias said earlier,
>>> the ?demo? aspect, but with a nice description/walkthrough submission
>>> details, maybe there is chance.. and tbh I have seen far far simplest apps
>>> accepted on their store.
>>>
>>>
>>> -
>>> Christos
>>>
>>>
>>>
>>> >
>>> > [1] -
>>> >
>>> https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
>>> >
>>> >
>>> > On 2014-10-09, Matthias Wessendorf wrote:
>>> >
>>> >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org>
>>> wrote:
>>> >>
>>> >>> On 2014-10-09, Matthias Wessendorf wrote:
>>> >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org
>>> >
>>> >>> wrote:
>>> >>>>
>>> >>>>> Good morning,
>>> >>>>>
>>> >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two
>>> years
>>> >>>>> ago. On conferences most of the developers get amazed with our API.
>>> >>>>>
>>> >>>>
>>> >>>> It's always great feedback when I show the OTP demo. Attendees at
>>> >>>> conferences love it!
>>> >>>>
>>> >>>>
>>> >>>>>
>>> >>>>> Although we don't have any app published on Google Play or App
>>> Store. I
>>> >>>>> think it's time to release our demos and get some feedback from our
>>> >>>>> community.
>>> >>>>>
>>> >>>>
>>> >>>> with release, what do you mean? Submit to the stores?
>>> >>>> On Apple one reason we never submitted anything to their App Store
>>> is
>>> >>> their
>>> >>>> rules clearly indicate no demos are allowed in there.
>>> >>>
>>> >>> I understand, it can be a real and non paid app. Once it does not
>>> depends
>>> >>> on
>>> >>> internet connection at this moment.
>>> >>>
>>> >>
>>> >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the
>>> tokens?
>>> >>
>>> >>
>>> >>>
>>> >>>>
>>> >>>>
>>> >>>>>
>>> >>>>> Into this way we can exercise things like:
>>> >>>>>
>>> >>>>> - Properly store the shared secret
>>> >>>>> - Password protection with offline authentication
>>> >>>>> - If we are very confident, sync the TOTPs across authorized
>>> devices
>>> >>>>>
>>> >>>>> At the moment, we don't need to do so much once most of our demos
>>> are
>>> >>>>> already on GH.
>>> >>>>
>>> >>>>
>>> >>>> The only thing is perhaps making sure the backend part of our OTP
>>> demo is
>>> >>>> (always) up :)
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>> I think it's just the matter of release it.
>>> >>>>>
>>> >>>>> Thoughts?
>>> >>>>>
>>> >>>>
>>> >>>> I like giving these nice demos, and their used AeroGear technology,
>>> some
>>> >>>> more love and visibility.
>>> >>>>
>>> >>>>
>>> >>>>>
>>> >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
>>> >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
>>> >>>>>
>>> >>>>> --
>>> >>>>>
>>> >>>>> abstractj
>>> >>>>> PGP: 0x84DC9914
>>> >>>>> _______________________________________________
>>> >>>>> aerogear-dev mailing list
>>> >>>>> aerogear-dev at lists.jboss.org
>>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> Matthias Wessendorf
>>> >>>>
>>> >>>> blog: http://matthiaswessendorf.wordpress.com/
>>> >>>> sessions: http://www.slideshare.net/mwessendorf
>>> >>>> twitter: http://twitter.com/mwessendorf
>>> >>>
>>> >>>> _______________________________________________
>>> >>>> aerogear-dev mailing list
>>> >>>> aerogear-dev at lists.jboss.org
>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>
>>> >>>
>>> >>> --
>>> >>>
>>> >>> abstractj
>>> >>> PGP: 0x84DC9914
>>> >>> _______________________________________________
>>> >>> aerogear-dev mailing list
>>> >>> aerogear-dev at lists.jboss.org
>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Matthias Wessendorf
>>> >>
>>> >> blog: http://matthiaswessendorf.wordpress.com/
>>> >> sessions: http://www.slideshare.net/mwessendorf
>>> >> twitter: http://twitter.com/mwessendorf
>>> >
>>> >> _______________________________________________
>>> >> aerogear-dev mailing list
>>> >> aerogear-dev at lists.jboss.org
>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> > --
>>> >
>>> > abstractj
>>> > PGP: 0x84DC9914
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20141010/a192321a/attachment.html 

From edewit at redhat.com  Fri Oct 10 08:41:17 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 10 Oct 2014 14:41:17 +0200
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <CAKjsGbv6+Y+skSpQNJ5n6XATtu8kMLNvfUWRBCXF7J1ZsLkN3Q@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
	<CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
	<CAAg5f2TtG7MNOgX-YJNNDt5YeUbcJXjnR_BwYA+XzQOftJORmg@mail.gmail.com>
	<CAKjsGbv6+Y+skSpQNJ5n6XATtu8kMLNvfUWRBCXF7J1ZsLkN3Q@mail.gmail.com>
Message-ID: <FB681C56-C065-455C-BC0D-992B7C17BF60@redhat.com>

Hi,

People should use cordova, as is supports the qrcode scan and stores the shared secret for iOS and android.

Cheers,
	Erik Jan

From bruno at abstractj.org  Fri Oct 10 09:20:07 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 10:20:07 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
Message-ID: <20141010132006.GA10563@abstractj.org>

Well it's your call, even if I don't like the design.

On 2014-10-10, Matthias Wessendorf wrote:
> On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-10-09, Matthias Wessendorf wrote:
> > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com>
> > wrote:
> > >
> > > > Another option could be :
> > > > - no change or addition of any endpoint
> > > > -no change on the angular side
> > > >
> > > > Since the result is the same : we want a list of applications (for
> > admin
> > > > there is just no restriction on developer that owns it)
> > > > But in the service layer when retrieving the applications we check the
> > > > role (do we have a method hasRole(string) ? ) to see if we add the
> > criteria
> > > > of developer.
> > > >
> > >
> > > yeah, that;s what I had in my email from last night as well. the service
> > > returns a list of applications.
> >
> > I think this is very clear to everyone and the basic principle of this
> > jira.
> >
> > > Inside we handle the different cases:
> > > - admin
> > >    Select all (e.g. "select pa from PushApplication pa")
> > > -developer
> > >    select 'my apps' (e.g. "select pa from PushApplication pa where
> > > pa.developer = :loginName")
> >
> > This is the recommendation from KC documentation
> >
> > http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > .
> >
>
> I understand their example, but we don't really (within UPS) have a
> completely different UI between "admin" and "developer" roles.
>
>
> >
> > So what do you guys suggest is: If I have several methods to validate
> > multiple roles, just add if/else all along the UPS code? And if I have a
> > new
> > role, include more ifs?
> >
> > I think it can be done inject the SecurityContext, have to check with
> > Stian and Bill. But it doesn't seem right.
> >
>
> might not be the most elegant, but looks like it avoids adding too much new
> code. Especially since the UI for 'admin' and 'developer' is pretty much
> the same.
>
>
> >
> > >
> > >
> > > -Matthias
> > >
> > >
> > >
> > >
> > >
> > > >
> > > > Envoy? de mon iPhone
> > > >
> > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
> > ?crit :
> > > > >
> > > > > Good morning, moving forward with
> > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > > > recommended approach for admin-ui.
> > > > >
> > > > > Have separated endpoints for the admin like:
> > > > >
> > > > > 1.
> > > > >
> > > > > @RolesAllowed("admin")
> > > > > @Path("/admin/applications")
> > > > > public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> > > > >
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    public Response listAllPushApplications(){
> > > > >        //queries
> > > > >    }
> > > > > }
> > > > >
> > > > > Or introduce a new method inside the current PushApplicationEndpoint:
> > > > >
> > > > > 2.
> > > > >
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    @RolesAllowed("admin")
> > > > >    public Response listAllPushApplications(){
> > > > >      //queries
> > > > >    }
> > > > >    // READ
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    public Response listAllPushApplicationsByUsername(@Context
> > > > HttpServletRequest request) {
> > > > >        return
> > > >
> > Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > > >    }
> > > > >
> > > > >
> > > > > If the option 2 is the correct. How the Angular.js service would look
> > > > > like? Once the username is not informed as argument on
> > > > > pushApplicationService.js, because for obvious reasons it can be
> > > > > retrieved with HttpServletRequest.
> > > > >
> > > > > One of my poor ideas due to my "amazing" Angular skills would be to
> > do
> > > > > something like:
> > > > >
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    @RolesAllowed("admin")
> > > > >    @Path("/all")
> > > > >    public Response listAllPushApplications(){
> > > > >      //queries
> > > > >    }
> > > > >
> > > > > And:
> > > > >
> > > > > backendMod.factory('pushApplication', function ($resource) {
> > > > >  return $resource('rest/applications/all/:verb', {
> > > > > .....
> > > > >
> > > > >
> > > > > Help?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > abstractj
> > > > > PGP: 0x84DC9914
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Fri Oct 10 09:35:38 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 15:35:38 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141010132006.GA10563@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010132006.GA10563@abstractj.org>
Message-ID: <CAAg5f2Sp6w-nguogs1aV6=d2m-FVMhzg3N97-yzhfDhARNyVgQ@mail.gmail.com>

On Fri, Oct 10, 2014 at 3:20 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Well it's your call, even if I don't like the design.
>

perhaps we do a little hangout ?


>
> On 2014-10-10, Matthias Wessendorf wrote:
> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > On 2014-10-09, Matthias Wessendorf wrote:
> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com
> >
> > > wrote:
> > > >
> > > > > Another option could be :
> > > > > - no change or addition of any endpoint
> > > > > -no change on the angular side
> > > > >
> > > > > Since the result is the same : we want a list of applications (for
> > > admin
> > > > > there is just no restriction on developer that owns it)
> > > > > But in the service layer when retrieving the applications we check
> the
> > > > > role (do we have a method hasRole(string) ? ) to see if we add the
> > > criteria
> > > > > of developer.
> > > > >
> > > >
> > > > yeah, that;s what I had in my email from last night as well. the
> service
> > > > returns a list of applications.
> > >
> > > I think this is very clear to everyone and the basic principle of this
> > > jira.
> > >
> > > > Inside we handle the different cases:
> > > > - admin
> > > >    Select all (e.g. "select pa from PushApplication pa")
> > > > -developer
> > > >    select 'my apps' (e.g. "select pa from PushApplication pa where
> > > > pa.developer = :loginName")
> > >
> > > This is the recommendation from KC documentation
> > >
> > >
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > > .
> > >
> >
> > I understand their example, but we don't really (within UPS) have a
> > completely different UI between "admin" and "developer" roles.
> >
> >
> > >
> > > So what do you guys suggest is: If I have several methods to validate
> > > multiple roles, just add if/else all along the UPS code? And if I have
> a
> > > new
> > > role, include more ifs?
> > >
> > > I think it can be done inject the SecurityContext, have to check with
> > > Stian and Bill. But it doesn't seem right.
> > >
> >
> > might not be the most elegant, but looks like it avoids adding too much
> new
> > code. Especially since the UI for 'admin' and 'developer' is pretty much
> > the same.
> >
> >
> > >
> > > >
> > > >
> > > > -Matthias
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > Envoy? de mon iPhone
> > > > >
> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
> > > ?crit :
> > > > > >
> > > > > > Good morning, moving forward with
> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > > > > recommended approach for admin-ui.
> > > > > >
> > > > > > Have separated endpoints for the admin like:
> > > > > >
> > > > > > 1.
> > > > > >
> > > > > > @RolesAllowed("admin")
> > > > > > @Path("/admin/applications")
> > > > > > public class AdminApplicationEndpoint extends
> AbstractBaseEndpoint {
> > > > > >
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    public Response listAllPushApplications(){
> > > > > >        //queries
> > > > > >    }
> > > > > > }
> > > > > >
> > > > > > Or introduce a new method inside the current
> PushApplicationEndpoint:
> > > > > >
> > > > > > 2.
> > > > > >
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    @RolesAllowed("admin")
> > > > > >    public Response listAllPushApplications(){
> > > > > >      //queries
> > > > > >    }
> > > > > >    // READ
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    public Response listAllPushApplicationsByUsername(@Context
> > > > > HttpServletRequest request) {
> > > > > >        return
> > > > >
> > >
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > > > >    }
> > > > > >
> > > > > >
> > > > > > If the option 2 is the correct. How the Angular.js service would
> look
> > > > > > like? Once the username is not informed as argument on
> > > > > > pushApplicationService.js, because for obvious reasons it can be
> > > > > > retrieved with HttpServletRequest.
> > > > > >
> > > > > > One of my poor ideas due to my "amazing" Angular skills would be
> to
> > > do
> > > > > > something like:
> > > > > >
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    @RolesAllowed("admin")
> > > > > >    @Path("/all")
> > > > > >    public Response listAllPushApplications(){
> > > > > >      //queries
> > > > > >    }
> > > > > >
> > > > > > And:
> > > > > >
> > > > > > backendMod.factory('pushApplication', function ($resource) {
> > > > > >  return $resource('rest/applications/all/:verb', {
> > > > > > .....
> > > > > >
> > > > > >
> > > > > > Help?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > abstractj
> > > > > > PGP: 0x84DC9914
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Fri Oct 10 09:36:23 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 10:36:23 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
Message-ID: <20141010133623.GA11110@abstractj.org>

I really want to confirm this. So this is what you guys want:

- https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
- https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
- https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
- https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199

And with more methods we add more IFs, right?

On 2014-10-10, Matthias Wessendorf wrote:
> On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-10-09, Matthias Wessendorf wrote:
> > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com>
> > wrote:
> > >
> > > > Another option could be :
> > > > - no change or addition of any endpoint
> > > > -no change on the angular side
> > > >
> > > > Since the result is the same : we want a list of applications (for
> > admin
> > > > there is just no restriction on developer that owns it)
> > > > But in the service layer when retrieving the applications we check the
> > > > role (do we have a method hasRole(string) ? ) to see if we add the
> > criteria
> > > > of developer.
> > > >
> > >
> > > yeah, that;s what I had in my email from last night as well. the service
> > > returns a list of applications.
> >
> > I think this is very clear to everyone and the basic principle of this
> > jira.
> >
> > > Inside we handle the different cases:
> > > - admin
> > >    Select all (e.g. "select pa from PushApplication pa")
> > > -developer
> > >    select 'my apps' (e.g. "select pa from PushApplication pa where
> > > pa.developer = :loginName")
> >
> > This is the recommendation from KC documentation
> >
> > http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > .
> >
>
> I understand their example, but we don't really (within UPS) have a
> completely different UI between "admin" and "developer" roles.
>
>
> >
> > So what do you guys suggest is: If I have several methods to validate
> > multiple roles, just add if/else all along the UPS code? And if I have a
> > new
> > role, include more ifs?
> >
> > I think it can be done inject the SecurityContext, have to check with
> > Stian and Bill. But it doesn't seem right.
> >
>
> might not be the most elegant, but looks like it avoids adding too much new
> code. Especially since the UI for 'admin' and 'developer' is pretty much
> the same.
>
>
> >
> > >
> > >
> > > -Matthias
> > >
> > >
> > >
> > >
> > >
> > > >
> > > > Envoy? de mon iPhone
> > > >
> > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
> > ?crit :
> > > > >
> > > > > Good morning, moving forward with
> > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > > > recommended approach for admin-ui.
> > > > >
> > > > > Have separated endpoints for the admin like:
> > > > >
> > > > > 1.
> > > > >
> > > > > @RolesAllowed("admin")
> > > > > @Path("/admin/applications")
> > > > > public class AdminApplicationEndpoint extends AbstractBaseEndpoint {
> > > > >
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    public Response listAllPushApplications(){
> > > > >        //queries
> > > > >    }
> > > > > }
> > > > >
> > > > > Or introduce a new method inside the current PushApplicationEndpoint:
> > > > >
> > > > > 2.
> > > > >
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    @RolesAllowed("admin")
> > > > >    public Response listAllPushApplications(){
> > > > >      //queries
> > > > >    }
> > > > >    // READ
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    public Response listAllPushApplicationsByUsername(@Context
> > > > HttpServletRequest request) {
> > > > >        return
> > > >
> > Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > > >    }
> > > > >
> > > > >
> > > > > If the option 2 is the correct. How the Angular.js service would look
> > > > > like? Once the username is not informed as argument on
> > > > > pushApplicationService.js, because for obvious reasons it can be
> > > > > retrieved with HttpServletRequest.
> > > > >
> > > > > One of my poor ideas due to my "amazing" Angular skills would be to
> > do
> > > > > something like:
> > > > >
> > > > >    @GET
> > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >    @RolesAllowed("admin")
> > > > >    @Path("/all")
> > > > >    public Response listAllPushApplications(){
> > > > >      //queries
> > > > >    }
> > > > >
> > > > > And:
> > > > >
> > > > > backendMod.factory('pushApplication', function ($resource) {
> > > > >  return $resource('rest/applications/all/:verb', {
> > > > > .....
> > > > >
> > > > >
> > > > > Help?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > abstractj
> > > > > PGP: 0x84DC9914
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Fri Oct 10 09:40:36 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 15:40:36 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141010133623.GA11110@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
Message-ID: <CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>

"you guys" :)

I think the only different between 'admin' and developer' role is really
the result of the "findAllPushApplicationsForDeveloper()"

everything else would be the same

On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> I really want to confirm this. So this is what you guys want:
>
> -
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> -
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> -
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> -
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
>
> And with more methods we add more IFs, right?
>
> On 2014-10-10, Matthias Wessendorf wrote:
> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > On 2014-10-09, Matthias Wessendorf wrote:
> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <scm.blanc at gmail.com
> >
> > > wrote:
> > > >
> > > > > Another option could be :
> > > > > - no change or addition of any endpoint
> > > > > -no change on the angular side
> > > > >
> > > > > Since the result is the same : we want a list of applications (for
> > > admin
> > > > > there is just no restriction on developer that owns it)
> > > > > But in the service layer when retrieving the applications we check
> the
> > > > > role (do we have a method hasRole(string) ? ) to see if we add the
> > > criteria
> > > > > of developer.
> > > > >
> > > >
> > > > yeah, that;s what I had in my email from last night as well. the
> service
> > > > returns a list of applications.
> > >
> > > I think this is very clear to everyone and the basic principle of this
> > > jira.
> > >
> > > > Inside we handle the different cases:
> > > > - admin
> > > >    Select all (e.g. "select pa from PushApplication pa")
> > > > -developer
> > > >    select 'my apps' (e.g. "select pa from PushApplication pa where
> > > > pa.developer = :loginName")
> > >
> > > This is the recommendation from KC documentation
> > >
> > >
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > > .
> > >
> >
> > I understand their example, but we don't really (within UPS) have a
> > completely different UI between "admin" and "developer" roles.
> >
> >
> > >
> > > So what do you guys suggest is: If I have several methods to validate
> > > multiple roles, just add if/else all along the UPS code? And if I have
> a
> > > new
> > > role, include more ifs?
> > >
> > > I think it can be done inject the SecurityContext, have to check with
> > > Stian and Bill. But it doesn't seem right.
> > >
> >
> > might not be the most elegant, but looks like it avoids adding too much
> new
> > code. Especially since the UI for 'admin' and 'developer' is pretty much
> > the same.
> >
> >
> > >
> > > >
> > > >
> > > > -Matthias
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > Envoy? de mon iPhone
> > > > >
> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
> > > ?crit :
> > > > > >
> > > > > > Good morning, moving forward with
> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> > > > > > recommended approach for admin-ui.
> > > > > >
> > > > > > Have separated endpoints for the admin like:
> > > > > >
> > > > > > 1.
> > > > > >
> > > > > > @RolesAllowed("admin")
> > > > > > @Path("/admin/applications")
> > > > > > public class AdminApplicationEndpoint extends
> AbstractBaseEndpoint {
> > > > > >
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    public Response listAllPushApplications(){
> > > > > >        //queries
> > > > > >    }
> > > > > > }
> > > > > >
> > > > > > Or introduce a new method inside the current
> PushApplicationEndpoint:
> > > > > >
> > > > > > 2.
> > > > > >
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    @RolesAllowed("admin")
> > > > > >    public Response listAllPushApplications(){
> > > > > >      //queries
> > > > > >    }
> > > > > >    // READ
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    public Response listAllPushApplicationsByUsername(@Context
> > > > > HttpServletRequest request) {
> > > > > >        return
> > > > >
> > >
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > > > >    }
> > > > > >
> > > > > >
> > > > > > If the option 2 is the correct. How the Angular.js service would
> look
> > > > > > like? Once the username is not informed as argument on
> > > > > > pushApplicationService.js, because for obvious reasons it can be
> > > > > > retrieved with HttpServletRequest.
> > > > > >
> > > > > > One of my poor ideas due to my "amazing" Angular skills would be
> to
> > > do
> > > > > > something like:
> > > > > >
> > > > > >    @GET
> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > > >    @RolesAllowed("admin")
> > > > > >    @Path("/all")
> > > > > >    public Response listAllPushApplications(){
> > > > > >      //queries
> > > > > >    }
> > > > > >
> > > > > > And:
> > > > > >
> > > > > > backendMod.factory('pushApplication', function ($resource) {
> > > > > >  return $resource('rest/applications/all/:verb', {
> > > > > > .....
> > > > > >
> > > > > >
> > > > > > Help?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > abstractj
> > > > > > PGP: 0x84DC9914
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Fri Oct 10 09:56:44 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 15:56:44 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
Message-ID: <CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>

hangout result: no need to add lot's of IFs - since only the "finder" for
PushApplications will have a different behavior (meaning for admin -> all;
for developer -> just my own apps)
At this point no need of a specific admin-ish endpoint, nor no need to
create a new "admin" UI.

However, once we are in a need to do more tweaks for an admin user (e.g. in
a year or so): yes, there should not be any more IFs but a more cleaner
approcah, like extra classes as Bruno did suggest.

Cheers!


On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> "you guys" :)
>
> I think the only different between 'admin' and developer' role is really
> the result of the "findAllPushApplicationsForDeveloper()"
>
> everything else would be the same
>
> On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> I really want to confirm this. So this is what you guys want:
>>
>> -
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
>> -
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
>> -
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
>> -
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
>>
>> And with more methods we add more IFs, right?
>>
>> On 2014-10-10, Matthias Wessendorf wrote:
>> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>> >
>> > > On 2014-10-09, Matthias Wessendorf wrote:
>> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
>> scm.blanc at gmail.com>
>> > > wrote:
>> > > >
>> > > > > Another option could be :
>> > > > > - no change or addition of any endpoint
>> > > > > -no change on the angular side
>> > > > >
>> > > > > Since the result is the same : we want a list of applications (for
>> > > admin
>> > > > > there is just no restriction on developer that owns it)
>> > > > > But in the service layer when retrieving the applications we
>> check the
>> > > > > role (do we have a method hasRole(string) ? ) to see if we add the
>> > > criteria
>> > > > > of developer.
>> > > > >
>> > > >
>> > > > yeah, that;s what I had in my email from last night as well. the
>> service
>> > > > returns a list of applications.
>> > >
>> > > I think this is very clear to everyone and the basic principle of this
>> > > jira.
>> > >
>> > > > Inside we handle the different cases:
>> > > > - admin
>> > > >    Select all (e.g. "select pa from PushApplication pa")
>> > > > -developer
>> > > >    select 'my apps' (e.g. "select pa from PushApplication pa where
>> > > > pa.developer = :loginName")
>> > >
>> > > This is the recommendation from KC documentation
>> > >
>> > >
>> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
>> > > .
>> > >
>> >
>> > I understand their example, but we don't really (within UPS) have a
>> > completely different UI between "admin" and "developer" roles.
>> >
>> >
>> > >
>> > > So what do you guys suggest is: If I have several methods to validate
>> > > multiple roles, just add if/else all along the UPS code? And if I
>> have a
>> > > new
>> > > role, include more ifs?
>> > >
>> > > I think it can be done inject the SecurityContext, have to check with
>> > > Stian and Bill. But it doesn't seem right.
>> > >
>> >
>> > might not be the most elegant, but looks like it avoids adding too much
>> new
>> > code. Especially since the UI for 'admin' and 'developer' is pretty much
>> > the same.
>> >
>> >
>> > >
>> > > >
>> > > >
>> > > > -Matthias
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > >
>> > > > > Envoy? de mon iPhone
>> > > > >
>> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
>> > > ?crit :
>> > > > > >
>> > > > > > Good morning, moving forward with
>> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
>> > > > > > recommended approach for admin-ui.
>> > > > > >
>> > > > > > Have separated endpoints for the admin like:
>> > > > > >
>> > > > > > 1.
>> > > > > >
>> > > > > > @RolesAllowed("admin")
>> > > > > > @Path("/admin/applications")
>> > > > > > public class AdminApplicationEndpoint extends
>> AbstractBaseEndpoint {
>> > > > > >
>> > > > > >    @GET
>> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > > >    public Response listAllPushApplications(){
>> > > > > >        //queries
>> > > > > >    }
>> > > > > > }
>> > > > > >
>> > > > > > Or introduce a new method inside the current
>> PushApplicationEndpoint:
>> > > > > >
>> > > > > > 2.
>> > > > > >
>> > > > > >    @GET
>> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > > >    @RolesAllowed("admin")
>> > > > > >    public Response listAllPushApplications(){
>> > > > > >      //queries
>> > > > > >    }
>> > > > > >    // READ
>> > > > > >    @GET
>> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > > >    public Response listAllPushApplicationsByUsername(@Context
>> > > > > HttpServletRequest request) {
>> > > > > >        return
>> > > > >
>> > >
>> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
>> > > > > >    }
>> > > > > >
>> > > > > >
>> > > > > > If the option 2 is the correct. How the Angular.js service
>> would look
>> > > > > > like? Once the username is not informed as argument on
>> > > > > > pushApplicationService.js, because for obvious reasons it can be
>> > > > > > retrieved with HttpServletRequest.
>> > > > > >
>> > > > > > One of my poor ideas due to my "amazing" Angular skills would
>> be to
>> > > do
>> > > > > > something like:
>> > > > > >
>> > > > > >    @GET
>> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > > >    @RolesAllowed("admin")
>> > > > > >    @Path("/all")
>> > > > > >    public Response listAllPushApplications(){
>> > > > > >      //queries
>> > > > > >    }
>> > > > > >
>> > > > > > And:
>> > > > > >
>> > > > > > backendMod.factory('pushApplication', function ($resource) {
>> > > > > >  return $resource('rest/applications/all/:verb', {
>> > > > > > .....
>> > > > > >
>> > > > > >
>> > > > > > Help?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > >
>> > > > > > abstractj
>> > > > > > PGP: 0x84DC9914
>> > > > > > _______________________________________________
>> > > > > > aerogear-dev mailing list
>> > > > > > aerogear-dev at lists.jboss.org
>> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > > > > _______________________________________________
>> > > > > aerogear-dev mailing list
>> > > > > aerogear-dev at lists.jboss.org
>> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Matthias Wessendorf
>> > > >
>> > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > twitter: http://twitter.com/mwessendorf
>> > >
>> > > > _______________________________________________
>> > > > aerogear-dev mailing list
>> > > > aerogear-dev at lists.jboss.org
>> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> > >
>> > > --
>> > >
>> > > abstractj
>> > > PGP: 0x84DC9914
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

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

From kpiwko at redhat.com  Fri Oct 10 10:02:00 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 10 Oct 2014 16:02:00 +0200
Subject: [aerogear-dev] Releasing new parent (0.2.7)
In-Reply-To: <1412783868.14539.13.camel@kpiwko-x220>
References: <CAAg5f2R2Rwj-4QAZC_pdw3X2ywUQ+9aT0ZeSTzOqQ5Y5AOR7VQ@mail.gmail.com>
	<1412783868.14539.13.camel@kpiwko-x220>
Message-ID: <1412949720.9097.25.camel@kpiwko-x220>

On Wed, 2014-10-08 at 17:57 +0200, Karel Piwko wrote:
> Sounds good! We'll update to newer test-bom tomorrow to check the
> content.

Testing of Aeroger parent and test BOMs passed.

> 
> Thanks for this release!
> 
> Karel
> 
> On Wed, 2014-10-08 at 17:32 +0200, Matthias Wessendorf wrote:
> > Hi,
> > 
> > I'd like to run a new release of our parent. Since the last 0.2.6 release
> > there were some changes related to newer versions:
> > 
> > * Added AngularJS extension, updated Selenium version
> > * Removal of unexisting dependency
> > * Moved declaration of org.slf4j dependencies to aerogear-test-bom, as they
> > are now used only in test profiles
> > * Upgrade Keycloak to final 1.0.1.Final
> > * Removed scope from aerogear-bom
> > * using latest greatest of OpenEJB for tests
> > 
> > 
> > The staging repo is here:
> > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3991/
> > 
> > Let me know about the release by Friday, so we can upload the bits to maven
> > central over the weekend.
> > 
> > Thanks,
> > 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



From bruno at abstractj.org  Fri Oct 10 10:06:00 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 11:06:00 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
Message-ID: <20141010140559.GB11110@abstractj.org>

+1 and one more question. During the hangouts we agreed on move this to
the service[1]. The downside is the fact that our service doesn't have
SecurityContext as maven dependency, which would imply on add it.

What works best to YOU GUYS (the team :P). Leave it as is:

https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95

Or:

boolean isAdmin = securityContext.isUserInRole("admin");
return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin, extractUsername(request))).build();

Or:

return Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext, extractUsername(request))).build();


[1] -
https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95

On 2014-10-10, Matthias Wessendorf wrote:
> hangout result: no need to add lot's of IFs - since only the "finder" for
> PushApplications will have a different behavior (meaning for admin -> all;
> for developer -> just my own apps)
> At this point no need of a specific admin-ish endpoint, nor no need to
> create a new "admin" UI.
>
> However, once we are in a need to do more tweaks for an admin user (e.g. in
> a year or so): yes, there should not be any more IFs but a more cleaner
> approcah, like extra classes as Bruno did suggest.
>
> Cheers!
>
>
> On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> > "you guys" :)
> >
> > I think the only different between 'admin' and developer' role is really
> > the result of the "findAllPushApplicationsForDeveloper()"
> >
> > everything else would be the same
> >
> > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> >
> >> I really want to confirm this. So this is what you guys want:
> >>
> >> -
> >> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> >> -
> >> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> >> -
> >> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> >> -
> >> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> >>
> >> And with more methods we add more IFs, right?
> >>
> >> On 2014-10-10, Matthias Wessendorf wrote:
> >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org>
> >> wrote:
> >> >
> >> > > On 2014-10-09, Matthias Wessendorf wrote:
> >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> >> scm.blanc at gmail.com>
> >> > > wrote:
> >> > > >
> >> > > > > Another option could be :
> >> > > > > - no change or addition of any endpoint
> >> > > > > -no change on the angular side
> >> > > > >
> >> > > > > Since the result is the same : we want a list of applications (for
> >> > > admin
> >> > > > > there is just no restriction on developer that owns it)
> >> > > > > But in the service layer when retrieving the applications we
> >> check the
> >> > > > > role (do we have a method hasRole(string) ? ) to see if we add the
> >> > > criteria
> >> > > > > of developer.
> >> > > > >
> >> > > >
> >> > > > yeah, that;s what I had in my email from last night as well. the
> >> service
> >> > > > returns a list of applications.
> >> > >
> >> > > I think this is very clear to everyone and the basic principle of this
> >> > > jira.
> >> > >
> >> > > > Inside we handle the different cases:
> >> > > > - admin
> >> > > >    Select all (e.g. "select pa from PushApplication pa")
> >> > > > -developer
> >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa where
> >> > > > pa.developer = :loginName")
> >> > >
> >> > > This is the recommendation from KC documentation
> >> > >
> >> > >
> >> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> >> > > .
> >> > >
> >> >
> >> > I understand their example, but we don't really (within UPS) have a
> >> > completely different UI between "admin" and "developer" roles.
> >> >
> >> >
> >> > >
> >> > > So what do you guys suggest is: If I have several methods to validate
> >> > > multiple roles, just add if/else all along the UPS code? And if I
> >> have a
> >> > > new
> >> > > role, include more ifs?
> >> > >
> >> > > I think it can be done inject the SecurityContext, have to check with
> >> > > Stian and Bill. But it doesn't seem right.
> >> > >
> >> >
> >> > might not be the most elegant, but looks like it avoids adding too much
> >> new
> >> > code. Especially since the UI for 'admin' and 'developer' is pretty much
> >> > the same.
> >> >
> >> >
> >> > >
> >> > > >
> >> > > >
> >> > > > -Matthias
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > >
> >> > > > > Envoy? de mon iPhone
> >> > > > >
> >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org> a
> >> > > ?crit :
> >> > > > > >
> >> > > > > > Good morning, moving forward with
> >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the most
> >> > > > > > recommended approach for admin-ui.
> >> > > > > >
> >> > > > > > Have separated endpoints for the admin like:
> >> > > > > >
> >> > > > > > 1.
> >> > > > > >
> >> > > > > > @RolesAllowed("admin")
> >> > > > > > @Path("/admin/applications")
> >> > > > > > public class AdminApplicationEndpoint extends
> >> AbstractBaseEndpoint {
> >> > > > > >
> >> > > > > >    @GET
> >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> >> > > > > >    public Response listAllPushApplications(){
> >> > > > > >        //queries
> >> > > > > >    }
> >> > > > > > }
> >> > > > > >
> >> > > > > > Or introduce a new method inside the current
> >> PushApplicationEndpoint:
> >> > > > > >
> >> > > > > > 2.
> >> > > > > >
> >> > > > > >    @GET
> >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> >> > > > > >    @RolesAllowed("admin")
> >> > > > > >    public Response listAllPushApplications(){
> >> > > > > >      //queries
> >> > > > > >    }
> >> > > > > >    // READ
> >> > > > > >    @GET
> >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> >> > > > > >    public Response listAllPushApplicationsByUsername(@Context
> >> > > > > HttpServletRequest request) {
> >> > > > > >        return
> >> > > > >
> >> > >
> >> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> >> > > > > >    }
> >> > > > > >
> >> > > > > >
> >> > > > > > If the option 2 is the correct. How the Angular.js service
> >> would look
> >> > > > > > like? Once the username is not informed as argument on
> >> > > > > > pushApplicationService.js, because for obvious reasons it can be
> >> > > > > > retrieved with HttpServletRequest.
> >> > > > > >
> >> > > > > > One of my poor ideas due to my "amazing" Angular skills would
> >> be to
> >> > > do
> >> > > > > > something like:
> >> > > > > >
> >> > > > > >    @GET
> >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> >> > > > > >    @RolesAllowed("admin")
> >> > > > > >    @Path("/all")
> >> > > > > >    public Response listAllPushApplications(){
> >> > > > > >      //queries
> >> > > > > >    }
> >> > > > > >
> >> > > > > > And:
> >> > > > > >
> >> > > > > > backendMod.factory('pushApplication', function ($resource) {
> >> > > > > >  return $resource('rest/applications/all/:verb', {
> >> > > > > > .....
> >> > > > > >
> >> > > > > >
> >> > > > > > Help?
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > >
> >> > > > > > abstractj
> >> > > > > > PGP: 0x84DC9914
> >> > > > > > _______________________________________________
> >> > > > > > aerogear-dev mailing list
> >> > > > > > aerogear-dev at lists.jboss.org
> >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> > > > >
> >> > > > > _______________________________________________
> >> > > > > aerogear-dev mailing list
> >> > > > > aerogear-dev at lists.jboss.org
> >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Matthias Wessendorf
> >> > > >
> >> > > > blog: http://matthiaswessendorf.wordpress.com/
> >> > > > sessions: http://www.slideshare.net/mwessendorf
> >> > > > twitter: http://twitter.com/mwessendorf
> >> > >
> >> > > > _______________________________________________
> >> > > > aerogear-dev mailing list
> >> > > > aerogear-dev at lists.jboss.org
> >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> > >
> >> > >
> >> > > --
> >> > >
> >> > > abstractj
> >> > > PGP: 0x84DC9914
> >> > > _______________________________________________
> >> > > aerogear-dev mailing list
> >> > > aerogear-dev at lists.jboss.org
> >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Matthias Wessendorf
> >> >
> >> > blog: http://matthiaswessendorf.wordpress.com/
> >> > sessions: http://www.slideshare.net/mwessendorf
> >> > twitter: http://twitter.com/mwessendorf
> >>
> >> > _______________________________________________
> >> > aerogear-dev mailing list
> >> > aerogear-dev at lists.jboss.org
> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >> --
> >>
> >> abstractj
> >> PGP: 0x84DC9914
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Fri Oct 10 10:11:34 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 16:11:34 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141010140559.GB11110@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
	<20141010140559.GB11110@abstractj.org>
Message-ID: <CAAg5f2RSuoyaeM6iy55dj1s+6agGYwZrFwLGs-MVx063uP3EDQ@mail.gmail.com>

I like this:

boolean isAdmin = securityContext.isUserInRole("admin");
return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
extractUsername(request))).build();



On Fri, Oct 10, 2014 at 4:06 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> +1 and one more question. During the hangouts we agreed on move this to
> the service[1]. The downside is the fact that our service doesn't have
> SecurityContext as maven dependency, which would imply on add it.
>
> What works best to YOU GUYS (the team :P). Leave it as is:
>
>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
>
> Or:
>
> boolean isAdmin = securityContext.isUserInRole("admin");
> return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> extractUsername(request))).build();
>
> Or:
>
> return
> Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
> extractUsername(request))).build();
>
>
> [1] -
>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
>
> On 2014-10-10, Matthias Wessendorf wrote:
> > hangout result: no need to add lot's of IFs - since only the "finder" for
> > PushApplications will have a different behavior (meaning for admin ->
> all;
> > for developer -> just my own apps)
> > At this point no need of a specific admin-ish endpoint, nor no need to
> > create a new "admin" UI.
> >
> > However, once we are in a need to do more tweaks for an admin user (e.g.
> in
> > a year or so): yes, there should not be any more IFs but a more cleaner
> > approcah, like extra classes as Bruno did suggest.
> >
> > Cheers!
> >
> >
> > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> > > "you guys" :)
> > >
> > > I think the only different between 'admin' and developer' role is
> really
> > > the result of the "findAllPushApplicationsForDeveloper()"
> > >
> > > everything else would be the same
> > >
> > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org>
> > > wrote:
> > >
> > >> I really want to confirm this. So this is what you guys want:
> > >>
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> > >>
> > >> And with more methods we add more IFs, right?
> > >>
> > >> On 2014-10-10, Matthias Wessendorf wrote:
> > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org
> >
> > >> wrote:
> > >> >
> > >> > > On 2014-10-09, Matthias Wessendorf wrote:
> > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> > >> scm.blanc at gmail.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > > Another option could be :
> > >> > > > > - no change or addition of any endpoint
> > >> > > > > -no change on the angular side
> > >> > > > >
> > >> > > > > Since the result is the same : we want a list of applications
> (for
> > >> > > admin
> > >> > > > > there is just no restriction on developer that owns it)
> > >> > > > > But in the service layer when retrieving the applications we
> > >> check the
> > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
> add the
> > >> > > criteria
> > >> > > > > of developer.
> > >> > > > >
> > >> > > >
> > >> > > > yeah, that;s what I had in my email from last night as well. the
> > >> service
> > >> > > > returns a list of applications.
> > >> > >
> > >> > > I think this is very clear to everyone and the basic principle of
> this
> > >> > > jira.
> > >> > >
> > >> > > > Inside we handle the different cases:
> > >> > > > - admin
> > >> > > >    Select all (e.g. "select pa from PushApplication pa")
> > >> > > > -developer
> > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
> where
> > >> > > > pa.developer = :loginName")
> > >> > >
> > >> > > This is the recommendation from KC documentation
> > >> > >
> > >> > >
> > >>
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > >> > > .
> > >> > >
> > >> >
> > >> > I understand their example, but we don't really (within UPS) have a
> > >> > completely different UI between "admin" and "developer" roles.
> > >> >
> > >> >
> > >> > >
> > >> > > So what do you guys suggest is: If I have several methods to
> validate
> > >> > > multiple roles, just add if/else all along the UPS code? And if I
> > >> have a
> > >> > > new
> > >> > > role, include more ifs?
> > >> > >
> > >> > > I think it can be done inject the SecurityContext, have to check
> with
> > >> > > Stian and Bill. But it doesn't seem right.
> > >> > >
> > >> >
> > >> > might not be the most elegant, but looks like it avoids adding too
> much
> > >> new
> > >> > code. Especially since the UI for 'admin' and 'developer' is pretty
> much
> > >> > the same.
> > >> >
> > >> >
> > >> > >
> > >> > > >
> > >> > > >
> > >> > > > -Matthias
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > >
> > >> > > > > Envoy? de mon iPhone
> > >> > > > >
> > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org>
> a
> > >> > > ?crit :
> > >> > > > > >
> > >> > > > > > Good morning, moving forward with
> > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the
> most
> > >> > > > > > recommended approach for admin-ui.
> > >> > > > > >
> > >> > > > > > Have separated endpoints for the admin like:
> > >> > > > > >
> > >> > > > > > 1.
> > >> > > > > >
> > >> > > > > > @RolesAllowed("admin")
> > >> > > > > > @Path("/admin/applications")
> > >> > > > > > public class AdminApplicationEndpoint extends
> > >> AbstractBaseEndpoint {
> > >> > > > > >
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    public Response listAllPushApplications(){
> > >> > > > > >        //queries
> > >> > > > > >    }
> > >> > > > > > }
> > >> > > > > >
> > >> > > > > > Or introduce a new method inside the current
> > >> PushApplicationEndpoint:
> > >> > > > > >
> > >> > > > > > 2.
> > >> > > > > >
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    @RolesAllowed("admin")
> > >> > > > > >    public Response listAllPushApplications(){
> > >> > > > > >      //queries
> > >> > > > > >    }
> > >> > > > > >    // READ
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    public Response
> listAllPushApplicationsByUsername(@Context
> > >> > > > > HttpServletRequest request) {
> > >> > > > > >        return
> > >> > > > >
> > >> > >
> > >>
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > >> > > > > >    }
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > If the option 2 is the correct. How the Angular.js service
> > >> would look
> > >> > > > > > like? Once the username is not informed as argument on
> > >> > > > > > pushApplicationService.js, because for obvious reasons it
> can be
> > >> > > > > > retrieved with HttpServletRequest.
> > >> > > > > >
> > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
> would
> > >> be to
> > >> > > do
> > >> > > > > > something like:
> > >> > > > > >
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    @RolesAllowed("admin")
> > >> > > > > >    @Path("/all")
> > >> > > > > >    public Response listAllPushApplications(){
> > >> > > > > >      //queries
> > >> > > > > >    }
> > >> > > > > >
> > >> > > > > > And:
> > >> > > > > >
> > >> > > > > > backendMod.factory('pushApplication', function ($resource) {
> > >> > > > > >  return $resource('rest/applications/all/:verb', {
> > >> > > > > > .....
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > Help?
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > >
> > >> > > > > > abstractj
> > >> > > > > > PGP: 0x84DC9914
> > >> > > > > > _______________________________________________
> > >> > > > > > aerogear-dev mailing list
> > >> > > > > > aerogear-dev at lists.jboss.org
> > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > > > >
> > >> > > > > _______________________________________________
> > >> > > > > aerogear-dev mailing list
> > >> > > > > aerogear-dev at lists.jboss.org
> > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Matthias Wessendorf
> > >> > > >
> > >> > > > blog: http://matthiaswessendorf.wordpress.com/
> > >> > > > sessions: http://www.slideshare.net/mwessendorf
> > >> > > > twitter: http://twitter.com/mwessendorf
> > >> > >
> > >> > > > _______________________________________________
> > >> > > > aerogear-dev mailing list
> > >> > > > aerogear-dev at lists.jboss.org
> > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > >
> > >> > >
> > >> > > --
> > >> > >
> > >> > > abstractj
> > >> > > PGP: 0x84DC9914
> > >> > > _______________________________________________
> > >> > > aerogear-dev mailing list
> > >> > > aerogear-dev at lists.jboss.org
> > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Matthias Wessendorf
> > >> >
> > >> > blog: http://matthiaswessendorf.wordpress.com/
> > >> > sessions: http://www.slideshare.net/mwessendorf
> > >> > twitter: http://twitter.com/mwessendorf
> > >>
> > >> > _______________________________________________
> > >> > aerogear-dev mailing list
> > >> > aerogear-dev at lists.jboss.org
> > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>
> > >>
> > >> --
> > >>
> > >> abstractj
> > >> PGP: 0x84DC9914
> > >> _______________________________________________
> > >> aerogear-dev mailing list
> > >> aerogear-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From daniel.bevenius at gmail.com  Fri Oct 10 10:14:23 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 10 Oct 2014 16:14:23 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141010140559.GB11110@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
	<20141010140559.GB11110@abstractj.org>
Message-ID: <CAFJm-3HWagxTERsgDu_ZvqS0FQbfFGXsd90Bb0PYZ5HfYen4xw@mail.gmail.com>

Just a thought here...is the securityContext used elsewhere in the
PushApplicationEndpoint class?
If not, perhaps we could have it injected into the PushAppService class not
have to pass anything into the findAllPushApplicationsByUser method?


On 10 October 2014 16:06, Bruno Oliveira <bruno at abstractj.org> wrote:

> +1 and one more question. During the hangouts we agreed on move this to
> the service[1]. The downside is the fact that our service doesn't have
> SecurityContext as maven dependency, which would imply on add it.
>
> What works best to YOU GUYS (the team :P). Leave it as is:
>
>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
>
> Or:
>
> boolean isAdmin = securityContext.isUserInRole("admin");
> return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> extractUsername(request))).build();
>
> Or:
>
> return
> Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
> extractUsername(request))).build();
>
>
> [1] -
>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
>
> On 2014-10-10, Matthias Wessendorf wrote:
> > hangout result: no need to add lot's of IFs - since only the "finder" for
> > PushApplications will have a different behavior (meaning for admin ->
> all;
> > for developer -> just my own apps)
> > At this point no need of a specific admin-ish endpoint, nor no need to
> > create a new "admin" UI.
> >
> > However, once we are in a need to do more tweaks for an admin user (e.g.
> in
> > a year or so): yes, there should not be any more IFs but a more cleaner
> > approcah, like extra classes as Bruno did suggest.
> >
> > Cheers!
> >
> >
> > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> > > "you guys" :)
> > >
> > > I think the only different between 'admin' and developer' role is
> really
> > > the result of the "findAllPushApplicationsForDeveloper()"
> > >
> > > everything else would be the same
> > >
> > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org>
> > > wrote:
> > >
> > >> I really want to confirm this. So this is what you guys want:
> > >>
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> > >> -
> > >>
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> > >>
> > >> And with more methods we add more IFs, right?
> > >>
> > >> On 2014-10-10, Matthias Wessendorf wrote:
> > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org
> >
> > >> wrote:
> > >> >
> > >> > > On 2014-10-09, Matthias Wessendorf wrote:
> > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> > >> scm.blanc at gmail.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > > Another option could be :
> > >> > > > > - no change or addition of any endpoint
> > >> > > > > -no change on the angular side
> > >> > > > >
> > >> > > > > Since the result is the same : we want a list of applications
> (for
> > >> > > admin
> > >> > > > > there is just no restriction on developer that owns it)
> > >> > > > > But in the service layer when retrieving the applications we
> > >> check the
> > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
> add the
> > >> > > criteria
> > >> > > > > of developer.
> > >> > > > >
> > >> > > >
> > >> > > > yeah, that;s what I had in my email from last night as well. the
> > >> service
> > >> > > > returns a list of applications.
> > >> > >
> > >> > > I think this is very clear to everyone and the basic principle of
> this
> > >> > > jira.
> > >> > >
> > >> > > > Inside we handle the different cases:
> > >> > > > - admin
> > >> > > >    Select all (e.g. "select pa from PushApplication pa")
> > >> > > > -developer
> > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
> where
> > >> > > > pa.developer = :loginName")
> > >> > >
> > >> > > This is the recommendation from KC documentation
> > >> > >
> > >> > >
> > >>
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > >> > > .
> > >> > >
> > >> >
> > >> > I understand their example, but we don't really (within UPS) have a
> > >> > completely different UI between "admin" and "developer" roles.
> > >> >
> > >> >
> > >> > >
> > >> > > So what do you guys suggest is: If I have several methods to
> validate
> > >> > > multiple roles, just add if/else all along the UPS code? And if I
> > >> have a
> > >> > > new
> > >> > > role, include more ifs?
> > >> > >
> > >> > > I think it can be done inject the SecurityContext, have to check
> with
> > >> > > Stian and Bill. But it doesn't seem right.
> > >> > >
> > >> >
> > >> > might not be the most elegant, but looks like it avoids adding too
> much
> > >> new
> > >> > code. Especially since the UI for 'admin' and 'developer' is pretty
> much
> > >> > the same.
> > >> >
> > >> >
> > >> > >
> > >> > > >
> > >> > > >
> > >> > > > -Matthias
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > >
> > >> > > > > Envoy? de mon iPhone
> > >> > > > >
> > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org>
> a
> > >> > > ?crit :
> > >> > > > > >
> > >> > > > > > Good morning, moving forward with
> > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the
> most
> > >> > > > > > recommended approach for admin-ui.
> > >> > > > > >
> > >> > > > > > Have separated endpoints for the admin like:
> > >> > > > > >
> > >> > > > > > 1.
> > >> > > > > >
> > >> > > > > > @RolesAllowed("admin")
> > >> > > > > > @Path("/admin/applications")
> > >> > > > > > public class AdminApplicationEndpoint extends
> > >> AbstractBaseEndpoint {
> > >> > > > > >
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    public Response listAllPushApplications(){
> > >> > > > > >        //queries
> > >> > > > > >    }
> > >> > > > > > }
> > >> > > > > >
> > >> > > > > > Or introduce a new method inside the current
> > >> PushApplicationEndpoint:
> > >> > > > > >
> > >> > > > > > 2.
> > >> > > > > >
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    @RolesAllowed("admin")
> > >> > > > > >    public Response listAllPushApplications(){
> > >> > > > > >      //queries
> > >> > > > > >    }
> > >> > > > > >    // READ
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    public Response
> listAllPushApplicationsByUsername(@Context
> > >> > > > > HttpServletRequest request) {
> > >> > > > > >        return
> > >> > > > >
> > >> > >
> > >>
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > >> > > > > >    }
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > If the option 2 is the correct. How the Angular.js service
> > >> would look
> > >> > > > > > like? Once the username is not informed as argument on
> > >> > > > > > pushApplicationService.js, because for obvious reasons it
> can be
> > >> > > > > > retrieved with HttpServletRequest.
> > >> > > > > >
> > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
> would
> > >> be to
> > >> > > do
> > >> > > > > > something like:
> > >> > > > > >
> > >> > > > > >    @GET
> > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > >> > > > > >    @RolesAllowed("admin")
> > >> > > > > >    @Path("/all")
> > >> > > > > >    public Response listAllPushApplications(){
> > >> > > > > >      //queries
> > >> > > > > >    }
> > >> > > > > >
> > >> > > > > > And:
> > >> > > > > >
> > >> > > > > > backendMod.factory('pushApplication', function ($resource) {
> > >> > > > > >  return $resource('rest/applications/all/:verb', {
> > >> > > > > > .....
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > Help?
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > >
> > >> > > > > > abstractj
> > >> > > > > > PGP: 0x84DC9914
> > >> > > > > > _______________________________________________
> > >> > > > > > aerogear-dev mailing list
> > >> > > > > > aerogear-dev at lists.jboss.org
> > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > > > >
> > >> > > > > _______________________________________________
> > >> > > > > aerogear-dev mailing list
> > >> > > > > aerogear-dev at lists.jboss.org
> > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Matthias Wessendorf
> > >> > > >
> > >> > > > blog: http://matthiaswessendorf.wordpress.com/
> > >> > > > sessions: http://www.slideshare.net/mwessendorf
> > >> > > > twitter: http://twitter.com/mwessendorf
> > >> > >
> > >> > > > _______________________________________________
> > >> > > > aerogear-dev mailing list
> > >> > > > aerogear-dev at lists.jboss.org
> > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > >
> > >> > >
> > >> > > --
> > >> > >
> > >> > > abstractj
> > >> > > PGP: 0x84DC9914
> > >> > > _______________________________________________
> > >> > > aerogear-dev mailing list
> > >> > > aerogear-dev at lists.jboss.org
> > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Matthias Wessendorf
> > >> >
> > >> > blog: http://matthiaswessendorf.wordpress.com/
> > >> > sessions: http://www.slideshare.net/mwessendorf
> > >> > twitter: http://twitter.com/mwessendorf
> > >>
> > >> > _______________________________________________
> > >> > aerogear-dev mailing list
> > >> > aerogear-dev at lists.jboss.org
> > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>
> > >>
> > >> --
> > >>
> > >> abstractj
> > >> PGP: 0x84DC9914
> > >> _______________________________________________
> > >> aerogear-dev mailing list
> > >> aerogear-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141010/f8d9d515/attachment-0001.html 

From bruno at abstractj.org  Fri Oct 10 10:15:01 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 11:15:01 -0300
Subject: [aerogear-dev] Eating our own dog food,
 or TOTP demos for AeroGear
In-Reply-To: <76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
Message-ID: <20141010141501.GA12017@abstractj.org>

It it will add an extra work, I see it as low priority. If we have,
cool, otherwise, best effort.

Thanks for the clarification Christos.

On 2014-10-10, Christos Vasilakis wrote:
> Hi,
>
> answers inline
>
> On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > No way, Matthias. OTP must be always offline. To retrieve the shared
> > secret, we scan the QR Code.
> >
> > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
> > On Android, I'm pretty much sure that QR Code scanning was already
> > implemented.
> >
>
> revisiting this, I can see indeed on iOS the shared secret is retrieved from the server and that is only the option offered. Our Android example offers both options, either from server, or using QR code scanning, so implementing the latter on our iOS demo need to be also done.
>
> created to track it :
>  https://issues.jboss.org/browse/AGIOS-289
>
> > We don't need to be perfect, get what is already done, improve if
> > possible or release what is already done.
>
> +1 for releasing on the app store. My fear is, as Matthias said earlier, the ?demo? aspect, but with a nice description/walkthrough submission details, maybe there is chance.. and tbh I have seen far far simplest apps accepted on their store.
>
>
> -
> Christos
>
>
>
> >
> > [1] -
> > https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
> >
> >
> > On 2014-10-09, Matthias Wessendorf wrote:
> >
> >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> >>
> >>> On 2014-10-09, Matthias Wessendorf wrote:
> >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
> >>> wrote:
> >>>>
> >>>>> Good morning,
> >>>>>
> >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> >>>>> ago. On conferences most of the developers get amazed with our API.
> >>>>>
> >>>>
> >>>> It's always great feedback when I show the OTP demo. Attendees at
> >>>> conferences love it!
> >>>>
> >>>>
> >>>>>
> >>>>> Although we don't have any app published on Google Play or App Store. I
> >>>>> think it's time to release our demos and get some feedback from our
> >>>>> community.
> >>>>>
> >>>>
> >>>> with release, what do you mean? Submit to the stores?
> >>>> On Apple one reason we never submitted anything to their App Store is
> >>> their
> >>>> rules clearly indicate no demos are allowed in there.
> >>>
> >>> I understand, it can be a real and non paid app. Once it does not depends
> >>> on
> >>> internet connection at this moment.
> >>>
> >>
> >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?
> >>
> >>
> >>>
> >>>>
> >>>>
> >>>>>
> >>>>> Into this way we can exercise things like:
> >>>>>
> >>>>> - Properly store the shared secret
> >>>>> - Password protection with offline authentication
> >>>>> - If we are very confident, sync the TOTPs across authorized devices
> >>>>>
> >>>>> At the moment, we don't need to do so much once most of our demos are
> >>>>> already on GH.
> >>>>
> >>>>
> >>>> The only thing is perhaps making sure the backend part of our OTP demo is
> >>>> (always) up :)
> >>>>
> >>>>
> >>>>
> >>>>> I think it's just the matter of release it.
> >>>>>
> >>>>> Thoughts?
> >>>>>
> >>>>
> >>>> I like giving these nice demos, and their used AeroGear technology, some
> >>>> more love and visibility.
> >>>>
> >>>>
> >>>>>
> >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
> >>>>>
> >>>>> --
> >>>>>
> >>>>> abstractj
> >>>>> PGP: 0x84DC9914
> >>>>> _______________________________________________
> >>>>> aerogear-dev mailing list
> >>>>> aerogear-dev at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Matthias Wessendorf
> >>>>
> >>>> blog: http://matthiaswessendorf.wordpress.com/
> >>>> sessions: http://www.slideshare.net/mwessendorf
> >>>> twitter: http://twitter.com/mwessendorf
> >>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>> --
> >>>
> >>> abstractj
> >>> PGP: 0x84DC9914
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Fri Oct 10 10:18:49 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 11:18:49 -0300
Subject: [aerogear-dev] Eating our own dog food,
 or TOTP demos for AeroGear
In-Reply-To: <CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
	<CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
Message-ID: <20141010141849.GB12017@abstractj.org>

Cool, the goal of this thread with OTP, is only if it's ready and do not
require extra effort.

On 2014-10-10, Corinne Krych wrote:
> Same here Bruno I would like to publish Shoot, in its Swift version to
> apple store.
> We have a ticket to enhance it with an iOS photo sharing dialog. Once this
> one is done, let's submit.
> For the app store I might limit it to Facebook and Google+, to start with.
>
> ++
> Corinne
>
> On 10 October 2014 08:48, Christos Vasilakis <cvasilak at gmail.com> wrote:
>
> > Hi,
> >
> > answers inline
> >
> > On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> > > No way, Matthias. OTP must be always offline. To retrieve the shared
> > > secret, we scan the QR Code.
> > >
> > > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
> > > On Android, I'm pretty much sure that QR Code scanning was already
> > > implemented.
> > >
> >
> > revisiting this, I can see indeed on iOS the shared secret is retrieved
> > from the server and that is only the option offered. Our Android example
> > offers both options, either from server, or using QR code scanning, so
> > implementing the latter on our iOS demo need to be also done.
> >
> > created to track it :
> >  https://issues.jboss.org/browse/AGIOS-289
> >
> > > We don't need to be perfect, get what is already done, improve if
> > > possible or release what is already done.
> >
> > +1 for releasing on the app store. My fear is, as Matthias said earlier,
> > the ?demo? aspect, but with a nice description/walkthrough submission
> > details, maybe there is chance.. and tbh I have seen far far simplest apps
> > accepted on their store.
> >
> >
> > -
> > Christos
> >
> >
> >
> > >
> > > [1] -
> > >
> > https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
> > >
> > >
> > > On 2014-10-09, Matthias Wessendorf wrote:
> > >
> > >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >>
> > >>> On 2014-10-09, Matthias Wessendorf wrote:
> > >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org>
> > >>> wrote:
> > >>>>
> > >>>>> Good morning,
> > >>>>>
> > >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two years
> > >>>>> ago. On conferences most of the developers get amazed with our API.
> > >>>>>
> > >>>>
> > >>>> It's always great feedback when I show the OTP demo. Attendees at
> > >>>> conferences love it!
> > >>>>
> > >>>>
> > >>>>>
> > >>>>> Although we don't have any app published on Google Play or App
> > Store. I
> > >>>>> think it's time to release our demos and get some feedback from our
> > >>>>> community.
> > >>>>>
> > >>>>
> > >>>> with release, what do you mean? Submit to the stores?
> > >>>> On Apple one reason we never submitted anything to their App Store is
> > >>> their
> > >>>> rules clearly indicate no demos are allowed in there.
> > >>>
> > >>> I understand, it can be a real and non paid app. Once it does not
> > depends
> > >>> on
> > >>> internet connection at this moment.
> > >>>
> > >>
> > >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the tokens?
> > >>
> > >>
> > >>>
> > >>>>
> > >>>>
> > >>>>>
> > >>>>> Into this way we can exercise things like:
> > >>>>>
> > >>>>> - Properly store the shared secret
> > >>>>> - Password protection with offline authentication
> > >>>>> - If we are very confident, sync the TOTPs across authorized devices
> > >>>>>
> > >>>>> At the moment, we don't need to do so much once most of our demos are
> > >>>>> already on GH.
> > >>>>
> > >>>>
> > >>>> The only thing is perhaps making sure the backend part of our OTP
> > demo is
> > >>>> (always) up :)
> > >>>>
> > >>>>
> > >>>>
> > >>>>> I think it's just the matter of release it.
> > >>>>>
> > >>>>> Thoughts?
> > >>>>>
> > >>>>
> > >>>> I like giving these nice demos, and their used AeroGear technology,
> > some
> > >>>> more love and visibility.
> > >>>>
> > >>>>
> > >>>>>
> > >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> > >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
> > >>>>>
> > >>>>> --
> > >>>>>
> > >>>>> abstractj
> > >>>>> PGP: 0x84DC9914
> > >>>>> _______________________________________________
> > >>>>> aerogear-dev mailing list
> > >>>>> aerogear-dev at lists.jboss.org
> > >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> Matthias Wessendorf
> > >>>>
> > >>>> blog: http://matthiaswessendorf.wordpress.com/
> > >>>> sessions: http://www.slideshare.net/mwessendorf
> > >>>> twitter: http://twitter.com/mwessendorf
> > >>>
> > >>>> _______________________________________________
> > >>>> aerogear-dev mailing list
> > >>>> aerogear-dev at lists.jboss.org
> > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>>
> > >>>
> > >>> --
> > >>>
> > >>> abstractj
> > >>> PGP: 0x84DC9914
> > >>> _______________________________________________
> > >>> aerogear-dev mailing list
> > >>> aerogear-dev at lists.jboss.org
> > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Matthias Wessendorf
> > >>
> > >> blog: http://matthiaswessendorf.wordpress.com/
> > >> sessions: http://www.slideshare.net/mwessendorf
> > >> twitter: http://twitter.com/mwessendorf
> > >
> > >> _______________________________________________
> > >> aerogear-dev mailing list
> > >> aerogear-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Fri Oct 10 10:20:43 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 11:20:43 -0300
Subject: [aerogear-dev] Eating our own dog food,
 or TOTP demos for AeroGear
In-Reply-To: <CAKjsGbv6+Y+skSpQNJ5n6XATtu8kMLNvfUWRBCXF7J1ZsLkN3Q@mail.gmail.com>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
	<CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
	<CAAg5f2TtG7MNOgX-YJNNDt5YeUbcJXjnR_BwYA+XzQOftJORmg@mail.gmail.com>
	<CAKjsGbv6+Y+skSpQNJ5n6XATtu8kMLNvfUWRBCXF7J1ZsLkN3Q@mail.gmail.com>
Message-ID: <20141010142043.GC12017@abstractj.org>

On 2014-10-10, Daniel Passos wrote:
> Hi guys,
>
> Yep, In Android land we have secret request and qrcode scan.
>
> 1) May be is a good idea remove the secret request?

+1

>
> 2) In related news, today we not store the secret. I think store that
> before publish is a good thing to do

+1 Feel free to file jiras and assign to me if you want.
>
> -- Passos
>
>
> On Fri, Oct 10, 2014 at 4:47 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> >
> >
> > On Fri, Oct 10, 2014 at 9:00 AM, Corinne Krych <corinnekrych at gmail.com>
> > wrote:
> >
> >> Same here Bruno I would like to publish Shoot, in its Swift version to
> >> apple store.
> >>
> >
> > +1 that is even useful :)
> > so not a "demo" at all.
> >
> > Great idea!
> >
> >
> >> We have a ticket to enhance it with an iOS photo sharing dialog. Once
> >> this one is done, let's submit.
> >> For the app store I might limit it to Facebook and Google+, to start with.
> >>
> >> ++
> >> Corinne
> >>
> >> On 10 October 2014 08:48, Christos Vasilakis <cvasilak at gmail.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> answers inline
> >>>
> >>> On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> >>>
> >>> > No way, Matthias. OTP must be always offline. To retrieve the shared
> >>> > secret, we scan the QR Code.
> >>> >
> >>> > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
> >>> > On Android, I'm pretty much sure that QR Code scanning was already
> >>> > implemented.
> >>> >
> >>>
> >>> revisiting this, I can see indeed on iOS the shared secret is retrieved
> >>> from the server and that is only the option offered. Our Android example
> >>> offers both options, either from server, or using QR code scanning, so
> >>> implementing the latter on our iOS demo need to be also done.
> >>>
> >>> created to track it :
> >>>  https://issues.jboss.org/browse/AGIOS-289
> >>>
> >>> > We don't need to be perfect, get what is already done, improve if
> >>> > possible or release what is already done.
> >>>
> >>> +1 for releasing on the app store. My fear is, as Matthias said earlier,
> >>> the ?demo? aspect, but with a nice description/walkthrough submission
> >>> details, maybe there is chance.. and tbh I have seen far far simplest apps
> >>> accepted on their store.
> >>>
> >>>
> >>> -
> >>> Christos
> >>>
> >>>
> >>>
> >>> >
> >>> > [1] -
> >>> >
> >>> https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
> >>> >
> >>> >
> >>> > On 2014-10-09, Matthias Wessendorf wrote:
> >>> >
> >>> >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <bruno at abstractj.org>
> >>> wrote:
> >>> >>
> >>> >>> On 2014-10-09, Matthias Wessendorf wrote:
> >>> >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <bruno at abstractj.org
> >>> >
> >>> >>> wrote:
> >>> >>>>
> >>> >>>>> Good morning,
> >>> >>>>>
> >>> >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two
> >>> years
> >>> >>>>> ago. On conferences most of the developers get amazed with our API.
> >>> >>>>>
> >>> >>>>
> >>> >>>> It's always great feedback when I show the OTP demo. Attendees at
> >>> >>>> conferences love it!
> >>> >>>>
> >>> >>>>
> >>> >>>>>
> >>> >>>>> Although we don't have any app published on Google Play or App
> >>> Store. I
> >>> >>>>> think it's time to release our demos and get some feedback from our
> >>> >>>>> community.
> >>> >>>>>
> >>> >>>>
> >>> >>>> with release, what do you mean? Submit to the stores?
> >>> >>>> On Apple one reason we never submitted anything to their App Store
> >>> is
> >>> >>> their
> >>> >>>> rules clearly indicate no demos are allowed in there.
> >>> >>>
> >>> >>> I understand, it can be a real and non paid app. Once it does not
> >>> depends
> >>> >>> on
> >>> >>> internet connection at this moment.
> >>> >>>
> >>> >>
> >>> >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the
> >>> tokens?
> >>> >>
> >>> >>
> >>> >>>
> >>> >>>>
> >>> >>>>
> >>> >>>>>
> >>> >>>>> Into this way we can exercise things like:
> >>> >>>>>
> >>> >>>>> - Properly store the shared secret
> >>> >>>>> - Password protection with offline authentication
> >>> >>>>> - If we are very confident, sync the TOTPs across authorized
> >>> devices
> >>> >>>>>
> >>> >>>>> At the moment, we don't need to do so much once most of our demos
> >>> are
> >>> >>>>> already on GH.
> >>> >>>>
> >>> >>>>
> >>> >>>> The only thing is perhaps making sure the backend part of our OTP
> >>> demo is
> >>> >>>> (always) up :)
> >>> >>>>
> >>> >>>>
> >>> >>>>
> >>> >>>>> I think it's just the matter of release it.
> >>> >>>>>
> >>> >>>>> Thoughts?
> >>> >>>>>
> >>> >>>>
> >>> >>>> I like giving these nice demos, and their used AeroGear technology,
> >>> some
> >>> >>>> more love and visibility.
> >>> >>>>
> >>> >>>>
> >>> >>>>>
> >>> >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> >>> >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
> >>> >>>>>
> >>> >>>>> --
> >>> >>>>>
> >>> >>>>> abstractj
> >>> >>>>> PGP: 0x84DC9914
> >>> >>>>> _______________________________________________
> >>> >>>>> aerogear-dev mailing list
> >>> >>>>> aerogear-dev at lists.jboss.org
> >>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>> >>>>>
> >>> >>>>
> >>> >>>>
> >>> >>>>
> >>> >>>> --
> >>> >>>> Matthias Wessendorf
> >>> >>>>
> >>> >>>> blog: http://matthiaswessendorf.wordpress.com/
> >>> >>>> sessions: http://www.slideshare.net/mwessendorf
> >>> >>>> twitter: http://twitter.com/mwessendorf
> >>> >>>
> >>> >>>> _______________________________________________
> >>> >>>> aerogear-dev mailing list
> >>> >>>> aerogear-dev at lists.jboss.org
> >>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>> >>>
> >>> >>>
> >>> >>> --
> >>> >>>
> >>> >>> abstractj
> >>> >>> PGP: 0x84DC9914
> >>> >>> _______________________________________________
> >>> >>> aerogear-dev mailing list
> >>> >>> aerogear-dev at lists.jboss.org
> >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>> >>>
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Matthias Wessendorf
> >>> >>
> >>> >> blog: http://matthiaswessendorf.wordpress.com/
> >>> >> sessions: http://www.slideshare.net/mwessendorf
> >>> >> twitter: http://twitter.com/mwessendorf
> >>> >
> >>> >> _______________________________________________
> >>> >> aerogear-dev mailing list
> >>> >> aerogear-dev at lists.jboss.org
> >>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>> >
> >>> >
> >>> > --
> >>> >
> >>> > abstractj
> >>> > PGP: 0x84DC9914
> >>> > _______________________________________________
> >>> > aerogear-dev mailing list
> >>> > aerogear-dev at lists.jboss.org
> >>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

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


--

abstractj
PGP: 0x84DC9914

From kpiwko at redhat.com  Fri Oct 10 10:39:19 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 10 Oct 2014 16:39:19 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAAg5f2RSuoyaeM6iy55dj1s+6agGYwZrFwLGs-MVx063uP3EDQ@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
	<20141010140559.GB11110@abstractj.org>
	<CAAg5f2RSuoyaeM6iy55dj1s+6agGYwZrFwLGs-MVx063uP3EDQ@mail.gmail.com>
Message-ID: <1412951959.9097.27.camel@kpiwko-x220>

On Fri, 2014-10-10 at 16:11 +0200, Matthias Wessendorf wrote:
> I like this:
> 
> boolean isAdmin = securityContext.isUserInRole("admin");
> return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> extractUsername(request))).build();

Can we ensure that admin and developer will be only roles on UPS for
ever? If not, securityContext seems like a better option to me - more
flexible.

> 
> 
> 
> On Fri, Oct 10, 2014 at 4:06 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> 
> > +1 and one more question. During the hangouts we agreed on move this to
> > the service[1]. The downside is the fact that our service doesn't have
> > SecurityContext as maven dependency, which would imply on add it.
> >
> > What works best to YOU GUYS (the team :P). Leave it as is:
> >
> >
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> >
> > Or:
> >
> > boolean isAdmin = securityContext.isUserInRole("admin");
> > return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> > extractUsername(request))).build();
> >
> > Or:
> >
> > return
> > Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
> > extractUsername(request))).build();
> >
> >
> > [1] -
> >
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> >
> > On 2014-10-10, Matthias Wessendorf wrote:
> > > hangout result: no need to add lot's of IFs - since only the "finder" for
> > > PushApplications will have a different behavior (meaning for admin ->
> > all;
> > > for developer -> just my own apps)
> > > At this point no need of a specific admin-ish endpoint, nor no need to
> > > create a new "admin" UI.
> > >
> > > However, once we are in a need to do more tweaks for an admin user (e.g.
> > in
> > > a year or so): yes, there should not be any more IFs but a more cleaner
> > > approcah, like extra classes as Bruno did suggest.
> > >
> > > Cheers!
> > >
> > >
> > > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <matzew at apache.org>
> > > wrote:
> > >
> > > > "you guys" :)
> > > >
> > > > I think the only different between 'admin' and developer' role is
> > really
> > > > the result of the "findAllPushApplicationsForDeveloper()"
> > > >
> > > > everything else would be the same
> > > >
> > > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org>
> > > > wrote:
> > > >
> > > >> I really want to confirm this. So this is what you guys want:
> > > >>
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> > > >>
> > > >> And with more methods we add more IFs, right?
> > > >>
> > > >> On 2014-10-10, Matthias Wessendorf wrote:
> > > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org
> > >
> > > >> wrote:
> > > >> >
> > > >> > > On 2014-10-09, Matthias Wessendorf wrote:
> > > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> > > >> scm.blanc at gmail.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > > Another option could be :
> > > >> > > > > - no change or addition of any endpoint
> > > >> > > > > -no change on the angular side
> > > >> > > > >
> > > >> > > > > Since the result is the same : we want a list of applications
> > (for
> > > >> > > admin
> > > >> > > > > there is just no restriction on developer that owns it)
> > > >> > > > > But in the service layer when retrieving the applications we
> > > >> check the
> > > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
> > add the
> > > >> > > criteria
> > > >> > > > > of developer.
> > > >> > > > >
> > > >> > > >
> > > >> > > > yeah, that;s what I had in my email from last night as well. the
> > > >> service
> > > >> > > > returns a list of applications.
> > > >> > >
> > > >> > > I think this is very clear to everyone and the basic principle of
> > this
> > > >> > > jira.
> > > >> > >
> > > >> > > > Inside we handle the different cases:
> > > >> > > > - admin
> > > >> > > >    Select all (e.g. "select pa from PushApplication pa")
> > > >> > > > -developer
> > > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
> > where
> > > >> > > > pa.developer = :loginName")
> > > >> > >
> > > >> > > This is the recommendation from KC documentation
> > > >> > >
> > > >> > >
> > > >>
> > http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > > >> > > .
> > > >> > >
> > > >> >
> > > >> > I understand their example, but we don't really (within UPS) have a
> > > >> > completely different UI between "admin" and "developer" roles.
> > > >> >
> > > >> >
> > > >> > >
> > > >> > > So what do you guys suggest is: If I have several methods to
> > validate
> > > >> > > multiple roles, just add if/else all along the UPS code? And if I
> > > >> have a
> > > >> > > new
> > > >> > > role, include more ifs?
> > > >> > >
> > > >> > > I think it can be done inject the SecurityContext, have to check
> > with
> > > >> > > Stian and Bill. But it doesn't seem right.
> > > >> > >
> > > >> >
> > > >> > might not be the most elegant, but looks like it avoids adding too
> > much
> > > >> new
> > > >> > code. Especially since the UI for 'admin' and 'developer' is pretty
> > much
> > > >> > the same.
> > > >> >
> > > >> >
> > > >> > >
> > > >> > > >
> > > >> > > >
> > > >> > > > -Matthias
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > >
> > > >> > > > > Envoy? de mon iPhone
> > > >> > > > >
> > > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org>
> > a
> > > >> > > ?crit :
> > > >> > > > > >
> > > >> > > > > > Good morning, moving forward with
> > > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the
> > most
> > > >> > > > > > recommended approach for admin-ui.
> > > >> > > > > >
> > > >> > > > > > Have separated endpoints for the admin like:
> > > >> > > > > >
> > > >> > > > > > 1.
> > > >> > > > > >
> > > >> > > > > > @RolesAllowed("admin")
> > > >> > > > > > @Path("/admin/applications")
> > > >> > > > > > public class AdminApplicationEndpoint extends
> > > >> AbstractBaseEndpoint {
> > > >> > > > > >
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    public Response listAllPushApplications(){
> > > >> > > > > >        //queries
> > > >> > > > > >    }
> > > >> > > > > > }
> > > >> > > > > >
> > > >> > > > > > Or introduce a new method inside the current
> > > >> PushApplicationEndpoint:
> > > >> > > > > >
> > > >> > > > > > 2.
> > > >> > > > > >
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    @RolesAllowed("admin")
> > > >> > > > > >    public Response listAllPushApplications(){
> > > >> > > > > >      //queries
> > > >> > > > > >    }
> > > >> > > > > >    // READ
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    public Response
> > listAllPushApplicationsByUsername(@Context
> > > >> > > > > HttpServletRequest request) {
> > > >> > > > > >        return
> > > >> > > > >
> > > >> > >
> > > >>
> > Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > >> > > > > >    }
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > If the option 2 is the correct. How the Angular.js service
> > > >> would look
> > > >> > > > > > like? Once the username is not informed as argument on
> > > >> > > > > > pushApplicationService.js, because for obvious reasons it
> > can be
> > > >> > > > > > retrieved with HttpServletRequest.
> > > >> > > > > >
> > > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
> > would
> > > >> be to
> > > >> > > do
> > > >> > > > > > something like:
> > > >> > > > > >
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    @RolesAllowed("admin")
> > > >> > > > > >    @Path("/all")
> > > >> > > > > >    public Response listAllPushApplications(){
> > > >> > > > > >      //queries
> > > >> > > > > >    }
> > > >> > > > > >
> > > >> > > > > > And:
> > > >> > > > > >
> > > >> > > > > > backendMod.factory('pushApplication', function ($resource) {
> > > >> > > > > >  return $resource('rest/applications/all/:verb', {
> > > >> > > > > > .....
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > Help?
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > --
> > > >> > > > > >
> > > >> > > > > > abstractj
> > > >> > > > > > PGP: 0x84DC9914
> > > >> > > > > > _______________________________________________
> > > >> > > > > > aerogear-dev mailing list
> > > >> > > > > > aerogear-dev at lists.jboss.org
> > > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > > > >
> > > >> > > > > _______________________________________________
> > > >> > > > > aerogear-dev mailing list
> > > >> > > > > aerogear-dev at lists.jboss.org
> > > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > > Matthias Wessendorf
> > > >> > > >
> > > >> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > >> > > > sessions: http://www.slideshare.net/mwessendorf
> > > >> > > > twitter: http://twitter.com/mwessendorf
> > > >> > >
> > > >> > > > _______________________________________________
> > > >> > > > aerogear-dev mailing list
> > > >> > > > aerogear-dev at lists.jboss.org
> > > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > >
> > > >> > > abstractj
> > > >> > > PGP: 0x84DC9914
> > > >> > > _______________________________________________
> > > >> > > aerogear-dev mailing list
> > > >> > > aerogear-dev at lists.jboss.org
> > > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Matthias Wessendorf
> > > >> >
> > > >> > blog: http://matthiaswessendorf.wordpress.com/
> > > >> > sessions: http://www.slideshare.net/mwessendorf
> > > >> > twitter: http://twitter.com/mwessendorf
> > > >>
> > > >> > _______________________________________________
> > > >> > aerogear-dev mailing list
> > > >> > aerogear-dev at lists.jboss.org
> > > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> abstractj
> > > >> PGP: 0x84DC9914
> > > >> _______________________________________________
> > > >> aerogear-dev mailing list
> > > >> aerogear-dev at lists.jboss.org
> > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From kpiwko at redhat.com  Fri Oct 10 10:43:26 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 10 Oct 2014 16:43:26 +0200
Subject: [aerogear-dev] [UPS] 0.10.x branches
In-Reply-To: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
References: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
Message-ID: <1412952206.9097.28.camel@kpiwko-x220>

On Thu, 2014-10-09 at 11:48 +0200, Matthias Wessendorf wrote:
> Hello,
> 
> since the 0.10.x series is already out dated, I'd like to kill those
> related branches.
> Just in case a community member needs a fix on one of the 0.10.x releases,
> there are TAGs for each release. They could work on them.
> 
> Any concerns I am getting rid of them ?

Nope.

> 
> -M
> 
> _______________________________________________
> 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 Oct 10 10:45:19 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 10 Oct 2014 16:45:19 +0200
Subject: [aerogear-dev] [UPS] 0.10.x branches
In-Reply-To: <1412952206.9097.28.camel@kpiwko-x220>
References: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
	<1412952206.9097.28.camel@kpiwko-x220>
Message-ID: <CAFJm-3EnN80ESp8N1bjQ7hsfu-U6hfWmjFFZfSrzADn-rkuD1Q@mail.gmail.com>

+1 on removing them.

On 10 October 2014 16:43, Karel Piwko <kpiwko at redhat.com> wrote:

> On Thu, 2014-10-09 at 11:48 +0200, Matthias Wessendorf wrote:
> > Hello,
> >
> > since the 0.10.x series is already out dated, I'd like to kill those
> > related branches.
> > Just in case a community member needs a fix on one of the 0.10.x
> releases,
> > there are TAGs for each release. They could work on them.
> >
> > Any concerns I am getting rid of them ?
>
> Nope.
>
> >
> > -M
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141010/0f1875c0/attachment.html 

From daniel at passos.me  Fri Oct 10 10:48:40 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 10 Oct 2014 11:48:40 -0300
Subject: [aerogear-dev] Eating our own dog food,
	or TOTP demos for AeroGear
In-Reply-To: <20141010142043.GC12017@abstractj.org>
References: <20141009025611.GB70897@abstractj.org>
	<CAAg5f2RC839hhm-GUHWMv8Apjzr3BApnL1e3etj7hVm04dioRA@mail.gmail.com>
	<20141009152621.GA87979@abstractj.org>
	<CAAg5f2RjYt_qeR7HwBq12PJwO-Sq7ngyUKoe1hmynaYbKhLdsQ@mail.gmail.com>
	<20141009204232.GA2102@abstractj.org>
	<76D9BA0A-147E-4647-8AD7-1324CFD00F7C@gmail.com>
	<CAL8vO=fPweykzhx1JnM_e2EN2E+fyruL-jC73yU23LRiywZMbQ@mail.gmail.com>
	<CAAg5f2TtG7MNOgX-YJNNDt5YeUbcJXjnR_BwYA+XzQOftJORmg@mail.gmail.com>
	<CAKjsGbv6+Y+skSpQNJ5n6XATtu8kMLNvfUWRBCXF7J1ZsLkN3Q@mail.gmail.com>
	<20141010142043.GC12017@abstractj.org>
Message-ID: <CAKjsGbsivy=YDKNPzBW+68uV25YNvCSzmNrNbZYMofK3RZyGtQ@mail.gmail.com>

Jira created

On Fri, Oct 10, 2014 at 11:20 AM, Bruno Oliveira <bruno at abstractj.org>
wrote:

> On 2014-10-10, Daniel Passos wrote:
> > Hi guys,
> >
> > Yep, In Android land we have secret request and qrcode scan.
> >
> > 1) May be is a good idea remove the secret request?
>
> +1
>

https://issues.jboss.org/browse/AGDROID-299


> >
> > 2) In related news, today we not store the secret. I think store that
> > before publish is a good thing to do
>
> +1 Feel free to file jiras and assign to me if you want.
>

https://issues.jboss.org/browse/AGDROID-300


> > -- Passos
> >
> >
> > On Fri, Oct 10, 2014 at 4:47 AM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> > >
> > >
> > > On Fri, Oct 10, 2014 at 9:00 AM, Corinne Krych <corinnekrych at gmail.com
> >
> > > wrote:
> > >
> > >> Same here Bruno I would like to publish Shoot, in its Swift version to
> > >> apple store.
> > >>
> > >
> > > +1 that is even useful :)
> > > so not a "demo" at all.
> > >
> > > Great idea!
> > >
> > >
> > >> We have a ticket to enhance it with an iOS photo sharing dialog. Once
> > >> this one is done, let's submit.
> > >> For the app store I might limit it to Facebook and Google+, to start
> with.
> > >>
> > >> ++
> > >> Corinne
> > >>
> > >> On 10 October 2014 08:48, Christos Vasilakis <cvasilak at gmail.com>
> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> answers inline
> > >>>
> > >>> On Oct 9, 2014, at 11:42 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> > >>>
> > >>> > No way, Matthias. OTP must be always offline. To retrieve the
> shared
> > >>> > secret, we scan the QR Code.
> > >>> >
> > >>> > Maybe the iOS demo is doing it (have to revisit and confirm)[1].
> > >>> > On Android, I'm pretty much sure that QR Code scanning was already
> > >>> > implemented.
> > >>> >
> > >>>
> > >>> revisiting this, I can see indeed on iOS the shared secret is
> retrieved
> > >>> from the server and that is only the option offered. Our Android
> example
> > >>> offers both options, either from server, or using QR code scanning,
> so
> > >>> implementing the latter on our iOS demo need to be also done.
> > >>>
> > >>> created to track it :
> > >>>  https://issues.jboss.org/browse/AGIOS-289
> > >>>
> > >>> > We don't need to be perfect, get what is already done, improve if
> > >>> > possible or release what is already done.
> > >>>
> > >>> +1 for releasing on the app store. My fear is, as Matthias said
> earlier,
> > >>> the ?demo? aspect, but with a nice description/walkthrough submission
> > >>> details, maybe there is chance.. and tbh I have seen far far
> simplest apps
> > >>> accepted on their store.
> > >>>
> > >>>
> > >>> -
> > >>> Christos
> > >>>
> > >>>
> > >>>
> > >>> >
> > >>> > [1] -
> > >>> >
> > >>>
> https://github.com/aerogear/aerogear-otp-ios-demo/blob/5b23acbaf5c3cd74377efdd483b43a65befb11ee/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Utilities/AGOTPClient.m#L63
> > >>> >
> > >>> >
> > >>> > On 2014-10-09, Matthias Wessendorf wrote:
> > >>> >
> > >>> >> On Thu, Oct 9, 2014 at 5:26 PM, Bruno Oliveira <
> bruno at abstractj.org>
> > >>> wrote:
> > >>> >>
> > >>> >>> On 2014-10-09, Matthias Wessendorf wrote:
> > >>> >>>> On Thu, Oct 9, 2014 at 4:57 AM, Bruno Oliveira <
> bruno at abstractj.org
> > >>> >
> > >>> >>> wrote:
> > >>> >>>>
> > >>> >>>>> Good morning,
> > >>> >>>>>
> > >>> >>>>> TOTP was implemented on AeroGear for iOS[1] and Android[2] two
> > >>> years
> > >>> >>>>> ago. On conferences most of the developers get amazed with our
> API.
> > >>> >>>>>
> > >>> >>>>
> > >>> >>>> It's always great feedback when I show the OTP demo. Attendees
> at
> > >>> >>>> conferences love it!
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>>
> > >>> >>>>> Although we don't have any app published on Google Play or App
> > >>> Store. I
> > >>> >>>>> think it's time to release our demos and get some feedback
> from our
> > >>> >>>>> community.
> > >>> >>>>>
> > >>> >>>>
> > >>> >>>> with release, what do you mean? Submit to the stores?
> > >>> >>>> On Apple one reason we never submitted anything to their App
> Store
> > >>> is
> > >>> >>> their
> > >>> >>>> rules clearly indicate no demos are allowed in there.
> > >>> >>>
> > >>> >>> I understand, it can be a real and non paid app. Once it does not
> > >>> depends
> > >>> >>> on
> > >>> >>> internet connection at this moment.
> > >>> >>>
> > >>> >>
> > >>> >> isn't the iOS OTP "demo" connecting to a JAX-RS backend for the
> > >>> tokens?
> > >>> >>
> > >>> >>
> > >>> >>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>>
> > >>> >>>>> Into this way we can exercise things like:
> > >>> >>>>>
> > >>> >>>>> - Properly store the shared secret
> > >>> >>>>> - Password protection with offline authentication
> > >>> >>>>> - If we are very confident, sync the TOTPs across authorized
> > >>> devices
> > >>> >>>>>
> > >>> >>>>> At the moment, we don't need to do so much once most of our
> demos
> > >>> are
> > >>> >>>>> already on GH.
> > >>> >>>>
> > >>> >>>>
> > >>> >>>> The only thing is perhaps making sure the backend part of our
> OTP
> > >>> demo is
> > >>> >>>> (always) up :)
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>> I think it's just the matter of release it.
> > >>> >>>>>
> > >>> >>>>> Thoughts?
> > >>> >>>>>
> > >>> >>>>
> > >>> >>>> I like giving these nice demos, and their used AeroGear
> technology,
> > >>> some
> > >>> >>>> more love and visibility.
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>>
> > >>> >>>>> [1] - https://github.com/aerogear/aerogear-otp-ios-demo
> > >>> >>>>> [2] - https://github.com/aerogear/aerogear-otp-android-demo
> > >>> >>>>>
> > >>> >>>>> --
> > >>> >>>>>
> > >>> >>>>> abstractj
> > >>> >>>>> PGP: 0x84DC9914
> > >>> >>>>> _______________________________________________
> > >>> >>>>> aerogear-dev mailing list
> > >>> >>>>> aerogear-dev at lists.jboss.org
> > >>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>> >>>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>> --
> > >>> >>>> Matthias Wessendorf
> > >>> >>>>
> > >>> >>>> blog: http://matthiaswessendorf.wordpress.com/
> > >>> >>>> sessions: http://www.slideshare.net/mwessendorf
> > >>> >>>> twitter: http://twitter.com/mwessendorf
> > >>> >>>
> > >>> >>>> _______________________________________________
> > >>> >>>> aerogear-dev mailing list
> > >>> >>>> aerogear-dev at lists.jboss.org
> > >>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>> >>>
> > >>> >>>
> > >>> >>> --
> > >>> >>>
> > >>> >>> abstractj
> > >>> >>> PGP: 0x84DC9914
> > >>> >>> _______________________________________________
> > >>> >>> aerogear-dev mailing list
> > >>> >>> aerogear-dev at lists.jboss.org
> > >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>> >>>
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> --
> > >>> >> Matthias Wessendorf
> > >>> >>
> > >>> >> blog: http://matthiaswessendorf.wordpress.com/
> > >>> >> sessions: http://www.slideshare.net/mwessendorf
> > >>> >> twitter: http://twitter.com/mwessendorf
> > >>> >
> > >>> >> _______________________________________________
> > >>> >> aerogear-dev mailing list
> > >>> >> aerogear-dev at lists.jboss.org
> > >>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>> >
> > >>> >
> > >>> > --
> > >>> >
> > >>> > abstractj
> > >>> > PGP: 0x84DC9914
> > >>> > _______________________________________________
> > >>> > aerogear-dev mailing list
> > >>> > aerogear-dev at lists.jboss.org
> > >>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> aerogear-dev mailing list
> > >>> aerogear-dev at lists.jboss.org
> > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>>
> > >>
> > >>
> > >> _______________________________________________
> > >> aerogear-dev mailing list
> > >> aerogear-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >>
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141010/43a5fdf3/attachment-0001.html 

From matzew at apache.org  Fri Oct 10 10:51:36 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 10 Oct 2014 16:51:36 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <1412951959.9097.27.camel@kpiwko-x220>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
	<20141010140559.GB11110@abstractj.org>
	<CAAg5f2RSuoyaeM6iy55dj1s+6agGYwZrFwLGs-MVx063uP3EDQ@mail.gmail.com>
	<1412951959.9097.27.camel@kpiwko-x220>
Message-ID: <CAAg5f2TufbLfRKf5-=+2FWhpB42BnqTCNrkfx3H7BxTC4JtOLQ@mail.gmail.com>

On Fri, Oct 10, 2014 at 4:39 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> On Fri, 2014-10-10 at 16:11 +0200, Matthias Wessendorf wrote:
> > I like this:
> >
> > boolean isAdmin = securityContext.isUserInRole("admin");
> > return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> > extractUsername(request))).build();
>
> Can we ensure that admin and developer will be only roles on UPS for
> ever? If not, securityContext seems like a better option to me - more
> flexible.
>


for now - yes!
On future, things may change, as said in an earlier email, and things will
be addressed at that time


>
> >
> >
> >
> > On Fri, Oct 10, 2014 at 4:06 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > +1 and one more question. During the hangouts we agreed on move this to
> > > the service[1]. The downside is the fact that our service doesn't have
> > > SecurityContext as maven dependency, which would imply on add it.
> > >
> > > What works best to YOU GUYS (the team :P). Leave it as is:
> > >
> > >
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> > >
> > > Or:
> > >
> > > boolean isAdmin = securityContext.isUserInRole("admin");
> > > return
> Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> > > extractUsername(request))).build();
> > >
> > > Or:
> > >
> > > return
> > >
> Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
> > > extractUsername(request))).build();
> > >
> > >
> > > [1] -
> > >
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> > >
> > > On 2014-10-10, Matthias Wessendorf wrote:
> > > > hangout result: no need to add lot's of IFs - since only the
> "finder" for
> > > > PushApplications will have a different behavior (meaning for admin ->
> > > all;
> > > > for developer -> just my own apps)
> > > > At this point no need of a specific admin-ish endpoint, nor no need
> to
> > > > create a new "admin" UI.
> > > >
> > > > However, once we are in a need to do more tweaks for an admin user
> (e.g.
> > > in
> > > > a year or so): yes, there should not be any more IFs but a more
> cleaner
> > > > approcah, like extra classes as Bruno did suggest.
> > > >
> > > > Cheers!
> > > >
> > > >
> > > > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <
> matzew at apache.org>
> > > > wrote:
> > > >
> > > > > "you guys" :)
> > > > >
> > > > > I think the only different between 'admin' and developer' role is
> > > really
> > > > > the result of the "findAllPushApplicationsForDeveloper()"
> > > > >
> > > > > everything else would be the same
> > > > >
> > > > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <
> bruno at abstractj.org>
> > > > > wrote:
> > > > >
> > > > >> I really want to confirm this. So this is what you guys want:
> > > > >>
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> > > > >>
> > > > >> And with more methods we add more IFs, right?
> > > > >>
> > > > >> On 2014-10-10, Matthias Wessendorf wrote:
> > > > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <
> bruno at abstractj.org
> > > >
> > > > >> wrote:
> > > > >> >
> > > > >> > > On 2014-10-09, Matthias Wessendorf wrote:
> > > > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> > > > >> scm.blanc at gmail.com>
> > > > >> > > wrote:
> > > > >> > > >
> > > > >> > > > > Another option could be :
> > > > >> > > > > - no change or addition of any endpoint
> > > > >> > > > > -no change on the angular side
> > > > >> > > > >
> > > > >> > > > > Since the result is the same : we want a list of
> applications
> > > (for
> > > > >> > > admin
> > > > >> > > > > there is just no restriction on developer that owns it)
> > > > >> > > > > But in the service layer when retrieving the applications
> we
> > > > >> check the
> > > > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
> > > add the
> > > > >> > > criteria
> > > > >> > > > > of developer.
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > > yeah, that;s what I had in my email from last night as
> well. the
> > > > >> service
> > > > >> > > > returns a list of applications.
> > > > >> > >
> > > > >> > > I think this is very clear to everyone and the basic
> principle of
> > > this
> > > > >> > > jira.
> > > > >> > >
> > > > >> > > > Inside we handle the different cases:
> > > > >> > > > - admin
> > > > >> > > >    Select all (e.g. "select pa from PushApplication pa")
> > > > >> > > > -developer
> > > > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
> > > where
> > > > >> > > > pa.developer = :loginName")
> > > > >> > >
> > > > >> > > This is the recommendation from KC documentation
> > > > >> > >
> > > > >> > >
> > > > >>
> > >
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > > > >> > > .
> > > > >> > >
> > > > >> >
> > > > >> > I understand their example, but we don't really (within UPS)
> have a
> > > > >> > completely different UI between "admin" and "developer" roles.
> > > > >> >
> > > > >> >
> > > > >> > >
> > > > >> > > So what do you guys suggest is: If I have several methods to
> > > validate
> > > > >> > > multiple roles, just add if/else all along the UPS code? And
> if I
> > > > >> have a
> > > > >> > > new
> > > > >> > > role, include more ifs?
> > > > >> > >
> > > > >> > > I think it can be done inject the SecurityContext, have to
> check
> > > with
> > > > >> > > Stian and Bill. But it doesn't seem right.
> > > > >> > >
> > > > >> >
> > > > >> > might not be the most elegant, but looks like it avoids adding
> too
> > > much
> > > > >> new
> > > > >> > code. Especially since the UI for 'admin' and 'developer' is
> pretty
> > > much
> > > > >> > the same.
> > > > >> >
> > > > >> >
> > > > >> > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > -Matthias
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > >
> > > > >> > > > > Envoy? de mon iPhone
> > > > >> > > > >
> > > > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <
> bruno at abstractj.org>
> > > a
> > > > >> > > ?crit :
> > > > >> > > > > >
> > > > >> > > > > > Good morning, moving forward with
> > > > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is
> the
> > > most
> > > > >> > > > > > recommended approach for admin-ui.
> > > > >> > > > > >
> > > > >> > > > > > Have separated endpoints for the admin like:
> > > > >> > > > > >
> > > > >> > > > > > 1.
> > > > >> > > > > >
> > > > >> > > > > > @RolesAllowed("admin")
> > > > >> > > > > > @Path("/admin/applications")
> > > > >> > > > > > public class AdminApplicationEndpoint extends
> > > > >> AbstractBaseEndpoint {
> > > > >> > > > > >
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    public Response listAllPushApplications(){
> > > > >> > > > > >        //queries
> > > > >> > > > > >    }
> > > > >> > > > > > }
> > > > >> > > > > >
> > > > >> > > > > > Or introduce a new method inside the current
> > > > >> PushApplicationEndpoint:
> > > > >> > > > > >
> > > > >> > > > > > 2.
> > > > >> > > > > >
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    @RolesAllowed("admin")
> > > > >> > > > > >    public Response listAllPushApplications(){
> > > > >> > > > > >      //queries
> > > > >> > > > > >    }
> > > > >> > > > > >    // READ
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    public Response
> > > listAllPushApplicationsByUsername(@Context
> > > > >> > > > > HttpServletRequest request) {
> > > > >> > > > > >        return
> > > > >> > > > >
> > > > >> > >
> > > > >>
> > >
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > > >> > > > > >    }
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > If the option 2 is the correct. How the Angular.js
> service
> > > > >> would look
> > > > >> > > > > > like? Once the username is not informed as argument on
> > > > >> > > > > > pushApplicationService.js, because for obvious reasons
> it
> > > can be
> > > > >> > > > > > retrieved with HttpServletRequest.
> > > > >> > > > > >
> > > > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
> > > would
> > > > >> be to
> > > > >> > > do
> > > > >> > > > > > something like:
> > > > >> > > > > >
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    @RolesAllowed("admin")
> > > > >> > > > > >    @Path("/all")
> > > > >> > > > > >    public Response listAllPushApplications(){
> > > > >> > > > > >      //queries
> > > > >> > > > > >    }
> > > > >> > > > > >
> > > > >> > > > > > And:
> > > > >> > > > > >
> > > > >> > > > > > backendMod.factory('pushApplication', function
> ($resource) {
> > > > >> > > > > >  return $resource('rest/applications/all/:verb', {
> > > > >> > > > > > .....
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > Help?
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > --
> > > > >> > > > > >
> > > > >> > > > > > abstractj
> > > > >> > > > > > PGP: 0x84DC9914
> > > > >> > > > > > _______________________________________________
> > > > >> > > > > > aerogear-dev mailing list
> > > > >> > > > > > aerogear-dev at lists.jboss.org
> > > > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > > > >
> > > > >> > > > > _______________________________________________
> > > > >> > > > > aerogear-dev mailing list
> > > > >> > > > > aerogear-dev at lists.jboss.org
> > > > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > --
> > > > >> > > > Matthias Wessendorf
> > > > >> > > >
> > > > >> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > >> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > >> > > > twitter: http://twitter.com/mwessendorf
> > > > >> > >
> > > > >> > > > _______________________________________________
> > > > >> > > > aerogear-dev mailing list
> > > > >> > > > aerogear-dev at lists.jboss.org
> > > > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > >
> > > > >> > > abstractj
> > > > >> > > PGP: 0x84DC9914
> > > > >> > > _______________________________________________
> > > > >> > > aerogear-dev mailing list
> > > > >> > > aerogear-dev at lists.jboss.org
> > > > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Matthias Wessendorf
> > > > >> >
> > > > >> > blog: http://matthiaswessendorf.wordpress.com/
> > > > >> > sessions: http://www.slideshare.net/mwessendorf
> > > > >> > twitter: http://twitter.com/mwessendorf
> > > > >>
> > > > >> > _______________________________________________
> > > > >> > aerogear-dev mailing list
> > > > >> > aerogear-dev at lists.jboss.org
> > > > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >>
> > > > >>
> > > > >> --
> > > > >>
> > > > >> abstractj
> > > > >> PGP: 0x84DC9914
> > > > >> _______________________________________________
> > > > >> aerogear-dev mailing list
> > > > >> aerogear-dev at lists.jboss.org
> > > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > twitter: http://twitter.com/mwessendorf
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Fri Oct 10 12:06:20 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 10 Oct 2014 13:06:20 -0300
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAFJm-3HWagxTERsgDu_ZvqS0FQbfFGXsd90Bb0PYZ5HfYen4xw@mail.gmail.com>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
	<20141010140559.GB11110@abstractj.org>
	<CAFJm-3HWagxTERsgDu_ZvqS0FQbfFGXsd90Bb0PYZ5HfYen4xw@mail.gmail.com>
Message-ID: <20141010160620.GA13584@abstractj.org>

Hi Dan, that would imply on having an extra Maven dependency into the
services, not sure if we want it.

I will attach a PR and ask for you review.

On 2014-10-10, Daniel Bevenius wrote:
> Just a thought here...is the securityContext used elsewhere in the
> PushApplicationEndpoint class?
> If not, perhaps we could have it injected into the PushAppService class not
> have to pass anything into the findAllPushApplicationsByUser method?
>
>
> On 10 October 2014 16:06, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > +1 and one more question. During the hangouts we agreed on move this to
> > the service[1]. The downside is the fact that our service doesn't have
> > SecurityContext as maven dependency, which would imply on add it.
> >
> > What works best to YOU GUYS (the team :P). Leave it as is:
> >
> >
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> >
> > Or:
> >
> > boolean isAdmin = securityContext.isUserInRole("admin");
> > return Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> > extractUsername(request))).build();
> >
> > Or:
> >
> > return
> > Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
> > extractUsername(request))).build();
> >
> >
> > [1] -
> >
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> >
> > On 2014-10-10, Matthias Wessendorf wrote:
> > > hangout result: no need to add lot's of IFs - since only the "finder" for
> > > PushApplications will have a different behavior (meaning for admin ->
> > all;
> > > for developer -> just my own apps)
> > > At this point no need of a specific admin-ish endpoint, nor no need to
> > > create a new "admin" UI.
> > >
> > > However, once we are in a need to do more tweaks for an admin user (e.g.
> > in
> > > a year or so): yes, there should not be any more IFs but a more cleaner
> > > approcah, like extra classes as Bruno did suggest.
> > >
> > > Cheers!
> > >
> > >
> > > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <matzew at apache.org>
> > > wrote:
> > >
> > > > "you guys" :)
> > > >
> > > > I think the only different between 'admin' and developer' role is
> > really
> > > > the result of the "findAllPushApplicationsForDeveloper()"
> > > >
> > > > everything else would be the same
> > > >
> > > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <bruno at abstractj.org>
> > > > wrote:
> > > >
> > > >> I really want to confirm this. So this is what you guys want:
> > > >>
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> > > >> -
> > > >>
> > https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> > > >>
> > > >> And with more methods we add more IFs, right?
> > > >>
> > > >> On 2014-10-10, Matthias Wessendorf wrote:
> > > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <bruno at abstractj.org
> > >
> > > >> wrote:
> > > >> >
> > > >> > > On 2014-10-09, Matthias Wessendorf wrote:
> > > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> > > >> scm.blanc at gmail.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > > Another option could be :
> > > >> > > > > - no change or addition of any endpoint
> > > >> > > > > -no change on the angular side
> > > >> > > > >
> > > >> > > > > Since the result is the same : we want a list of applications
> > (for
> > > >> > > admin
> > > >> > > > > there is just no restriction on developer that owns it)
> > > >> > > > > But in the service layer when retrieving the applications we
> > > >> check the
> > > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
> > add the
> > > >> > > criteria
> > > >> > > > > of developer.
> > > >> > > > >
> > > >> > > >
> > > >> > > > yeah, that;s what I had in my email from last night as well. the
> > > >> service
> > > >> > > > returns a list of applications.
> > > >> > >
> > > >> > > I think this is very clear to everyone and the basic principle of
> > this
> > > >> > > jira.
> > > >> > >
> > > >> > > > Inside we handle the different cases:
> > > >> > > > - admin
> > > >> > > >    Select all (e.g. "select pa from PushApplication pa")
> > > >> > > > -developer
> > > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
> > where
> > > >> > > > pa.developer = :loginName")
> > > >> > >
> > > >> > > This is the recommendation from KC documentation
> > > >> > >
> > > >> > >
> > > >>
> > http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > > >> > > .
> > > >> > >
> > > >> >
> > > >> > I understand their example, but we don't really (within UPS) have a
> > > >> > completely different UI between "admin" and "developer" roles.
> > > >> >
> > > >> >
> > > >> > >
> > > >> > > So what do you guys suggest is: If I have several methods to
> > validate
> > > >> > > multiple roles, just add if/else all along the UPS code? And if I
> > > >> have a
> > > >> > > new
> > > >> > > role, include more ifs?
> > > >> > >
> > > >> > > I think it can be done inject the SecurityContext, have to check
> > with
> > > >> > > Stian and Bill. But it doesn't seem right.
> > > >> > >
> > > >> >
> > > >> > might not be the most elegant, but looks like it avoids adding too
> > much
> > > >> new
> > > >> > code. Especially since the UI for 'admin' and 'developer' is pretty
> > much
> > > >> > the same.
> > > >> >
> > > >> >
> > > >> > >
> > > >> > > >
> > > >> > > >
> > > >> > > > -Matthias
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > >
> > > >> > > > > Envoy? de mon iPhone
> > > >> > > > >
> > > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <bruno at abstractj.org>
> > a
> > > >> > > ?crit :
> > > >> > > > > >
> > > >> > > > > > Good morning, moving forward with
> > > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is the
> > most
> > > >> > > > > > recommended approach for admin-ui.
> > > >> > > > > >
> > > >> > > > > > Have separated endpoints for the admin like:
> > > >> > > > > >
> > > >> > > > > > 1.
> > > >> > > > > >
> > > >> > > > > > @RolesAllowed("admin")
> > > >> > > > > > @Path("/admin/applications")
> > > >> > > > > > public class AdminApplicationEndpoint extends
> > > >> AbstractBaseEndpoint {
> > > >> > > > > >
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    public Response listAllPushApplications(){
> > > >> > > > > >        //queries
> > > >> > > > > >    }
> > > >> > > > > > }
> > > >> > > > > >
> > > >> > > > > > Or introduce a new method inside the current
> > > >> PushApplicationEndpoint:
> > > >> > > > > >
> > > >> > > > > > 2.
> > > >> > > > > >
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    @RolesAllowed("admin")
> > > >> > > > > >    public Response listAllPushApplications(){
> > > >> > > > > >      //queries
> > > >> > > > > >    }
> > > >> > > > > >    // READ
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    public Response
> > listAllPushApplicationsByUsername(@Context
> > > >> > > > > HttpServletRequest request) {
> > > >> > > > > >        return
> > > >> > > > >
> > > >> > >
> > > >>
> > Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > >> > > > > >    }
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > If the option 2 is the correct. How the Angular.js service
> > > >> would look
> > > >> > > > > > like? Once the username is not informed as argument on
> > > >> > > > > > pushApplicationService.js, because for obvious reasons it
> > can be
> > > >> > > > > > retrieved with HttpServletRequest.
> > > >> > > > > >
> > > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
> > would
> > > >> be to
> > > >> > > do
> > > >> > > > > > something like:
> > > >> > > > > >
> > > >> > > > > >    @GET
> > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > >> > > > > >    @RolesAllowed("admin")
> > > >> > > > > >    @Path("/all")
> > > >> > > > > >    public Response listAllPushApplications(){
> > > >> > > > > >      //queries
> > > >> > > > > >    }
> > > >> > > > > >
> > > >> > > > > > And:
> > > >> > > > > >
> > > >> > > > > > backendMod.factory('pushApplication', function ($resource) {
> > > >> > > > > >  return $resource('rest/applications/all/:verb', {
> > > >> > > > > > .....
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > Help?
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > --
> > > >> > > > > >
> > > >> > > > > > abstractj
> > > >> > > > > > PGP: 0x84DC9914
> > > >> > > > > > _______________________________________________
> > > >> > > > > > aerogear-dev mailing list
> > > >> > > > > > aerogear-dev at lists.jboss.org
> > > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > > > >
> > > >> > > > > _______________________________________________
> > > >> > > > > aerogear-dev mailing list
> > > >> > > > > aerogear-dev at lists.jboss.org
> > > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > > Matthias Wessendorf
> > > >> > > >
> > > >> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > >> > > > sessions: http://www.slideshare.net/mwessendorf
> > > >> > > > twitter: http://twitter.com/mwessendorf
> > > >> > >
> > > >> > > > _______________________________________________
> > > >> > > > aerogear-dev mailing list
> > > >> > > > aerogear-dev at lists.jboss.org
> > > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > >
> > > >> > > abstractj
> > > >> > > PGP: 0x84DC9914
> > > >> > > _______________________________________________
> > > >> > > aerogear-dev mailing list
> > > >> > > aerogear-dev at lists.jboss.org
> > > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Matthias Wessendorf
> > > >> >
> > > >> > blog: http://matthiaswessendorf.wordpress.com/
> > > >> > sessions: http://www.slideshare.net/mwessendorf
> > > >> > twitter: http://twitter.com/mwessendorf
> > > >>
> > > >> > _______________________________________________
> > > >> > aerogear-dev mailing list
> > > >> > aerogear-dev at lists.jboss.org
> > > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> abstractj
> > > >> PGP: 0x84DC9914
> > > >> _______________________________________________
> > > >> aerogear-dev mailing list
> > > >> aerogear-dev at lists.jboss.org
> > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

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


--

abstractj
PGP: 0x84DC9914

From qmx at qmx.me  Fri Oct 10 13:03:34 2014
From: qmx at qmx.me (Douglas Campos)
Date: Fri, 10 Oct 2014 14:03:34 -0300
Subject: [aerogear-dev] [UPS] 0.10.x branches
In-Reply-To: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
References: <CAAg5f2Q3wp8iFMeTApt65KHe_9E+goO7J87U8XDJJFpvb=SBxg@mail.gmail.com>
Message-ID: <20141010170334.GA56451@darkstar.local>

go for it!

-- 
qmx

From lholmqui at redhat.com  Fri Oct 10 22:01:41 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 10 Oct 2014 22:01:41 -0400
Subject: [aerogear-dev] AeroGear.js 2.0.0-beta1
Message-ID: <B85217D1-66D1-43AF-81C3-0B84DD1DAB74@redhat.com>

The first beta release of AeroGear.js 2.0 is out and ready for you to test it!

There's been a bunch of changes that could possibly break existing code as well as some things that have been removed.

Pipeline

It was deteremined that Pipeline and pipes did not add much value since it was basically a wrapper on top of jQuery Ajax.

So Pipeline and pipes have been completely removed in 2.0

If this was something that you used, they will still live on in the 1.X branch

Authentication

Similar to Pipeline, the Auth module didn't really add any value to the library, so this has also been removed.

Again It will live on in the 1.X branch

Datamanager

One of the big things that has changed in Datamanager is that it is no longer dependent on jQuery.

The other thing is that we have fully embraced es6 Promises. Which means we have removed callbacks.

For the IndexedDB and WebSQL adapters, the auto param has now been updated to default to true. This means that you no longer have to excplitly call open.

So instead of doing something like this:

idbStore.open(...).then(function () {
    idbStore.read(...)
});
You can now just do

idbStore.read(...)
Ajax Promises

We also updated the internal Ajax library to just use promises also.

This is used by both the UnifiedPush SDK and the Authz OAuth2 module.

Since ES6 promises only have 1 return value we return an object with this signature:

{
    data: dataOrError, - the data or an error
    statusText: statusText, - the status of the response
    agXHR: request - the xhr request object
};
Cookbook Examples

The cookbook examples have also been updated with the 2.0.0 beta1 version and can be found in this branch

Integration Tests

Last but not least the Integration tests have been completly reworked, thanks to lfryc!!!

The PR's for these are https://github.com/aerogear/aerogear-js-integration/pull/12

and

https://github.com/aerogear/aerogear-js/pull/150

Release Notes - AeroGear JavaScript - Version 2.0.0

Bug

[AGJS-184] - Vertx and SimplePush integration tests execution issues
Feature Request

[AGJS-201] - XMLHttpRequest#response not implemented in Sinon.JS lib & authentication unit tests fail
[AGJS-251] - DataManager - Auto connect options should default to true
Task

[AGJS-189] - Review DevDependencies Versions
[AGJS-211] - Rework Integration Tests from the ground up
[AGJS-228] - Deprecate Pipeline
[AGJS-229] - Deprecate Authentication Module
[AGJS-232] - Remove AeroGear.isArray method from core
[AGJS-233] - Remove pipeline integration tests
[AGJS-234] - Promisify Library
[AGJS-242] - Update cookbook examples with deprecation notices, etc...
[AGJS-248] - Move the SimplePush and UnifiedPush examples to the real js-cookbook
Sub-task

[AGJS-42] - Remove jQuery dependency from DataManager; embrace Promises instead
[AGJS-162] - Remove jQuery Dependency from Auth
[AGJS-212] - Update to express 4
[AGJS-231] - Update Authz cookbook example without pipeline
[AGJS-235] - Promisify Datamanager
[AGJS-236] - Promisfy Crypto
[AGJS-237] - Promisfy Notifier
[AGJS-238] - Promisfy UnifiedPush client
[AGJS-239] - Promisfy Authorization
[AGJS-240] - Promisfy SimplePush
[AGJS-243] - Add deprecation Notice for Pipeline Cookbook example
[AGJS-244] - Add deprecation notice on Auth cookbook example
[AGJS-245] - Promisify AeroGear.ajax
[AGJS-246] - Update unified push example to use just promises
[AGJS-247] - Update Datamanager example to use promises not callbacks

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

From daniel.bevenius at gmail.com  Sat Oct 11 03:53:00 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Sat, 11 Oct 2014 09:53:00 +0200
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <20141010160620.GA13584@abstractj.org>
References: <20141009154544.GA88134@abstractj.org>
	<FC79D500-18CF-427F-AE8B-7F01588EDFC4@gmail.com>
	<CAAg5f2QsOF8Yoez-XfsKmmaQF3uwY0ZEnHxjHPyJVpF4kz3Cfw@mail.gmail.com>
	<20141009195832.GC727@abstractj.org>
	<CAAg5f2TZAMuRC4ZKMgL2x7wJwtLGPUkTR27H6YhFCdmt+ESjOg@mail.gmail.com>
	<20141010133623.GA11110@abstractj.org>
	<CAAg5f2Qf-KnJ0m3eRx=HkE25gRDi2aHeC2wnFp6nQX6UQ__7Ew@mail.gmail.com>
	<CAAg5f2QRr3RJuGcLQajqhTzfFw-RKER6G1BtrWLu96H49A2dQg@mail.gmail.com>
	<20141010140559.GB11110@abstractj.org>
	<CAFJm-3HWagxTERsgDu_ZvqS0FQbfFGXsd90Bb0PYZ5HfYen4xw@mail.gmail.com>
	<20141010160620.GA13584@abstractj.org>
Message-ID: <CAFJm-3GMQwkSrLADOGnF-kfMj8dxdzCA94xSzR9ioU-BVfYucg@mail.gmail.com>

Hey Bruno,

ah I see. I've been lazy and did not take a closer look and if this would
add an extra dependency that does not sounds good.



On 10 October 2014 18:06, Bruno Oliveira <bruno at abstractj.org> wrote:

> Hi Dan, that would imply on having an extra Maven dependency into the
> services, not sure if we want it.
>
> I will attach a PR and ask for you review.
>
> On 2014-10-10, Daniel Bevenius wrote:
> > Just a thought here...is the securityContext used elsewhere in the
> > PushApplicationEndpoint class?
> > If not, perhaps we could have it injected into the PushAppService class
> not
> > have to pass anything into the findAllPushApplicationsByUser method?
> >
> >
> > On 10 October 2014 16:06, Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> > > +1 and one more question. During the hangouts we agreed on move this to
> > > the service[1]. The downside is the fact that our service doesn't have
> > > SecurityContext as maven dependency, which would imply on add it.
> > >
> > > What works best to YOU GUYS (the team :P). Leave it as is:
> > >
> > >
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> > >
> > > Or:
> > >
> > > boolean isAdmin = securityContext.isUserInRole("admin");
> > > return
> Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
> > > extractUsername(request))).build();
> > >
> > > Or:
> > >
> > > return
> > >
> Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
> > > extractUsername(request))).build();
> > >
> > >
> > > [1] -
> > >
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
> > >
> > > On 2014-10-10, Matthias Wessendorf wrote:
> > > > hangout result: no need to add lot's of IFs - since only the
> "finder" for
> > > > PushApplications will have a different behavior (meaning for admin ->
> > > all;
> > > > for developer -> just my own apps)
> > > > At this point no need of a specific admin-ish endpoint, nor no need
> to
> > > > create a new "admin" UI.
> > > >
> > > > However, once we are in a need to do more tweaks for an admin user
> (e.g.
> > > in
> > > > a year or so): yes, there should not be any more IFs but a more
> cleaner
> > > > approcah, like extra classes as Bruno did suggest.
> > > >
> > > > Cheers!
> > > >
> > > >
> > > > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <
> matzew at apache.org>
> > > > wrote:
> > > >
> > > > > "you guys" :)
> > > > >
> > > > > I think the only different between 'admin' and developer' role is
> > > really
> > > > > the result of the "findAllPushApplicationsForDeveloper()"
> > > > >
> > > > > everything else would be the same
> > > > >
> > > > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <
> bruno at abstractj.org>
> > > > > wrote:
> > > > >
> > > > >> I really want to confirm this. So this is what you guys want:
> > > > >>
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
> > > > >> -
> > > > >>
> > >
> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
> > > > >>
> > > > >> And with more methods we add more IFs, right?
> > > > >>
> > > > >> On 2014-10-10, Matthias Wessendorf wrote:
> > > > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <
> bruno at abstractj.org
> > > >
> > > > >> wrote:
> > > > >> >
> > > > >> > > On 2014-10-09, Matthias Wessendorf wrote:
> > > > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
> > > > >> scm.blanc at gmail.com>
> > > > >> > > wrote:
> > > > >> > > >
> > > > >> > > > > Another option could be :
> > > > >> > > > > - no change or addition of any endpoint
> > > > >> > > > > -no change on the angular side
> > > > >> > > > >
> > > > >> > > > > Since the result is the same : we want a list of
> applications
> > > (for
> > > > >> > > admin
> > > > >> > > > > there is just no restriction on developer that owns it)
> > > > >> > > > > But in the service layer when retrieving the applications
> we
> > > > >> check the
> > > > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
> > > add the
> > > > >> > > criteria
> > > > >> > > > > of developer.
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > > yeah, that;s what I had in my email from last night as
> well. the
> > > > >> service
> > > > >> > > > returns a list of applications.
> > > > >> > >
> > > > >> > > I think this is very clear to everyone and the basic
> principle of
> > > this
> > > > >> > > jira.
> > > > >> > >
> > > > >> > > > Inside we handle the different cases:
> > > > >> > > > - admin
> > > > >> > > >    Select all (e.g. "select pa from PushApplication pa")
> > > > >> > > > -developer
> > > > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
> > > where
> > > > >> > > > pa.developer = :loginName")
> > > > >> > >
> > > > >> > > This is the recommendation from KC documentation
> > > > >> > >
> > > > >> > >
> > > > >>
> > >
> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
> > > > >> > > .
> > > > >> > >
> > > > >> >
> > > > >> > I understand their example, but we don't really (within UPS)
> have a
> > > > >> > completely different UI between "admin" and "developer" roles.
> > > > >> >
> > > > >> >
> > > > >> > >
> > > > >> > > So what do you guys suggest is: If I have several methods to
> > > validate
> > > > >> > > multiple roles, just add if/else all along the UPS code? And
> if I
> > > > >> have a
> > > > >> > > new
> > > > >> > > role, include more ifs?
> > > > >> > >
> > > > >> > > I think it can be done inject the SecurityContext, have to
> check
> > > with
> > > > >> > > Stian and Bill. But it doesn't seem right.
> > > > >> > >
> > > > >> >
> > > > >> > might not be the most elegant, but looks like it avoids adding
> too
> > > much
> > > > >> new
> > > > >> > code. Especially since the UI for 'admin' and 'developer' is
> pretty
> > > much
> > > > >> > the same.
> > > > >> >
> > > > >> >
> > > > >> > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > -Matthias
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > >
> > > > >> > > > > Envoy? de mon iPhone
> > > > >> > > > >
> > > > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <
> bruno at abstractj.org>
> > > a
> > > > >> > > ?crit :
> > > > >> > > > > >
> > > > >> > > > > > Good morning, moving forward with
> > > > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is
> the
> > > most
> > > > >> > > > > > recommended approach for admin-ui.
> > > > >> > > > > >
> > > > >> > > > > > Have separated endpoints for the admin like:
> > > > >> > > > > >
> > > > >> > > > > > 1.
> > > > >> > > > > >
> > > > >> > > > > > @RolesAllowed("admin")
> > > > >> > > > > > @Path("/admin/applications")
> > > > >> > > > > > public class AdminApplicationEndpoint extends
> > > > >> AbstractBaseEndpoint {
> > > > >> > > > > >
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    public Response listAllPushApplications(){
> > > > >> > > > > >        //queries
> > > > >> > > > > >    }
> > > > >> > > > > > }
> > > > >> > > > > >
> > > > >> > > > > > Or introduce a new method inside the current
> > > > >> PushApplicationEndpoint:
> > > > >> > > > > >
> > > > >> > > > > > 2.
> > > > >> > > > > >
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    @RolesAllowed("admin")
> > > > >> > > > > >    public Response listAllPushApplications(){
> > > > >> > > > > >      //queries
> > > > >> > > > > >    }
> > > > >> > > > > >    // READ
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    public Response
> > > listAllPushApplicationsByUsername(@Context
> > > > >> > > > > HttpServletRequest request) {
> > > > >> > > > > >        return
> > > > >> > > > >
> > > > >> > >
> > > > >>
> > >
> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
> > > > >> > > > > >    }
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > If the option 2 is the correct. How the Angular.js
> service
> > > > >> would look
> > > > >> > > > > > like? Once the username is not informed as argument on
> > > > >> > > > > > pushApplicationService.js, because for obvious reasons
> it
> > > can be
> > > > >> > > > > > retrieved with HttpServletRequest.
> > > > >> > > > > >
> > > > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
> > > would
> > > > >> be to
> > > > >> > > do
> > > > >> > > > > > something like:
> > > > >> > > > > >
> > > > >> > > > > >    @GET
> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
> > > > >> > > > > >    @RolesAllowed("admin")
> > > > >> > > > > >    @Path("/all")
> > > > >> > > > > >    public Response listAllPushApplications(){
> > > > >> > > > > >      //queries
> > > > >> > > > > >    }
> > > > >> > > > > >
> > > > >> > > > > > And:
> > > > >> > > > > >
> > > > >> > > > > > backendMod.factory('pushApplication', function
> ($resource) {
> > > > >> > > > > >  return $resource('rest/applications/all/:verb', {
> > > > >> > > > > > .....
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > Help?
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > --
> > > > >> > > > > >
> > > > >> > > > > > abstractj
> > > > >> > > > > > PGP: 0x84DC9914
> > > > >> > > > > > _______________________________________________
> > > > >> > > > > > aerogear-dev mailing list
> > > > >> > > > > > aerogear-dev at lists.jboss.org
> > > > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > > > >
> > > > >> > > > > _______________________________________________
> > > > >> > > > > aerogear-dev mailing list
> > > > >> > > > > aerogear-dev at lists.jboss.org
> > > > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > --
> > > > >> > > > Matthias Wessendorf
> > > > >> > > >
> > > > >> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > >> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > >> > > > twitter: http://twitter.com/mwessendorf
> > > > >> > >
> > > > >> > > > _______________________________________________
> > > > >> > > > aerogear-dev mailing list
> > > > >> > > > aerogear-dev at lists.jboss.org
> > > > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > >
> > > > >> > > abstractj
> > > > >> > > PGP: 0x84DC9914
> > > > >> > > _______________________________________________
> > > > >> > > aerogear-dev mailing list
> > > > >> > > aerogear-dev at lists.jboss.org
> > > > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Matthias Wessendorf
> > > > >> >
> > > > >> > blog: http://matthiaswessendorf.wordpress.com/
> > > > >> > sessions: http://www.slideshare.net/mwessendorf
> > > > >> > twitter: http://twitter.com/mwessendorf
> > > > >>
> > > > >> > _______________________________________________
> > > > >> > aerogear-dev mailing list
> > > > >> > aerogear-dev at lists.jboss.org
> > > > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >>
> > > > >>
> > > > >> --
> > > > >>
> > > > >> abstractj
> > > > >> PGP: 0x84DC9914
> > > > >> _______________________________________________
> > > > >> aerogear-dev mailing list
> > > > >> aerogear-dev at lists.jboss.org
> > > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > twitter: http://twitter.com/mwessendorf
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141011/db68294a/attachment-0001.html 

From matzew at apache.org  Sat Oct 11 05:38:36 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 11 Oct 2014 11:38:36 +0200
Subject: [aerogear-dev] AeroGear.js 2.0.0-beta1
In-Reply-To: <B85217D1-66D1-43AF-81C3-0B84DD1DAB74@redhat.com>
References: <B85217D1-66D1-43AF-81C3-0B84DD1DAB74@redhat.com>
Message-ID: <CAAg5f2TUTXxj8AyB8d07UCpO0+AYezO6aDeUTFurYczN6OJyPQ@mail.gmail.com>

Sounds good!

regarding "Pipeline"  and "Authentication" do we have a doc that helps to
migrate away?

On Sat, Oct 11, 2014 at 4:01 AM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

> The first beta release of AeroGear.js 2.0
> <https://github.com/aerogear/aerogear-js/releases/tag/2.0.0-beta1> is out
> and ready for you to test it!
>
> There's been a bunch of changes that could possibly break existing code as
> well as some things that have been removed.
> Pipeline
>
> It was deteremined that Pipeline and pipes did not add much value since it
> was basically a wrapper on top of jQuery Ajax.
>
> So Pipeline and pipes have been completely removed in 2.0
>
> If this was something that you used, they will still live on in the 1.X
> branch
> Authentication
>
> Similar to Pipeline, the Auth module didn't really add any value to the
> library, so this has also been removed.
>
> Again It will live on in the 1.X branch
> Datamanager
>
> One of the big things that has changed in Datamanager is that it is no
> longer dependent on jQuery.
>
> The other thing is that we have fully embraced es6 Promises. Which means
> we have removed callbacks.
>
> For the IndexedDB and WebSQL adapters, the auto param has now been
> updated to default to true. This means that you no longer have to
> excplitly call open.
>
> So instead of doing something like this:
>
> idbStore.open(...).then(function () {
>     idbStore.read(...)
> });
>
> You can now just do
>
> idbStore.read(...)
>
> Ajax Promises
>
> We also updated the internal Ajax library to just use promises also.
>
> This is used by both the UnifiedPush SDK and the Authz OAuth2 module.
>
> Since ES6 promises only have 1 return value we return an object with this
> signature:
>
> {
>     data: dataOrError, - the data or an error
>     statusText: statusText, - the status of the response
>     agXHR: request - the xhr request object
> };
>
> Cookbook Examples
>
> The cookbook examples have also been updated with the 2.0.0 beta1 version
> and can be found in this branch
> <https://github.com/aerogear/aerogear-js-cookbook/tree/2-beta1>
> Integration Tests
>
> Last but not least the Integration tests have been completly reworked,
> thanks to lfryc!!!
>
> The PR's for these are
> https://github.com/aerogear/aerogear-js-integration/pull/12
>
> and
>
> https://github.com/aerogear/aerogear-js/pull/150
> Release Notes - AeroGear JavaScript - Version 2.0.0Bug
>
>    - [AGJS-184 <https://issues.jboss.org/browse/AGJS-184>] - Vertx and
>    SimplePush integration tests execution issues
>
> Feature Request
>
>    - [AGJS-201 <https://issues.jboss.org/browse/AGJS-201>] -
>    XMLHttpRequest#response not implemented in Sinon.JS lib & authentication
>    unit tests fail
>    - [AGJS-251 <https://issues.jboss.org/browse/AGJS-251>] - DataManager
>    - Auto connect options should default to true
>
> Task
>
>    - [AGJS-189 <https://issues.jboss.org/browse/AGJS-189>] - Review
>    DevDependencies Versions
>    - [AGJS-211 <https://issues.jboss.org/browse/AGJS-211>] - Rework
>    Integration Tests from the ground up
>    - [AGJS-228 <https://issues.jboss.org/browse/AGJS-228>] - Deprecate
>    Pipeline
>    - [AGJS-229 <https://issues.jboss.org/browse/AGJS-229>] - Deprecate
>    Authentication Module
>    - [AGJS-232 <https://issues.jboss.org/browse/AGJS-232>] - Remove
>    AeroGear.isArray method from core
>    - [AGJS-233 <https://issues.jboss.org/browse/AGJS-233>] - Remove
>    pipeline integration tests
>    - [AGJS-234 <https://issues.jboss.org/browse/AGJS-234>] - Promisify
>    Library
>    - [AGJS-242 <https://issues.jboss.org/browse/AGJS-242>] - Update
>    cookbook examples with deprecation notices, etc...
>    - [AGJS-248 <https://issues.jboss.org/browse/AGJS-248>] - Move the
>    SimplePush and UnifiedPush examples to the real js-cookbook
>
> Sub-task
>
>    - [AGJS-42 <https://issues.jboss.org/browse/AGJS-42>] - Remove jQuery
>    dependency from DataManager; embrace Promises instead
>    - [AGJS-162 <https://issues.jboss.org/browse/AGJS-162>] - Remove
>    jQuery Dependency from Auth
>    - [AGJS-212 <https://issues.jboss.org/browse/AGJS-212>] - Update to
>    express 4
>    - [AGJS-231 <https://issues.jboss.org/browse/AGJS-231>] - Update Authz
>    cookbook example without pipeline
>    - [AGJS-235 <https://issues.jboss.org/browse/AGJS-235>] - Promisify
>    Datamanager
>    - [AGJS-236 <https://issues.jboss.org/browse/AGJS-236>] - Promisfy
>    Crypto
>    - [AGJS-237 <https://issues.jboss.org/browse/AGJS-237>] - Promisfy
>    Notifier
>    - [AGJS-238 <https://issues.jboss.org/browse/AGJS-238>] - Promisfy
>    UnifiedPush client
>    - [AGJS-239 <https://issues.jboss.org/browse/AGJS-239>] - Promisfy
>    Authorization
>    - [AGJS-240 <https://issues.jboss.org/browse/AGJS-240>] - Promisfy
>    SimplePush
>    - [AGJS-243 <https://issues.jboss.org/browse/AGJS-243>] - Add
>    deprecation Notice for Pipeline Cookbook example
>    - [AGJS-244 <https://issues.jboss.org/browse/AGJS-244>] - Add
>    deprecation notice on Auth cookbook example
>    - [AGJS-245 <https://issues.jboss.org/browse/AGJS-245>] - Promisify
>    AeroGear.ajax
>    - [AGJS-246 <https://issues.jboss.org/browse/AGJS-246>] - Update
>    unified push example to use just promises
>    - [AGJS-247 <https://issues.jboss.org/browse/AGJS-247>] - Update
>    Datamanager example to use promises not callbacks
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141011/49b1c594/attachment.html 

From bruno at abstractj.org  Sat Oct 11 10:20:09 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Sat, 11 Oct 2014 07:20:09 -0700 (PDT)
Subject: [aerogear-dev] Admin endpoints
In-Reply-To: <CAFJm-3GMQwkSrLADOGnF-kfMj8dxdzCA94xSzR9ioU-BVfYucg@mail.gmail.com>
References: <CAFJm-3GMQwkSrLADOGnF-kfMj8dxdzCA94xSzR9ioU-BVfYucg@mail.gmail.com>
Message-ID: <1413037208818.1af2b6e3@Nodemailer>

Chillax!

?

abstractj
PGP: 0x84DC9914

On Sat, Oct 11, 2014 at 4:53 AM, Daniel Bevenius
<daniel.bevenius at gmail.com> wrote:

> Hey Bruno,
> ah I see. I've been lazy and did not take a closer look and if this would
> add an extra dependency that does not sounds good.
> On 10 October 2014 18:06, Bruno Oliveira <bruno at abstractj.org> wrote:
>> Hi Dan, that would imply on having an extra Maven dependency into the
>> services, not sure if we want it.
>>
>> I will attach a PR and ask for you review.
>>
>> On 2014-10-10, Daniel Bevenius wrote:
>> > Just a thought here...is the securityContext used elsewhere in the
>> > PushApplicationEndpoint class?
>> > If not, perhaps we could have it injected into the PushAppService class
>> not
>> > have to pass anything into the findAllPushApplicationsByUser method?
>> >
>> >
>> > On 10 October 2014 16:06, Bruno Oliveira <bruno at abstractj.org> wrote:
>> >
>> > > +1 and one more question. During the hangouts we agreed on move this to
>> > > the service[1]. The downside is the fact that our service doesn't have
>> > > SecurityContext as maven dependency, which would imply on add it.
>> > >
>> > > What works best to YOU GUYS (the team :P). Leave it as is:
>> > >
>> > >
>> > >
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
>> > >
>> > > Or:
>> > >
>> > > boolean isAdmin = securityContext.isUserInRole("admin");
>> > > return
>> Response.ok(pushAppService.findAllPushApplicationsByUser(isAdmin,
>> > > extractUsername(request))).build();
>> > >
>> > > Or:
>> > >
>> > > return
>> > >
>> Response.ok(pushAppService.findAllPushApplicationsByUser(securityContext,
>> > > extractUsername(request))).build();
>> > >
>> > >
>> > > [1] -
>> > >
>> > >
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L95
>> > >
>> > > On 2014-10-10, Matthias Wessendorf wrote:
>> > > > hangout result: no need to add lot's of IFs - since only the
>> "finder" for
>> > > > PushApplications will have a different behavior (meaning for admin ->
>> > > all;
>> > > > for developer -> just my own apps)
>> > > > At this point no need of a specific admin-ish endpoint, nor no need
>> to
>> > > > create a new "admin" UI.
>> > > >
>> > > > However, once we are in a need to do more tweaks for an admin user
>> (e.g.
>> > > in
>> > > > a year or so): yes, there should not be any more IFs but a more
>> cleaner
>> > > > approcah, like extra classes as Bruno did suggest.
>> > > >
>> > > > Cheers!
>> > > >
>> > > >
>> > > > On Fri, Oct 10, 2014 at 3:40 PM, Matthias Wessendorf <
>> matzew at apache.org>
>> > > > wrote:
>> > > >
>> > > > > "you guys" :)
>> > > > >
>> > > > > I think the only different between 'admin' and developer' role is
>> > > really
>> > > > > the result of the "findAllPushApplicationsForDeveloper()"
>> > > > >
>> > > > > everything else would be the same
>> > > > >
>> > > > > On Fri, Oct 10, 2014 at 3:36 PM, Bruno Oliveira <
>> bruno at abstractj.org>
>> > > > > wrote:
>> > > > >
>> > > > >> I really want to confirm this. So this is what you guys want:
>> > > > >>
>> > > > >> -
>> > > > >>
>> > >
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L109
>> > > > >> -
>> > > > >>
>> > >
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L132
>> > > > >> -
>> > > > >>
>> > >
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L172
>> > > > >> -
>> > > > >>
>> > >
>> https://gist.github.com/abstractj/3873482db8f4535aefe0#file-pushapplicationendpoint-java-L199
>> > > > >>
>> > > > >> And with more methods we add more IFs, right?
>> > > > >>
>> > > > >> On 2014-10-10, Matthias Wessendorf wrote:
>> > > > >> > On Thu, Oct 9, 2014 at 9:58 PM, Bruno Oliveira <
>> bruno at abstractj.org
>> > > >
>> > > > >> wrote:
>> > > > >> >
>> > > > >> > > On 2014-10-09, Matthias Wessendorf wrote:
>> > > > >> > > > On Thu, Oct 9, 2014 at 6:04 PM, S?bastien Blanc <
>> > > > >> scm.blanc at gmail.com>
>> > > > >> > > wrote:
>> > > > >> > > >
>> > > > >> > > > > Another option could be :
>> > > > >> > > > > - no change or addition of any endpoint
>> > > > >> > > > > -no change on the angular side
>> > > > >> > > > >
>> > > > >> > > > > Since the result is the same : we want a list of
>> applications
>> > > (for
>> > > > >> > > admin
>> > > > >> > > > > there is just no restriction on developer that owns it)
>> > > > >> > > > > But in the service layer when retrieving the applications
>> we
>> > > > >> check the
>> > > > >> > > > > role (do we have a method hasRole(string) ? ) to see if we
>> > > add the
>> > > > >> > > criteria
>> > > > >> > > > > of developer.
>> > > > >> > > > >
>> > > > >> > > >
>> > > > >> > > > yeah, that;s what I had in my email from last night as
>> well. the
>> > > > >> service
>> > > > >> > > > returns a list of applications.
>> > > > >> > >
>> > > > >> > > I think this is very clear to everyone and the basic
>> principle of
>> > > this
>> > > > >> > > jira.
>> > > > >> > >
>> > > > >> > > > Inside we handle the different cases:
>> > > > >> > > > - admin
>> > > > >> > > >    Select all (e.g. "select pa from PushApplication pa")
>> > > > >> > > > -developer
>> > > > >> > > >    select 'my apps' (e.g. "select pa from PushApplication pa
>> > > where
>> > > > >> > > > pa.developer = :loginName")
>> > > > >> > >
>> > > > >> > > This is the recommendation from KC documentation
>> > > > >> > >
>> > > > >> > >
>> > > > >>
>> > >
>> http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/ch07.html#d4e611
>> > > > >> > > .
>> > > > >> > >
>> > > > >> >
>> > > > >> > I understand their example, but we don't really (within UPS)
>> have a
>> > > > >> > completely different UI between "admin" and "developer" roles.
>> > > > >> >
>> > > > >> >
>> > > > >> > >
>> > > > >> > > So what do you guys suggest is: If I have several methods to
>> > > validate
>> > > > >> > > multiple roles, just add if/else all along the UPS code? And
>> if I
>> > > > >> have a
>> > > > >> > > new
>> > > > >> > > role, include more ifs?
>> > > > >> > >
>> > > > >> > > I think it can be done inject the SecurityContext, have to
>> check
>> > > with
>> > > > >> > > Stian and Bill. But it doesn't seem right.
>> > > > >> > >
>> > > > >> >
>> > > > >> > might not be the most elegant, but looks like it avoids adding
>> too
>> > > much
>> > > > >> new
>> > > > >> > code. Especially since the UI for 'admin' and 'developer' is
>> pretty
>> > > much
>> > > > >> > the same.
>> > > > >> >
>> > > > >> >
>> > > > >> > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > -Matthias
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > >
>> > > > >> > > > > Envoy? de mon iPhone
>> > > > >> > > > >
>> > > > >> > > > > > Le 9 oct. 2014 ? 17:45, Bruno Oliveira <
>> bruno at abstractj.org>
>> > > a
>> > > > >> > > ?crit :
>> > > > >> > > > > >
>> > > > >> > > > > > Good morning, moving forward with
>> > > > >> > > > > > https://issues.jboss.org/browse/AGPUSH-1036. What is
>> the
>> > > most
>> > > > >> > > > > > recommended approach for admin-ui.
>> > > > >> > > > > >
>> > > > >> > > > > > Have separated endpoints for the admin like:
>> > > > >> > > > > >
>> > > > >> > > > > > 1.
>> > > > >> > > > > >
>> > > > >> > > > > > @RolesAllowed("admin")
>> > > > >> > > > > > @Path("/admin/applications")
>> > > > >> > > > > > public class AdminApplicationEndpoint extends
>> > > > >> AbstractBaseEndpoint {
>> > > > >> > > > > >
>> > > > >> > > > > >    @GET
>> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > >> > > > > >    public Response listAllPushApplications(){
>> > > > >> > > > > >        //queries
>> > > > >> > > > > >    }
>> > > > >> > > > > > }
>> > > > >> > > > > >
>> > > > >> > > > > > Or introduce a new method inside the current
>> > > > >> PushApplicationEndpoint:
>> > > > >> > > > > >
>> > > > >> > > > > > 2.
>> > > > >> > > > > >
>> > > > >> > > > > >    @GET
>> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > >> > > > > >    @RolesAllowed("admin")
>> > > > >> > > > > >    public Response listAllPushApplications(){
>> > > > >> > > > > >      //queries
>> > > > >> > > > > >    }
>> > > > >> > > > > >    // READ
>> > > > >> > > > > >    @GET
>> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > >> > > > > >    public Response
>> > > listAllPushApplicationsByUsername(@Context
>> > > > >> > > > > HttpServletRequest request) {
>> > > > >> > > > > >        return
>> > > > >> > > > >
>> > > > >> > >
>> > > > >>
>> > >
>> Response.ok(pushAppService.findAllPushApplicationsForDeveloper(extractUsername(request))).build();
>> > > > >> > > > > >    }
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > > If the option 2 is the correct. How the Angular.js
>> service
>> > > > >> would look
>> > > > >> > > > > > like? Once the username is not informed as argument on
>> > > > >> > > > > > pushApplicationService.js, because for obvious reasons
>> it
>> > > can be
>> > > > >> > > > > > retrieved with HttpServletRequest.
>> > > > >> > > > > >
>> > > > >> > > > > > One of my poor ideas due to my "amazing" Angular skills
>> > > would
>> > > > >> be to
>> > > > >> > > do
>> > > > >> > > > > > something like:
>> > > > >> > > > > >
>> > > > >> > > > > >    @GET
>> > > > >> > > > > >    @Produces(MediaType.APPLICATION_JSON)
>> > > > >> > > > > >    @RolesAllowed("admin")
>> > > > >> > > > > >    @Path("/all")
>> > > > >> > > > > >    public Response listAllPushApplications(){
>> > > > >> > > > > >      //queries
>> > > > >> > > > > >    }
>> > > > >> > > > > >
>> > > > >> > > > > > And:
>> > > > >> > > > > >
>> > > > >> > > > > > backendMod.factory('pushApplication', function
>> ($resource) {
>> > > > >> > > > > >  return $resource('rest/applications/all/:verb', {
>> > > > >> > > > > > .....
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > > Help?
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > > --
>> > > > >> > > > > >
>> > > > >> > > > > > abstractj
>> > > > >> > > > > > PGP: 0x84DC9914
>> > > > >> > > > > > _______________________________________________
>> > > > >> > > > > > aerogear-dev mailing list
>> > > > >> > > > > > aerogear-dev at lists.jboss.org
>> > > > >> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >> > > > >
>> > > > >> > > > > _______________________________________________
>> > > > >> > > > > aerogear-dev mailing list
>> > > > >> > > > > aerogear-dev at lists.jboss.org
>> > > > >> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >> > > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > --
>> > > > >> > > > Matthias Wessendorf
>> > > > >> > > >
>> > > > >> > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > >> > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > >> > > > twitter: http://twitter.com/mwessendorf
>> > > > >> > >
>> > > > >> > > > _______________________________________________
>> > > > >> > > > aerogear-dev mailing list
>> > > > >> > > > aerogear-dev at lists.jboss.org
>> > > > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >> > >
>> > > > >> > >
>> > > > >> > > --
>> > > > >> > >
>> > > > >> > > abstractj
>> > > > >> > > PGP: 0x84DC9914
>> > > > >> > > _______________________________________________
>> > > > >> > > aerogear-dev mailing list
>> > > > >> > > aerogear-dev at lists.jboss.org
>> > > > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >> > >
>> > > > >> >
>> > > > >> >
>> > > > >> >
>> > > > >> > --
>> > > > >> > Matthias Wessendorf
>> > > > >> >
>> > > > >> > blog: http://matthiaswessendorf.wordpress.com/
>> > > > >> > sessions: http://www.slideshare.net/mwessendorf
>> > > > >> > twitter: http://twitter.com/mwessendorf
>> > > > >>
>> > > > >> > _______________________________________________
>> > > > >> > aerogear-dev mailing list
>> > > > >> > aerogear-dev at lists.jboss.org
>> > > > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >>
>> > > > >>
>> > > > >> --
>> > > > >>
>> > > > >> abstractj
>> > > > >> PGP: 0x84DC9914
>> > > > >> _______________________________________________
>> > > > >> aerogear-dev mailing list
>> > > > >> aerogear-dev at lists.jboss.org
>> > > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >>
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Matthias Wessendorf
>> > > > >
>> > > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > > twitter: http://twitter.com/mwessendorf
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Matthias Wessendorf
>> > > >
>> > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > twitter: http://twitter.com/mwessendorf
>> > >
>> > > > _______________________________________________
>> > > > aerogear-dev mailing list
>> > > > aerogear-dev at lists.jboss.org
>> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> > >
>> > > --
>> > >
>> > > abstractj
>> > > PGP: 0x84DC9914
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141011/689a5f0b/attachment-0001.html 

From qmx at qmx.me  Mon Oct 13 00:31:03 2014
From: qmx at qmx.me (Douglas Campos)
Date: Mon, 13 Oct 2014 01:31:03 -0300
Subject: [aerogear-dev] database migration
In-Reply-To: <91B9B026-7646-4C4B-928D-93FC2E4FED25@redhat.com>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
	<CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
	<1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>
	<DBBFE1C0-DDBC-43E1-BC86-1B60F4CFA174@redhat.com>
	<1862184835.63049258.1412687518710.JavaMail.zimbra@redhat.com>
	<91B9B026-7646-4C4B-928D-93FC2E4FED25@redhat.com>
Message-ID: <20141013043103.GC56451@darkstar.local>

On Tue, Oct 07, 2014 at 03:20:19PM +0200, Erik Jan de Wit wrote:
> On 7 Oct,2014, at 15:11 , Stian Thorgersen <stian at redhat.com> wrote:
> 
> >> FlywayDB uses SQL directly, so we have to deal with differences between
> >> databases ourselves. IMO that renders it useless!
> >> 
> >> liquibase it is, and let?s not use xml for the change sets ;)
> > 
> > Why not XML?
> > 
> 
> We hate XML
While I do hate XML too, in this case their xsd's are kickass on
validating stuff for us. (happy liquibase user here too)

I'd say "embrace the darkness^H^H^HXML unless we have a huge reason to
avoid it.

-- 
qmx

From daniel.bevenius at gmail.com  Mon Oct 13 02:56:33 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 13 Oct 2014 08:56:33 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3FG6T5cCfPLEJ2N9Je6z_PnBV3Reduw_qaNti_Usp4H3g@mail.gmail.com>

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

From ek at fastlane-it.com  Mon Oct 13 09:18:45 2014
From: ek at fastlane-it.com (ekolesnikov)
Date: Mon, 13 Oct 2014 06:18:45 -0700 (PDT)
Subject: [aerogear-dev] Using existing Keycloak installation with Aerogear
Message-ID: <1413206325014-9440.post@n5.nabble.com>

Hi,

Apologies for writing straight into DEV forums - I was unable to locate
"aerogear-users" mailing list anywhere. Please feel free to point me to the
right direction if this mailing list is inappropriate for questions like
this.

Is it possible to use/integrate Aerogear with existing Keycloak
installation? We are already using Keycloak for all things auth in our
application and have found ourselves in the situation where we potentially
have to manage separate infrastructure - which makes the whole point of
using Keycloak a bit irrelevant.

As an alternative, we could consider using Keycloak supplied with with
Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
option to create additional realms.

I would really appreciate it if you could share your thought on this.

Thanks
Egor



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Mon Oct 13 09:29:26 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 13 Oct 2014 15:29:26 +0200
Subject: [aerogear-dev] Using existing Keycloak installation with
	Aerogear
In-Reply-To: <1413206325014-9440.post@n5.nabble.com>
References: <1413206325014-9440.post@n5.nabble.com>
Message-ID: <CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>

Hi,

for the UnifiedPush Server the initial integration case was to function
only for the need of the AeroGear UnifiedPush server.

So, looks like, you'd appreciate a bit more flexibility, to basically use
the auth-server for other apps as well ?



On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com> wrote:

> Hi,
>
> Apologies for writing straight into DEV forums - I was unable to locate
> "aerogear-users" mailing list anywhere. Please feel free to point me to the
> right direction if this mailing list is inappropriate for questions like
> this.
>
> Is it possible to use/integrate Aerogear with existing Keycloak
> installation? We are already using Keycloak for all things auth in our
> application and have found ourselves in the situation where we potentially
> have to manage separate infrastructure - which makes the whole point of
> using Keycloak a bit irrelevant.
>
> As an alternative, we could consider using Keycloak supplied with with
> Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
> option to create additional realms.
>
> I would really appreciate it if you could share your thought on this.
>
> Thanks
> Egor
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.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/20141013/41e30538/attachment.html 

From egor.kolesnikov at fastlane-it.com  Mon Oct 13 09:40:37 2014
From: egor.kolesnikov at fastlane-it.com (Egor Kolesnikov)
Date: Tue, 14 Oct 2014 00:40:37 +1100
Subject: [aerogear-dev] Using existing Keycloak installation
	with	Aerogear
In-Reply-To: <CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
References: <1413206325014-9440.post@n5.nabble.com>
	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
Message-ID: <006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>

Hi Matthias

 

That?s correct ? we are already using Keycloak to secure our RESTful APIs for mobile and web client access. Not that having separate installation for exclusive Aerogear is a dealbreaker, but it would re-introduce the problem Keycloak was supposed to solve in the first place :)

 

I can see that UpsSecurityApplication class kills off Keycloak admin user in master realm ? would it break anything if I disabled this feature and started using Aerogear-supplied Keycloak for other purposes on separate realms?

 

Our use case is mobile app (iOS+android), backend and AngularJS-based web frontend and so far Keycloak fits our purpose like a glove. Now that we?re adding Push notification support, Aerogear appears to be quite logical choice.

 

Thanks

Egor

 

From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf
Sent: Tuesday, 14 October 2014 12:29 AM
To: AeroGear Developer Mailing List
Subject: Re: [aerogear-dev] Using existing Keycloak installation with Aerogear

 

Hi,

 

for the UnifiedPush Server the initial integration case was to function only for the need of the AeroGear UnifiedPush server.

 

So, looks like, you'd appreciate a bit more flexibility, to basically use the auth-server for other apps as well ?

 

 

 

On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com <mailto:ek at fastlane-it.com> > wrote:

Hi,

Apologies for writing straight into DEV forums - I was unable to locate
"aerogear-users" mailing list anywhere. Please feel free to point me to the
right direction if this mailing list is inappropriate for questions like
this.

Is it possible to use/integrate Aerogear with existing Keycloak
installation? We are already using Keycloak for all things auth in our
application and have found ourselves in the situation where we potentially
have to manage separate infrastructure - which makes the whole point of
using Keycloak a bit irrelevant.

As an alternative, we could consider using Keycloak supplied with with
Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
option to create additional realms.

I would really appreciate it if you could share your thought on this.

Thanks
Egor



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.html
Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
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 



---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141014/39bcf0ed/attachment.html 

From matzew at apache.org  Mon Oct 13 09:49:10 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 13 Oct 2014 15:49:10 +0200
Subject: [aerogear-dev] Using existing Keycloak installation with
	Aerogear
In-Reply-To: <006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
References: <1413206325014-9440.post@n5.nabble.com>
	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
	<006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
Message-ID: <CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>

On Mon, Oct 13, 2014 at 3:40 PM, Egor Kolesnikov <
egor.kolesnikov at fastlane-it.com> wrote:

> Hi Matthias
>
>
>
> That?s correct ? we are already using Keycloak to secure our RESTful APIs
> for mobile and web client access. Not that having separate installation for
> exclusive Aerogear is a dealbreaker, but it would re-introduce the problem
> Keycloak was supposed to solve in the first place J
>

fully understand! But we, initially, felt like limiting a bit. that said,
we are flexible and there might be a chance to have this changed


>
>
> I can see that UpsSecurityApplication class kills off Keycloak admin user
> in master realm ? would it break anything if I disabled this feature and
> started using Aerogear-supplied Keycloak for other purposes on separate
> realms?
>

I don't think so (not tested). I recall we did this mainly to avoid adding
new realms


>
>
> Our use case is mobile app (iOS+android), backend and AngularJS-based web
> frontend and so far Keycloak fits our purpose like a glove. Now that we?re
> adding Push notification support, Aerogear appears to be quite logical
> choice.
>


sounds great!


>
>
> Thanks
>
> Egor
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* Tuesday, 14 October 2014 12:29 AM
> *To:* AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> Aerogear
>
>
>
> Hi,
>
>
>
> for the UnifiedPush Server the initial integration case was to function
> only for the need of the AeroGear UnifiedPush server.
>
>
>
> So, looks like, you'd appreciate a bit more flexibility, to basically use
> the auth-server for other apps as well ?
>
>
>
>
>
>
>
> On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com> wrote:
>
> Hi,
>
> Apologies for writing straight into DEV forums - I was unable to locate
> "aerogear-users" mailing list anywhere. Please feel free to point me to the
> right direction if this mailing list is inappropriate for questions like
> this.
>
> Is it possible to use/integrate Aerogear with existing Keycloak
> installation? We are already using Keycloak for all things auth in our
> application and have found ourselves in the situation where we potentially
> have to manage separate infrastructure - which makes the whole point of
> using Keycloak a bit irrelevant.
>
> As an alternative, we could consider using Keycloak supplied with with
> Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
> option to create additional realms.
>
> I would really appreciate it if you could share your thought on this.
>
> Thanks
> Egor
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.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
>
>
> ------------------------------
>    <http://www.avast.com/>
>
> This email is free from viruses and malware because avast! Antivirus
> <http://www.avast.com/> protection is active.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141013/7f21a482/attachment-0001.html 

From egor.kolesnikov at fastlane-it.com  Mon Oct 13 10:08:34 2014
From: egor.kolesnikov at fastlane-it.com (Egor Kolesnikov)
Date: Tue, 14 Oct 2014 01:08:34 +1100
Subject: [aerogear-dev] Using existing Keycloak installation
	with	Aerogear
In-Reply-To: <CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>
References: <1413206325014-9440.post@n5.nabble.com>	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>	<006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
	<CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>
Message-ID: <009601cfe6ef$2f9219f0$8eb64dd0$@fastlane-it.com>

Hi Matthias 

 

I do understand that Aerogear is quite young product and may not have all features yet ? just need to understand your vision of the project to align our further development appropriately.

 

Having said that, I can see two possible integration options with projects like ours:

1.       Aerogear+Keycloak combo used for ?all things auth? (this will require unlocking master/admin user);

2.       Configuring Aerogear to use external Keycloak installation.

Option 1 appears to be the easiest way around, whether Option 2 looks like the most appropriate solution in the SSO world ? as in, there?s still a ?single? sign-on point which is used by all third-party systems. If I understand correctly, this could possibly be as easy as setting up auth-server-url property in Aerogear?s keycloak.json so it delegates to external Keycloak instance instead of using its ?own? one.

 

I?m happy to spend some time investigating and experimenting with both options.

 

Cheers

Egor 

 

 

 

From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf
Sent: Tuesday, 14 October 2014 12:49 AM
To: AeroGear Developer Mailing List
Subject: Re: [aerogear-dev] Using existing Keycloak installation with Aerogear

 

 

 

On Mon, Oct 13, 2014 at 3:40 PM, Egor Kolesnikov <egor.kolesnikov at fastlane-it.com <mailto:egor.kolesnikov at fastlane-it.com> > wrote:

Hi Matthias

 

That?s correct ? we are already using Keycloak to secure our RESTful APIs for mobile and web client access. Not that having separate installation for exclusive Aerogear is a dealbreaker, but it would re-introduce the problem Keycloak was supposed to solve in the first place :)

 

fully understand! But we, initially, felt like limiting a bit. that said, we are flexible and there might be a chance to have this changed 

 

 

I can see that UpsSecurityApplication class kills off Keycloak admin user in master realm ? would it break anything if I disabled this feature and started using Aerogear-supplied Keycloak for other purposes on separate realms?

 

I don't think so (not tested). I recall we did this mainly to avoid adding new realms

 

 

Our use case is mobile app (iOS+android), backend and AngularJS-based web frontend and so far Keycloak fits our purpose like a glove. Now that we?re adding Push notification support, Aerogear appears to be quite logical choice.

 

 

sounds great!

 

 

Thanks

Egor

 

From: aerogear-dev-bounces at lists.jboss.org <mailto:aerogear-dev-bounces at lists.jboss.org>  [mailto:aerogear-dev-bounces at lists.jboss.org <mailto:aerogear-dev-bounces at lists.jboss.org> ] On Behalf Of Matthias Wessendorf
Sent: Tuesday, 14 October 2014 12:29 AM
To: AeroGear Developer Mailing List
Subject: Re: [aerogear-dev] Using existing Keycloak installation with Aerogear

 

Hi,

 

for the UnifiedPush Server the initial integration case was to function only for the need of the AeroGear UnifiedPush server.

 

So, looks like, you'd appreciate a bit more flexibility, to basically use the auth-server for other apps as well ?

 

 

 

On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com <mailto:ek at fastlane-it.com> > wrote:

Hi,

Apologies for writing straight into DEV forums - I was unable to locate
"aerogear-users" mailing list anywhere. Please feel free to point me to the
right direction if this mailing list is inappropriate for questions like
this.

Is it possible to use/integrate Aerogear with existing Keycloak
installation? We are already using Keycloak for all things auth in our
application and have found ourselves in the situation where we potentially
have to manage separate infrastructure - which makes the whole point of
using Keycloak a bit irrelevant.

As an alternative, we could consider using Keycloak supplied with with
Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
option to create additional realms.

I would really appreciate it if you could share your thought on this.

Thanks
Egor



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.html
Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
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 

 

  _____  


 <http://www.avast.com/> 

This email is free from viruses and malware because avast! Antivirus <http://www.avast.com/>  protection is active. 

 


_______________________________________________
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 



---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141014/6fc193f4/attachment.html 

From cvasilak at gmail.com  Mon Oct 13 10:14:00 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 13 Oct 2014 17:14:00 +0300
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3FG6T5cCfPLEJ2N9Je6z_PnBV3Reduw_qaNti_Usp4H3g@mail.gmail.com>
References: <CAFJm-3FG6T5cCfPLEJ2N9Je6z_PnBV3Reduw_qaNti_Usp4H3g@mail.gmail.com>
Message-ID: <C68E47D2-D8E5-476F-87C4-B4EA28439096@gmail.com>

fyi,

meeting minutes:

<jbott>	 Meeting ended Mon Oct 13 14:12:33 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-10-13-14.03.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-13-14.03.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-13-14.03.log.html



On Oct 13, 2014, at 9:56 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

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

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

From matzew at apache.org  Mon Oct 13 10:16:47 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 13 Oct 2014 16:16:47 +0200
Subject: [aerogear-dev] Using existing Keycloak installation with
	Aerogear
In-Reply-To: <009601cfe6ef$2f9219f0$8eb64dd0$@fastlane-it.com>
References: <1413206325014-9440.post@n5.nabble.com>
	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
	<006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
	<CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>
	<009601cfe6ef$2f9219f0$8eb64dd0$@fastlane-it.com>
Message-ID: <CAAg5f2RLtRzQk+qhAJERUJdztpZiuY=mCN6WPAGzrMeKcpN2hg@mail.gmail.com>

On Mon, Oct 13, 2014 at 4:08 PM, Egor Kolesnikov <
egor.kolesnikov at fastlane-it.com> wrote:

> Hi Matthias
>
>
>
> I do understand that Aerogear is quite young product and may not have all
> features yet
>

AeroGear is more, than just its UPS (UnifiedPush Server) - which we are
talking about here :)


> ? just need to understand your vision of the project to align our further
> development appropriately.
>
>
>
> Having said that, I can see two possible integration options with projects
> like ours:
>
> 1.       Aerogear+Keycloak combo used for ?all things auth? (this will
> require unlocking master/admin user);
>
moving forward, I'd like us to go there. Again it was just done to limit
the initial scope of the UPS



> 2.       Configuring Aerogear to use external Keycloak installation.
>
we have had discussions about that too. that it should be possible to have
our UnifiedPush Server on one machine, and a standalone keycloak server,
that is used for more. not just UPS



> Option 1 appears to be the easiest way around, whether Option 2 looks like
> the most appropriate solution in the SSO world ? as in, there?s still a
> ?single? sign-on point which is used by all third-party systems. If I
> understand correctly, this could possibly be as easy as setting up
> auth-server-url property in Aerogear?s keycloak.json so it delegates to
> external Keycloak instance instead of using its ?own? one.
>
>
>
> I?m happy to spend some time investigating and experimenting with both
> options.
>
>
>
> Cheers
>
> Egor
>
>
>
>
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* Tuesday, 14 October 2014 12:49 AM
>
> *To:* AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> Aerogear
>
>
>
>
>
>
>
> On Mon, Oct 13, 2014 at 3:40 PM, Egor Kolesnikov <
> egor.kolesnikov at fastlane-it.com> wrote:
>
> Hi Matthias
>
>
>
> That?s correct ? we are already using Keycloak to secure our RESTful APIs
> for mobile and web client access. Not that having separate installation for
> exclusive Aerogear is a dealbreaker, but it would re-introduce the problem
> Keycloak was supposed to solve in the first place J
>
>
>
> fully understand! But we, initially, felt like limiting a bit. that said,
> we are flexible and there might be a chance to have this changed
>
>
>
>
>
> I can see that UpsSecurityApplication class kills off Keycloak admin user
> in master realm ? would it break anything if I disabled this feature and
> started using Aerogear-supplied Keycloak for other purposes on separate
> realms?
>
>
>
> I don't think so (not tested). I recall we did this mainly to avoid adding
> new realms
>
>
>
>
>
> Our use case is mobile app (iOS+android), backend and AngularJS-based web
> frontend and so far Keycloak fits our purpose like a glove. Now that we?re
> adding Push notification support, Aerogear appears to be quite logical
> choice.
>
>
>
>
>
> sounds great!
>
>
>
>
>
> Thanks
>
> Egor
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* Tuesday, 14 October 2014 12:29 AM
> *To:* AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> Aerogear
>
>
>
> Hi,
>
>
>
> for the UnifiedPush Server the initial integration case was to function
> only for the need of the AeroGear UnifiedPush server.
>
>
>
> So, looks like, you'd appreciate a bit more flexibility, to basically use
> the auth-server for other apps as well ?
>
>
>
>
>
>
>
> On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com> wrote:
>
> Hi,
>
> Apologies for writing straight into DEV forums - I was unable to locate
> "aerogear-users" mailing list anywhere. Please feel free to point me to the
> right direction if this mailing list is inappropriate for questions like
> this.
>
> Is it possible to use/integrate Aerogear with existing Keycloak
> installation? We are already using Keycloak for all things auth in our
> application and have found ourselves in the situation where we potentially
> have to manage separate infrastructure - which makes the whole point of
> using Keycloak a bit irrelevant.
>
> As an alternative, we could consider using Keycloak supplied with with
> Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
> option to create additional realms.
>
> I would really appreciate it if you could share your thought on this.
>
> Thanks
> Egor
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.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
>
>
> ------------------------------
>
> <http://www.avast.com/>
>
> This email is free from viruses and malware because avast! Antivirus
> <http://www.avast.com/> protection is active.
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ------------------------------
>    <http://www.avast.com/>
>
> This email is free from viruses and malware because avast! Antivirus
> <http://www.avast.com/> protection is active.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141013/7a4d7fcd/attachment.html 

From bruno at abstractj.org  Mon Oct 13 10:38:08 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 13 Oct 2014 11:38:08 -0300
Subject: [aerogear-dev] Using existing Keycloak installation with
	Aerogear
In-Reply-To: <CAAg5f2RLtRzQk+qhAJERUJdztpZiuY=mCN6WPAGzrMeKcpN2hg@mail.gmail.com>
References: <1413206325014-9440.post@n5.nabble.com>
	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
	<006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
	<CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>
	<009601cfe6ef$2f9219f0$8eb64dd0$@fastlane-it.com>
	<CAAg5f2RLtRzQk+qhAJERUJdztpZiuY=mCN6WPAGzrMeKcpN2hg@mail.gmail.com>
Message-ID: <20141013143808.GA35341@abstractj.org>

On 2014-10-13, Matthias Wessendorf wrote:
> On Mon, Oct 13, 2014 at 4:08 PM, Egor Kolesnikov <
> egor.kolesnikov at fastlane-it.com> wrote:
>
> > Hi Matthias
> >
> >
> >
> > I do understand that Aerogear is quite young product and may not have all
> > features yet
> >
>
> AeroGear is more, than just its UPS (UnifiedPush Server) - which we are
> talking about here :)
>
>
> > ? just need to understand your vision of the project to align our further
> > development appropriately.
> >
> >
> >
> > Having said that, I can see two possible integration options with projects
> > like ours:
> >
> > 1.       Aerogear+Keycloak combo used for ?all things auth? (this will
> > require unlocking master/admin user);
> >
> moving forward, I'd like us to go there. Again it was just done to limit
> the initial scope of the UPS
>
>
>
> > 2.       Configuring Aerogear to use external Keycloak installation.
> >
> we have had discussions about that too. that it should be possible to have
> our UnifiedPush Server on one machine, and a standalone keycloak server,
> that is used for more. not just UPS

I think it makes perfect sense. There are two solutions quick or slow.

1. Quick: enable our developers to make use of not only AeroGear, but
create new realms as well. Also, let them, do whatever they want with
the admin.

2. Slow (I'm +1 on it). Dettach UPS from Keycloak and use as an external
installation. (off course, provide an easy way to install). If we think
carefuly, people might want to have 1 server with Keycloak and 4 with
UPS or the opposite.


>
>
>
> > Option 1 appears to be the easiest way around, whether Option 2 looks like
> > the most appropriate solution in the SSO world ? as in, there?s still a
> > ?single? sign-on point which is used by all third-party systems. If I
> > understand correctly, this could possibly be as easy as setting up
> > auth-server-url property in Aerogear?s keycloak.json so it delegates to
> > external Keycloak instance instead of using its ?own? one.
> >
> >
> >
> > I?m happy to spend some time investigating and experimenting with both
> > options.
> >
> >
> >
> > Cheers
> >
> > Egor
> >
> >
> >
> >
> >
> >
> >
> > *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> > *Sent:* Tuesday, 14 October 2014 12:49 AM
> >
> > *To:* AeroGear Developer Mailing List
> > *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> > Aerogear
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Oct 13, 2014 at 3:40 PM, Egor Kolesnikov <
> > egor.kolesnikov at fastlane-it.com> wrote:
> >
> > Hi Matthias
> >
> >
> >
> > That?s correct ? we are already using Keycloak to secure our RESTful APIs
> > for mobile and web client access. Not that having separate installation for
> > exclusive Aerogear is a dealbreaker, but it would re-introduce the problem
> > Keycloak was supposed to solve in the first place J
> >
> >
> >
> > fully understand! But we, initially, felt like limiting a bit. that said,
> > we are flexible and there might be a chance to have this changed
> >
> >
> >
> >
> >
> > I can see that UpsSecurityApplication class kills off Keycloak admin user
> > in master realm ? would it break anything if I disabled this feature and
> > started using Aerogear-supplied Keycloak for other purposes on separate
> > realms?
> >
> >
> >
> > I don't think so (not tested). I recall we did this mainly to avoid adding
> > new realms
> >
> >
> >
> >
> >
> > Our use case is mobile app (iOS+android), backend and AngularJS-based web
> > frontend and so far Keycloak fits our purpose like a glove. Now that we?re
> > adding Push notification support, Aerogear appears to be quite logical
> > choice.
> >
> >
> >
> >
> >
> > sounds great!
> >
> >
> >
> >
> >
> > Thanks
> >
> > Egor
> >
> >
> >
> > *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> > *Sent:* Tuesday, 14 October 2014 12:29 AM
> > *To:* AeroGear Developer Mailing List
> > *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> > Aerogear
> >
> >
> >
> > Hi,
> >
> >
> >
> > for the UnifiedPush Server the initial integration case was to function
> > only for the need of the AeroGear UnifiedPush server.
> >
> >
> >
> > So, looks like, you'd appreciate a bit more flexibility, to basically use
> > the auth-server for other apps as well ?
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com> wrote:
> >
> > Hi,
> >
> > Apologies for writing straight into DEV forums - I was unable to locate
> > "aerogear-users" mailing list anywhere. Please feel free to point me to the
> > right direction if this mailing list is inappropriate for questions like
> > this.
> >
> > Is it possible to use/integrate Aerogear with existing Keycloak
> > installation? We are already using Keycloak for all things auth in our
> > application and have found ourselves in the situation where we potentially
> > have to manage separate infrastructure - which makes the whole point of
> > using Keycloak a bit irrelevant.
> >
> > As an alternative, we could consider using Keycloak supplied with with
> > Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
> > option to create additional realms.
> >
> > I would really appreciate it if you could share your thought on this.
> >
> > Thanks
> > Egor
> >
> >
> >
> > --
> > View this message in context:
> > http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.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
> >
> >
> > ------------------------------
> >
> > <http://www.avast.com/>
> >
> > This email is free from viruses and malware because avast! Antivirus
> > <http://www.avast.com/> protection is active.
> >
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> >
> > ------------------------------
> >    <http://www.avast.com/>
> >
> > This email is free from viruses and malware because avast! Antivirus
> > <http://www.avast.com/> protection is active.
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From stian at redhat.com  Mon Oct 13 13:30:31 2014
From: stian at redhat.com (Stian Thorgersen)
Date: Mon, 13 Oct 2014 13:30:31 -0400 (EDT)
Subject: [aerogear-dev] Using existing Keycloak installation
	with	Aerogear
In-Reply-To: <20141013143808.GA35341@abstractj.org>
References: <1413206325014-9440.post@n5.nabble.com>
	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
	<006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
	<CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>
	<009601cfe6ef$2f9219f0$8eb64dd0$@fastlane-it.com>
	<CAAg5f2RLtRzQk+qhAJERUJdztpZiuY=mCN6WPAGzrMeKcpN2hg@mail.gmail.com>
	<20141013143808.GA35341@abstractj.org>
Message-ID: <351459117.67219689.1413221431843.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Bruno Oliveira" <bruno at abstractj.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Monday, 13 October, 2014 4:38:08 PM
> Subject: Re: [aerogear-dev] Using existing Keycloak installation with	Aerogear
> 
> On 2014-10-13, Matthias Wessendorf wrote:
> > On Mon, Oct 13, 2014 at 4:08 PM, Egor Kolesnikov <
> > egor.kolesnikov at fastlane-it.com> wrote:
> >
> > > Hi Matthias
> > >
> > >
> > >
> > > I do understand that Aerogear is quite young product and may not have all
> > > features yet
> > >
> >
> > AeroGear is more, than just its UPS (UnifiedPush Server) - which we are
> > talking about here :)
> >
> >
> > > ? just need to understand your vision of the project to align our further
> > > development appropriately.
> > >
> > >
> > >
> > > Having said that, I can see two possible integration options with
> > > projects
> > > like ours:
> > >
> > > 1.       Aerogear+Keycloak combo used for ?all things auth? (this will
> > > require unlocking master/admin user);
> > >
> > moving forward, I'd like us to go there. Again it was just done to limit
> > the initial scope of the UPS
> >
> >
> >
> > > 2.       Configuring Aerogear to use external Keycloak installation.
> > >
> > we have had discussions about that too. that it should be possible to have
> > our UnifiedPush Server on one machine, and a standalone keycloak server,
> > that is used for more. not just UPS
> 
> I think it makes perfect sense. There are two solutions quick or slow.
> 
> 1. Quick: enable our developers to make use of not only AeroGear, but
> create new realms as well. Also, let them, do whatever they want with
> the admin.
> 
> 2. Slow (I'm +1 on it). Dettach UPS from Keycloak and use as an external
> installation. (off course, provide an easy way to install). If we think
> carefuly, people might want to have 1 server with Keycloak and 4 with
> UPS or the opposite.

+1000 To option 2. The other option doesn't really make that much sense to me.

> 
> 
> >
> >
> >
> > > Option 1 appears to be the easiest way around, whether Option 2 looks
> > > like
> > > the most appropriate solution in the SSO world ? as in, there?s still a
> > > ?single? sign-on point which is used by all third-party systems. If I
> > > understand correctly, this could possibly be as easy as setting up
> > > auth-server-url property in Aerogear?s keycloak.json so it delegates to
> > > external Keycloak instance instead of using its ?own? one.
> > >
> > >
> > >
> > > I?m happy to spend some time investigating and experimenting with both
> > > options.
> > >
> > >
> > >
> > > Cheers
> > >
> > > Egor
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> > > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> > > *Sent:* Tuesday, 14 October 2014 12:49 AM
> > >
> > > *To:* AeroGear Developer Mailing List
> > > *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> > > Aerogear
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Oct 13, 2014 at 3:40 PM, Egor Kolesnikov <
> > > egor.kolesnikov at fastlane-it.com> wrote:
> > >
> > > Hi Matthias
> > >
> > >
> > >
> > > That?s correct ? we are already using Keycloak to secure our RESTful APIs
> > > for mobile and web client access. Not that having separate installation
> > > for
> > > exclusive Aerogear is a dealbreaker, but it would re-introduce the
> > > problem
> > > Keycloak was supposed to solve in the first place J
> > >
> > >
> > >
> > > fully understand! But we, initially, felt like limiting a bit. that said,
> > > we are flexible and there might be a chance to have this changed
> > >
> > >
> > >
> > >
> > >
> > > I can see that UpsSecurityApplication class kills off Keycloak admin user
> > > in master realm ? would it break anything if I disabled this feature and
> > > started using Aerogear-supplied Keycloak for other purposes on separate
> > > realms?
> > >
> > >
> > >
> > > I don't think so (not tested). I recall we did this mainly to avoid
> > > adding
> > > new realms
> > >
> > >
> > >
> > >
> > >
> > > Our use case is mobile app (iOS+android), backend and AngularJS-based web
> > > frontend and so far Keycloak fits our purpose like a glove. Now that
> > > we?re
> > > adding Push notification support, Aerogear appears to be quite logical
> > > choice.
> > >
> > >
> > >
> > >
> > >
> > > sounds great!
> > >
> > >
> > >
> > >
> > >
> > > Thanks
> > >
> > > Egor
> > >
> > >
> > >
> > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> > > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> > > *Sent:* Tuesday, 14 October 2014 12:29 AM
> > > *To:* AeroGear Developer Mailing List
> > > *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> > > Aerogear
> > >
> > >
> > >
> > > Hi,
> > >
> > >
> > >
> > > for the UnifiedPush Server the initial integration case was to function
> > > only for the need of the AeroGear UnifiedPush server.
> > >
> > >
> > >
> > > So, looks like, you'd appreciate a bit more flexibility, to basically use
> > > the auth-server for other apps as well ?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com> wrote:
> > >
> > > Hi,
> > >
> > > Apologies for writing straight into DEV forums - I was unable to locate
> > > "aerogear-users" mailing list anywhere. Please feel free to point me to
> > > the
> > > right direction if this mailing list is inappropriate for questions like
> > > this.
> > >
> > > Is it possible to use/integrate Aerogear with existing Keycloak
> > > installation? We are already using Keycloak for all things auth in our
> > > application and have found ourselves in the situation where we
> > > potentially
> > > have to manage separate infrastructure - which makes the whole point of
> > > using Keycloak a bit irrelevant.
> > >
> > > As an alternative, we could consider using Keycloak supplied with with
> > > Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
> > > option to create additional realms.
> > >
> > > I would really appreciate it if you could share your thought on this.
> > >
> > > Thanks
> > > Egor
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > > http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.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
> > >
> > >
> > > ------------------------------
> > >
> > > <http://www.avast.com/>
> > >
> > > This email is free from viruses and malware because avast! Antivirus
> > > <http://www.avast.com/> protection is active.
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > >
> > >
> > > ------------------------------
> > >    <http://www.avast.com/>
> > >
> > > This email is free from viruses and malware because avast! Antivirus
> > > <http://www.avast.com/> protection is active.
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> 
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From bruno at abstractj.org  Mon Oct 13 16:32:14 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 13 Oct 2014 17:32:14 -0300
Subject: [aerogear-dev] Using existing Keycloak installation
	with	Aerogear
In-Reply-To: <351459117.67219689.1413221431843.JavaMail.zimbra@redhat.com>
References: <1413206325014-9440.post@n5.nabble.com>
	<CAAg5f2RzX-LiAZ8zuj9_wmWDrsxiM5w9w_jrZXupWsV_MCypXw@mail.gmail.com>
	<006c01cfe6eb$47d4dfb0$d77e9f10$@fastlane-it.com>
	<CAAg5f2QXUe=8cVmwGXrjyM5EK3=9xEJMK4AniAx+Hnz5qj4nVQ@mail.gmail.com>
	<009601cfe6ef$2f9219f0$8eb64dd0$@fastlane-it.com>
	<CAAg5f2RLtRzQk+qhAJERUJdztpZiuY=mCN6WPAGzrMeKcpN2hg@mail.gmail.com>
	<20141013143808.GA35341@abstractj.org>
	<351459117.67219689.1413221431843.JavaMail.zimbra@redhat.com>
Message-ID: <20141013203214.GA42946@abstractj.org>

Thank you guys, a JIRA was created to track the issue:
https://issues.jboss.org/browse/AGPUSH-1047

It will be the next item after user management.

On 2014-10-13, Stian Thorgersen wrote:
>
>
> ----- Original Message -----
> > From: "Bruno Oliveira" <bruno at abstractj.org>
> > To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> > Sent: Monday, 13 October, 2014 4:38:08 PM
> > Subject: Re: [aerogear-dev] Using existing Keycloak installation with	Aerogear
> >
> > On 2014-10-13, Matthias Wessendorf wrote:
> > > On Mon, Oct 13, 2014 at 4:08 PM, Egor Kolesnikov <
> > > egor.kolesnikov at fastlane-it.com> wrote:
> > >
> > > > Hi Matthias
> > > >
> > > >
> > > >
> > > > I do understand that Aerogear is quite young product and may not have all
> > > > features yet
> > > >
> > >
> > > AeroGear is more, than just its UPS (UnifiedPush Server) - which we are
> > > talking about here :)
> > >
> > >
> > > > ? just need to understand your vision of the project to align our further
> > > > development appropriately.
> > > >
> > > >
> > > >
> > > > Having said that, I can see two possible integration options with
> > > > projects
> > > > like ours:
> > > >
> > > > 1.       Aerogear+Keycloak combo used for ?all things auth? (this will
> > > > require unlocking master/admin user);
> > > >
> > > moving forward, I'd like us to go there. Again it was just done to limit
> > > the initial scope of the UPS
> > >
> > >
> > >
> > > > 2.       Configuring Aerogear to use external Keycloak installation.
> > > >
> > > we have had discussions about that too. that it should be possible to have
> > > our UnifiedPush Server on one machine, and a standalone keycloak server,
> > > that is used for more. not just UPS
> >
> > I think it makes perfect sense. There are two solutions quick or slow.
> >
> > 1. Quick: enable our developers to make use of not only AeroGear, but
> > create new realms as well. Also, let them, do whatever they want with
> > the admin.
> >
> > 2. Slow (I'm +1 on it). Dettach UPS from Keycloak and use as an external
> > installation. (off course, provide an easy way to install). If we think
> > carefuly, people might want to have 1 server with Keycloak and 4 with
> > UPS or the opposite.
>
> +1000 To option 2. The other option doesn't really make that much sense to me.
>
> >
> >
> > >
> > >
> > >
> > > > Option 1 appears to be the easiest way around, whether Option 2 looks
> > > > like
> > > > the most appropriate solution in the SSO world ? as in, there?s still a
> > > > ?single? sign-on point which is used by all third-party systems. If I
> > > > understand correctly, this could possibly be as easy as setting up
> > > > auth-server-url property in Aerogear?s keycloak.json so it delegates to
> > > > external Keycloak instance instead of using its ?own? one.
> > > >
> > > >
> > > >
> > > > I?m happy to spend some time investigating and experimenting with both
> > > > options.
> > > >
> > > >
> > > >
> > > > Cheers
> > > >
> > > > Egor
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> > > > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> > > > *Sent:* Tuesday, 14 October 2014 12:49 AM
> > > >
> > > > *To:* AeroGear Developer Mailing List
> > > > *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> > > > Aerogear
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Oct 13, 2014 at 3:40 PM, Egor Kolesnikov <
> > > > egor.kolesnikov at fastlane-it.com> wrote:
> > > >
> > > > Hi Matthias
> > > >
> > > >
> > > >
> > > > That?s correct ? we are already using Keycloak to secure our RESTful APIs
> > > > for mobile and web client access. Not that having separate installation
> > > > for
> > > > exclusive Aerogear is a dealbreaker, but it would re-introduce the
> > > > problem
> > > > Keycloak was supposed to solve in the first place J
> > > >
> > > >
> > > >
> > > > fully understand! But we, initially, felt like limiting a bit. that said,
> > > > we are flexible and there might be a chance to have this changed
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I can see that UpsSecurityApplication class kills off Keycloak admin user
> > > > in master realm ? would it break anything if I disabled this feature and
> > > > started using Aerogear-supplied Keycloak for other purposes on separate
> > > > realms?
> > > >
> > > >
> > > >
> > > > I don't think so (not tested). I recall we did this mainly to avoid
> > > > adding
> > > > new realms
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Our use case is mobile app (iOS+android), backend and AngularJS-based web
> > > > frontend and so far Keycloak fits our purpose like a glove. Now that
> > > > we?re
> > > > adding Push notification support, Aerogear appears to be quite logical
> > > > choice.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > sounds great!
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Egor
> > > >
> > > >
> > > >
> > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> > > > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> > > > *Sent:* Tuesday, 14 October 2014 12:29 AM
> > > > *To:* AeroGear Developer Mailing List
> > > > *Subject:* Re: [aerogear-dev] Using existing Keycloak installation with
> > > > Aerogear
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > >
> > > >
> > > > for the UnifiedPush Server the initial integration case was to function
> > > > only for the need of the AeroGear UnifiedPush server.
> > > >
> > > >
> > > >
> > > > So, looks like, you'd appreciate a bit more flexibility, to basically use
> > > > the auth-server for other apps as well ?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Oct 13, 2014 at 3:18 PM, ekolesnikov <ek at fastlane-it.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Apologies for writing straight into DEV forums - I was unable to locate
> > > > "aerogear-users" mailing list anywhere. Please feel free to point me to
> > > > the
> > > > right direction if this mailing list is inappropriate for questions like
> > > > this.
> > > >
> > > > Is it possible to use/integrate Aerogear with existing Keycloak
> > > > installation? We are already using Keycloak for all things auth in our
> > > > application and have found ourselves in the situation where we
> > > > potentially
> > > > have to manage separate infrastructure - which makes the whole point of
> > > > using Keycloak a bit irrelevant.
> > > >
> > > > As an alternative, we could consider using Keycloak supplied with with
> > > > Aerogear - unfortunately, it looks like Aerogear has disabled Keycloak
> > > > option to create additional realms.
> > > >
> > > > I would really appreciate it if you could share your thought on this.
> > > >
> > > > Thanks
> > > > Egor
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context:
> > > > http://aerogear-dev.1069024.n5.nabble.com/Using-existing-Keycloak-installation-with-Aerogear-tp9440.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
> > > >
> > > >
> > > > ------------------------------
> > > >
> > > > <http://www.avast.com/>
> > > >
> > > > This email is free from viruses and malware because avast! Antivirus
> > > > <http://www.avast.com/> protection is active.
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > > >
> > > >
> > > > ------------------------------
> > > >    <http://www.avast.com/>
> > > >
> > > > This email is free from viruses and malware because avast! Antivirus
> > > > <http://www.avast.com/> protection is active.
> > > >
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From supittma at redhat.com  Mon Oct 13 18:12:52 2014
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 13 Oct 2014 18:12:52 -0400
Subject: [aerogear-dev] Sync on Android
Message-ID: <543C4E64.9020802@redhat.com>

TL;DR; Watch this repo over the next few days :

https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync

Currently I am researching integrating the sync client technology that 
DanBev, LolQuist et al have been working on into Android all proper 
like.  Danbev wrote a POC demo a while ago* which uses the Java 
websocket client.  This seems to work "OK" but there is a lot of work 
getting websockets working right on Android.  However, Google has a two 
way messaging protocol built into Google Play Services on top of GCM.  
This is the technology I am trying to introduce to the sync systems in 
this branch.

This branch includes a fork of the server library and a fork of the 
client library which interact with GCM on the client and XMPP on the 
server side.  Right now it compiles and not much else.  However, because 
the server is decoupled from the connection handling, adding in the 
correct hooks has been rather simple.  There are going to be some issues 
to hammer out once this gets past "compiling" and makes it into "demoable".

First, the server does not receive implicit connect/disconnect messages 
from Google per device.  Google does send Ack/Nack messages however so 
with some bookkeeping connections/shadows/etc can be properly 
maintained.    There is a similar mechanism on the client side; however, 
we may need to expand the sync protocol to include some kind of heartbeat.

Second, the sync server isn't multitenant.  This means that until we 
figure out how to merge, things listening to WebSockets don't hear 
things listening to XMPP or see updates from one to the other.

Finally, Google Play Services is not FOSS by any stretch of the 
imagination.  However, having a single connection managed by the OS is 
great for usability, speed of development, battery life, etc so I feel 
like this is more getting mileage out of the chunk of my soul I tossed 
in the black Googley shredder for UPS and less of a deal breaker.

As I've said right now, today, this code is work in progress.  Soon it 
will be proof of concept and we can discuss how to work around these 
issues and merge the ideas back into mainline.


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

PS: WebSocket's biggest problems are maintaining connections and 
performing message redelivery in a sporatic connection scenario. This is 
one of those things which is a lot of work to get right both on our end 
as service providers and on the developer's end as consumers.  
Additionally, Android L is going to include a lot more end user 
configurability which will affect when/how messages are delivered.  To 
do WebSockets right we will have to respect those settings as well.  It 
is my assumption (we all know what that means) that Google Play Services 
will correctly enforce data/power settings out of the box as well as 
correctly maintain messaging connections and delivery.

From daniel.bevenius at gmail.com  Tue Oct 14 01:48:36 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 14 Oct 2014 07:48:36 +0200
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <543C4E64.9020802@redhat.com>
References: <543C4E64.9020802@redhat.com>
Message-ID: <CAFJm-3Fvc3Cwg_8F9qJ3gQoHMtv9GwLNYxSgCswoo2S9rHwjAA@mail.gmail.com>

This sounds really nice! Looking forward to seeing it in actions.

>Second, the sync server isn't multitenant.  This means that until we figure
out how to merge, things listening to WebSockets don't hear things
listening to XMPP or see updates from one to the other.
I was thinking that perhaps we can have the XMPP server part of the Netty
DiffSync server as well. It would be pretty much as it right now, but be a
Netty channel handler in the same pipeline. Let me know if this makes
sense. Let me know if what you think and if you like I'd be happy to take a
stab at this.



On 14 October 2014 00:12, Summers Pittman <supittma at redhat.com> wrote:

> TL;DR; Watch this repo over the next few days :
>
> https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
>
> Currently I am researching integrating the sync client technology that
> DanBev, LolQuist et al have been working on into Android all proper
> like.  Danbev wrote a POC demo a while ago* which uses the Java
> websocket client.  This seems to work "OK" but there is a lot of work
> getting websockets working right on Android.  However, Google has a two
> way messaging protocol built into Google Play Services on top of GCM.
> This is the technology I am trying to introduce to the sync systems in
> this branch.
>
> This branch includes a fork of the server library and a fork of the
> client library which interact with GCM on the client and XMPP on the
> server side.  Right now it compiles and not much else.  However, because
> the server is decoupled from the connection handling, adding in the
> correct hooks has been rather simple.  There are going to be some issues
> to hammer out once this gets past "compiling" and makes it into "demoable".
>
> First, the server does not receive implicit connect/disconnect messages
> from Google per device.  Google does send Ack/Nack messages however so
> with some bookkeeping connections/shadows/etc can be properly
> maintained.    There is a similar mechanism on the client side; however,
> we may need to expand the sync protocol to include some kind of heartbeat.
>
> Second, the sync server isn't multitenant.  This means that until we
> figure out how to merge, things listening to WebSockets don't hear
> things listening to XMPP or see updates from one to the other.
>
> Finally, Google Play Services is not FOSS by any stretch of the
> imagination.  However, having a single connection managed by the OS is
> great for usability, speed of development, battery life, etc so I feel
> like this is more getting mileage out of the chunk of my soul I tossed
> in the black Googley shredder for UPS and less of a deal breaker.
>
> As I've said right now, today, this code is work in progress.  Soon it
> will be proof of concept and we can discuss how to work around these
> issues and merge the ideas back into mainline.
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
> PS: WebSocket's biggest problems are maintaining connections and
> performing message redelivery in a sporatic connection scenario. This is
> one of those things which is a lot of work to get right both on our end
> as service providers and on the developer's end as consumers.
> Additionally, Android L is going to include a lot more end user
> configurability which will affect when/how messages are delivered.  To
> do WebSockets right we will have to respect those settings as well.  It
> is my assumption (we all know what that means) that Google Play Services
> will correctly enforce data/power settings out of the box as well as
> correctly maintain messaging connections and delivery.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141014/340bffc8/attachment-0001.html 

From cvasilak at gmail.com  Tue Oct 14 03:23:12 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 14 Oct 2014 10:23:12 +0300
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <543C4E64.9020802@redhat.com>
References: <543C4E64.9020802@redhat.com>
Message-ID: <D7C3B9E6-8C5E-4D47-BD82-F11FBDBD92DA@gmail.com>

interesting work Summers  +1 to utilise platform native features 

thanks for sharing

On Oct 14, 2014, at 1:12 AM, Summers Pittman <supittma at redhat.com> wrote:

> TL;DR; Watch this repo over the next few days :
> 
> https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
> 
> Currently I am researching integrating the sync client technology that 
> DanBev, LolQuist et al have been working on into Android all proper 
> like.  Danbev wrote a POC demo a while ago* which uses the Java 
> websocket client.  This seems to work "OK" but there is a lot of work 
> getting websockets working right on Android.  However, Google has a two 
> way messaging protocol built into Google Play Services on top of GCM.  
> This is the technology I am trying to introduce to the sync systems in 
> this branch.
> 
> This branch includes a fork of the server library and a fork of the 
> client library which interact with GCM on the client and XMPP on the 
> server side.  Right now it compiles and not much else.  However, because 
> the server is decoupled from the connection handling, adding in the 
> correct hooks has been rather simple.  There are going to be some issues 
> to hammer out once this gets past "compiling" and makes it into "demoable".
> 
> First, the server does not receive implicit connect/disconnect messages 
> from Google per device.  Google does send Ack/Nack messages however so 
> with some bookkeeping connections/shadows/etc can be properly 
> maintained.    There is a similar mechanism on the client side; however, 
> we may need to expand the sync protocol to include some kind of heartbeat.
> 
> Second, the sync server isn't multitenant.  This means that until we 
> figure out how to merge, things listening to WebSockets don't hear 
> things listening to XMPP or see updates from one to the other.
> 
> Finally, Google Play Services is not FOSS by any stretch of the 
> imagination.  However, having a single connection managed by the OS is 
> great for usability, speed of development, battery life, etc so I feel 
> like this is more getting mileage out of the chunk of my soul I tossed 
> in the black Googley shredder for UPS and less of a deal breaker.
> 
> As I've said right now, today, this code is work in progress.  Soon it 
> will be proof of concept and we can discuss how to work around these 
> issues and merge the ideas back into mainline.
> 
> 
> -- 
> Summers Pittman
>>> Phone:404 941 4698
>>> Java is my crack.
> 
> PS: WebSocket's biggest problems are maintaining connections and 
> performing message redelivery in a sporatic connection scenario. This is 
> one of those things which is a lot of work to get right both on our end 
> as service providers and on the developer's end as consumers.  
> Additionally, Android L is going to include a lot more end user 
> configurability which will affect when/how messages are delivered.  To 
> do WebSockets right we will have to respect those settings as well.  It 
> is my assumption (we all know what that means) that Google Play Services 
> will correctly enforce data/power settings out of the box as well as 
> correctly maintain messaging connections and delivery.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From matzew at apache.org  Tue Oct 14 03:46:47 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 14 Oct 2014 09:46:47 +0200
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <543C4E64.9020802@redhat.com>
References: <543C4E64.9020802@redhat.com>
Message-ID: <CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>

On Tue, Oct 14, 2014 at 12:12 AM, Summers Pittman <supittma at redhat.com>
wrote:

> TL;DR; Watch this repo over the next few days :
>
> https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
>
> Currently I am researching integrating the sync client technology that
> DanBev, LolQuist et al have been working on into Android all proper
> like.  Danbev wrote a POC demo a while ago* which uses the Java
> websocket client.


what java client was used?



> This seems to work "OK" but there is a lot of work
> getting websockets working right on Android.


+1


> However, Google has a two
> way messaging protocol built into Google Play Services on top of GCM.
> This is the technology I am trying to introduce to the sync systems in
> this branch.
>
> This branch includes a fork of the server library and a fork of the
> client library which interact with GCM on the client and XMPP on the
> server side.  Right now it compiles and not much else.  However, because
> the server is decoupled from the connection handling, adding in the
> correct hooks has been rather simple.  There are going to be some issues
> to hammer out once this gets past "compiling" and makes it into "demoable".
>
> First, the server does not receive implicit connect/disconnect messages
> from Google per device.  Google does send Ack/Nack messages however so
> with some bookkeeping connections/shadows/etc can be properly
> maintained.    There is a similar mechanism on the client side; however,
> we may need to expand the sync protocol to include some kind of heartbeat.
>
> Second, the sync server isn't multitenant.  This means that until we
> figure out how to merge, things listening to WebSockets don't hear
> things listening to XMPP or see updates from one to the other.
>

on our sync-server, can't have have different "endpoints" (e.g. xmpp,
websocket),
that all connect to its heart, the Netty-based DiffSync engine?



>
> Finally, Google Play Services is not FOSS by any stretch of the
> imagination.  However, having a single connection managed by the OS is
> great for usability, speed of development, battery life, etc so I feel
> like this is more getting mileage out of the chunk of my soul I tossed
> in the black Googley shredder for UPS and less of a deal breaker.
>

not sure I follow here


>
> As I've said right now, today, this code is work in progress.  Soon it
> will be proof of concept and we can discuss how to work around these
> issues and merge the ideas back into mainline.
>

looking forward to that.


>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
> PS: WebSocket's biggest problems are maintaining connections and
> performing message redelivery in a sporatic connection scenario. This is
> one of those things which is a lot of work to get right both on our end
> as service providers and on the developer's end as consumers.
> Additionally, Android L is going to include a lot more end user
> configurability which will affect when/how messages are delivered.


any link to share?


> To
> do WebSockets right we will have to respect those settings as well.  It
> is my assumption (we all know what that means) that Google Play Services
> will correctly enforce data/power settings out of the box as well as
> correctly maintain messaging connections and delivery.
>

instead of having our Android lib do a WS connection (including all the
required work for maintaining etc), we could leverage the XMPP from GCM.
That's the prefered route you are suggesting, right ?


ANDROID   <----> GCM <------> Sync-Server


This would allow us, to do more than we do atm on "pure" push
notifications, via GCM. In this scenario we can do a two way communication:
Android client can send data to Sync-Server (via GCM), and receive "diff"
from the server, via GCM.


-Matthias


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



-- 
Matthias Wessendorf

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

From daniel.bevenius at gmail.com  Tue Oct 14 03:55:43 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 14 Oct 2014 09:55:43 +0200
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>
References: <543C4E64.9020802@redhat.com>
	<CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>
Message-ID: <CAFJm-3HsnF4T41iatcKnNj_wRBrU9QPsJyiv_NxjteBiaeexVg@mail.gmail.com>

>what java client was used?
There is an Java client for sync[1] which was used for the Android demo[2]

[1]
https://github.com/danbev/aerogear-sync-server/tree/differential-synchronization/diffsync/client-netty
[2] https://github.com/danbev/android-diffsync-demo

>on our sync-server, can't have have different "endpoints" (e.g. xmpp,
websocket), that all connect to its heart, the Netty-based DiffSync engine?
This is what I had in mind when a wrote my comment about making the XMPP
into a handler. It would not have to be tied to Netty, but we could use the
XMPP server from within Netty and make sure that it get separate threading
etc.


On 14 October 2014 09:46, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
> On Tue, Oct 14, 2014 at 12:12 AM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> TL;DR; Watch this repo over the next few days :
>>
>> https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
>>
>> Currently I am researching integrating the sync client technology that
>> DanBev, LolQuist et al have been working on into Android all proper
>> like.  Danbev wrote a POC demo a while ago* which uses the Java
>> websocket client.
>
>
> what java client was used?
>
>
>
>> This seems to work "OK" but there is a lot of work
>> getting websockets working right on Android.
>
>
> +1
>
>
>> However, Google has a two
>> way messaging protocol built into Google Play Services on top of GCM.
>> This is the technology I am trying to introduce to the sync systems in
>> this branch.
>>
>> This branch includes a fork of the server library and a fork of the
>> client library which interact with GCM on the client and XMPP on the
>> server side.  Right now it compiles and not much else.  However, because
>> the server is decoupled from the connection handling, adding in the
>> correct hooks has been rather simple.  There are going to be some issues
>> to hammer out once this gets past "compiling" and makes it into
>> "demoable".
>>
>> First, the server does not receive implicit connect/disconnect messages
>> from Google per device.  Google does send Ack/Nack messages however so
>> with some bookkeeping connections/shadows/etc can be properly
>> maintained.    There is a similar mechanism on the client side; however,
>> we may need to expand the sync protocol to include some kind of heartbeat.
>>
>> Second, the sync server isn't multitenant.  This means that until we
>> figure out how to merge, things listening to WebSockets don't hear
>> things listening to XMPP or see updates from one to the other.
>>
>
> on our sync-server, can't have have different "endpoints" (e.g. xmpp,
> websocket),
> that all connect to its heart, the Netty-based DiffSync engine?
>
>
>
>>
>> Finally, Google Play Services is not FOSS by any stretch of the
>> imagination.  However, having a single connection managed by the OS is
>> great for usability, speed of development, battery life, etc so I feel
>> like this is more getting mileage out of the chunk of my soul I tossed
>> in the black Googley shredder for UPS and less of a deal breaker.
>>
>
> not sure I follow here
>
>
>>
>> As I've said right now, today, this code is work in progress.  Soon it
>> will be proof of concept and we can discuss how to work around these
>> issues and merge the ideas back into mainline.
>>
>
> looking forward to that.
>
>
>>
>>
>> --
>> Summers Pittman
>> >>Phone:404 941 4698
>> >>Java is my crack.
>>
>> PS: WebSocket's biggest problems are maintaining connections and
>> performing message redelivery in a sporatic connection scenario. This is
>> one of those things which is a lot of work to get right both on our end
>> as service providers and on the developer's end as consumers.
>> Additionally, Android L is going to include a lot more end user
>> configurability which will affect when/how messages are delivered.
>
>
> any link to share?
>
>
>> To
>> do WebSockets right we will have to respect those settings as well.  It
>> is my assumption (we all know what that means) that Google Play Services
>> will correctly enforce data/power settings out of the box as well as
>> correctly maintain messaging connections and delivery.
>>
>
> instead of having our Android lib do a WS connection (including all the
> required work for maintaining etc), we could leverage the XMPP from GCM.
> That's the prefered route you are suggesting, right ?
>
>
> ANDROID   <----> GCM <------> Sync-Server
>
>
> This would allow us, to do more than we do atm on "pure" push
> notifications, via GCM. In this scenario we can do a two way communication:
> Android client can send data to Sync-Server (via GCM), and receive "diff"
> from the server, via GCM.
>
>
> -Matthias
>
>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141014/407ef3a6/attachment-0001.html 

From matzew at apache.org  Tue Oct 14 04:00:25 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 14 Oct 2014 10:00:25 +0200
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <CAFJm-3HsnF4T41iatcKnNj_wRBrU9QPsJyiv_NxjteBiaeexVg@mail.gmail.com>
References: <543C4E64.9020802@redhat.com>
	<CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>
	<CAFJm-3HsnF4T41iatcKnNj_wRBrU9QPsJyiv_NxjteBiaeexVg@mail.gmail.com>
Message-ID: <CAAg5f2T-LQ1DvRkqLA5o4ZEpQ_-AYK1EzWQZLx7seLU33YMkZw@mail.gmail.com>

On Tue, Oct 14, 2014 at 9:55 AM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> >what java client was used?
> There is an Java client for sync[1] which was used for the Android demo[2]
>
> [1]
> https://github.com/danbev/aerogear-sync-server/tree/differential-synchronization/diffsync/client-netty
> [2] https://github.com/danbev/android-diffsync-demo
>

thanks for sharing!


>
> >on our sync-server, can't have have different "endpoints" (e.g. xmpp,
> websocket), that all connect to its heart, the Netty-based DiffSync
> engine?
> This is what I had in mind when a wrote my comment about making the XMPP
> into a handler.
>

hehe


> It would not have to be tied to Netty, but we could use the XMPP server
> from within Netty and make sure that it get separate threading etc.
>

sounds good!



>
>
> On 14 October 2014 09:46, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>> On Tue, Oct 14, 2014 at 12:12 AM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> TL;DR; Watch this repo over the next few days :
>>>
>>> https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
>>>
>>> Currently I am researching integrating the sync client technology that
>>> DanBev, LolQuist et al have been working on into Android all proper
>>> like.  Danbev wrote a POC demo a while ago* which uses the Java
>>> websocket client.
>>
>>
>> what java client was used?
>>
>>
>>
>>> This seems to work "OK" but there is a lot of work
>>> getting websockets working right on Android.
>>
>>
>> +1
>>
>>
>>> However, Google has a two
>>> way messaging protocol built into Google Play Services on top of GCM.
>>> This is the technology I am trying to introduce to the sync systems in
>>> this branch.
>>>
>>> This branch includes a fork of the server library and a fork of the
>>> client library which interact with GCM on the client and XMPP on the
>>> server side.  Right now it compiles and not much else.  However, because
>>> the server is decoupled from the connection handling, adding in the
>>> correct hooks has been rather simple.  There are going to be some issues
>>> to hammer out once this gets past "compiling" and makes it into
>>> "demoable".
>>>
>>> First, the server does not receive implicit connect/disconnect messages
>>> from Google per device.  Google does send Ack/Nack messages however so
>>> with some bookkeeping connections/shadows/etc can be properly
>>> maintained.    There is a similar mechanism on the client side; however,
>>> we may need to expand the sync protocol to include some kind of
>>> heartbeat.
>>>
>>> Second, the sync server isn't multitenant.  This means that until we
>>> figure out how to merge, things listening to WebSockets don't hear
>>> things listening to XMPP or see updates from one to the other.
>>>
>>
>> on our sync-server, can't have have different "endpoints" (e.g. xmpp,
>> websocket),
>> that all connect to its heart, the Netty-based DiffSync engine?
>>
>>
>>
>>>
>>> Finally, Google Play Services is not FOSS by any stretch of the
>>> imagination.  However, having a single connection managed by the OS is
>>> great for usability, speed of development, battery life, etc so I feel
>>> like this is more getting mileage out of the chunk of my soul I tossed
>>> in the black Googley shredder for UPS and less of a deal breaker.
>>>
>>
>> not sure I follow here
>>
>>
>>>
>>> As I've said right now, today, this code is work in progress.  Soon it
>>> will be proof of concept and we can discuss how to work around these
>>> issues and merge the ideas back into mainline.
>>>
>>
>> looking forward to that.
>>
>>
>>>
>>>
>>> --
>>> Summers Pittman
>>> >>Phone:404 941 4698
>>> >>Java is my crack.
>>>
>>> PS: WebSocket's biggest problems are maintaining connections and
>>> performing message redelivery in a sporatic connection scenario. This is
>>> one of those things which is a lot of work to get right both on our end
>>> as service providers and on the developer's end as consumers.
>>> Additionally, Android L is going to include a lot more end user
>>> configurability which will affect when/how messages are delivered.
>>
>>
>> any link to share?
>>
>>
>>> To
>>> do WebSockets right we will have to respect those settings as well.  It
>>> is my assumption (we all know what that means) that Google Play Services
>>> will correctly enforce data/power settings out of the box as well as
>>> correctly maintain messaging connections and delivery.
>>>
>>
>> instead of having our Android lib do a WS connection (including all the
>> required work for maintaining etc), we could leverage the XMPP from GCM.
>> That's the prefered route you are suggesting, right ?
>>
>>
>> ANDROID   <----> GCM <------> Sync-Server
>>
>>
>> This would allow us, to do more than we do atm on "pure" push
>> notifications, via GCM. In this scenario we can do a two way communication:
>> Android client can send data to Sync-Server (via GCM), and receive "diff"
>> from the server, via GCM.
>>
>>
>> -Matthias
>>
>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141014/6dc5387f/attachment.html 

From avibelli at redhat.com  Tue Oct 14 05:57:17 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Tue, 14 Oct 2014 02:57:17 -0700 (PDT)
Subject: [aerogear-dev] Keycloak version 1.0.2.Final
Message-ID: <1413280637423-9456.post@n5.nabble.com>

Hi all, 
Keycloak 1.0.2.Final has been released 6 days ago, I would like to know if
there are any plans to upgrade UPS to use 1.0.2.Final instead of
1.0.1.Final.

1.0.2.Final is a maintenance release and contains bug fixes and one (minor)
security fix
(https://issues.jboss.org/issues/?jql=project%20%3D%20KEYCLOAK%20AND%20fixVersion%20%3D%201.0.2.Final%20AND%20resolution%20%3D%20Done),
and has a nice document about security vulnerabilities and solutions

Thanks!
Andrea



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Keycloak-version-1-0-2-Final-tp9456.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From lukas.fryc at gmail.com  Tue Oct 14 07:11:52 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Tue, 14 Oct 2014 13:11:52 +0200
Subject: [aerogear-dev] Keycloak version 1.0.2.Final
In-Reply-To: <1413280637423-9456.post@n5.nabble.com>
References: <1413280637423-9456.post@n5.nabble.com>
Message-ID: <CAEroY37G_AZ7fHEru3wcXqeKd278UFSqPmd5K6Tz2NhH45rGWA@mail.gmail.com>

Hi Andrea,

I know about one minor fix that was fixed in Keycloak:
https://issues.jboss.org/browse/AGPUSH-1049

I've created an issue to upgrade to KC 1.0.2 in UPS:
https://issues.jboss.org/browse/AGPUSH-1050


Cheers,

~ Lukas

On Tue, Oct 14, 2014 at 11:57 AM, Andrea Vibelli <avibelli at redhat.com>
wrote:

> Hi all,
> Keycloak 1.0.2.Final has been released 6 days ago, I would like to know if
> there are any plans to upgrade UPS to use 1.0.2.Final instead of
> 1.0.1.Final.
>
> 1.0.2.Final is a maintenance release and contains bug fixes and one (minor)
> security fix
> (
> https://issues.jboss.org/issues/?jql=project%20%3D%20KEYCLOAK%20AND%20fixVersion%20%3D%201.0.2.Final%20AND%20resolution%20%3D%20Done
> ),
> and has a nice document about security vulnerabilities and solutions
>
> Thanks!
> Andrea
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Keycloak-version-1-0-2-Final-tp9456.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/20141014/c666b123/attachment.html 

From matzew at apache.org  Tue Oct 14 07:14:42 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 14 Oct 2014 13:14:42 +0200
Subject: [aerogear-dev] Keycloak version 1.0.2.Final
In-Reply-To: <CAEroY37G_AZ7fHEru3wcXqeKd278UFSqPmd5K6Tz2NhH45rGWA@mail.gmail.com>
References: <1413280637423-9456.post@n5.nabble.com>
	<CAEroY37G_AZ7fHEru3wcXqeKd278UFSqPmd5K6Tz2NhH45rGWA@mail.gmail.com>
Message-ID: <CAAg5f2Rwv4sJ412ppo=hN8OQb_u9-OdTvfNSvX+okVLoqShqUg@mail.gmail.com>

On Tue, Oct 14, 2014 at 1:11 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hi Andrea,
>
> I know about one minor fix that was fixed in Keycloak:
> https://issues.jboss.org/browse/AGPUSH-1049
>
> I've created an issue to upgrade to KC 1.0.2 in UPS:
> https://issues.jboss.org/browse/AGPUSH-1050
>

so did abstractj a few days ago:
https://issues.jboss.org/browse/AGPUSH-1042

please check for JIRAs before creating a lot of dups


>
>
> Cheers,
>
> ~ Lukas
>
> On Tue, Oct 14, 2014 at 11:57 AM, Andrea Vibelli <avibelli at redhat.com>
> wrote:
>
>> Hi all,
>> Keycloak 1.0.2.Final has been released 6 days ago, I would like to know if
>> there are any plans to upgrade UPS to use 1.0.2.Final instead of
>> 1.0.1.Final.
>>
>> 1.0.2.Final is a maintenance release and contains bug fixes and one
>> (minor)
>> security fix
>> (
>> https://issues.jboss.org/issues/?jql=project%20%3D%20KEYCLOAK%20AND%20fixVersion%20%3D%201.0.2.Final%20AND%20resolution%20%3D%20Done
>> ),
>> and has a nice document about security vulnerabilities and solutions
>>
>> Thanks!
>> Andrea
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/Keycloak-version-1-0-2-Final-tp9456.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/20141014/c63a8c6a/attachment-0001.html 

From supittma at redhat.com  Tue Oct 14 09:37:49 2014
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 14 Oct 2014 09:37:49 -0400
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>
References: <543C4E64.9020802@redhat.com>
	<CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>
Message-ID: <543D272D.2070907@redhat.com>

I'll skip the questions DanBev Answered.

On 10/14/2014 03:46 AM, Matthias Wessendorf wrote:
>
>
> On Tue, Oct 14, 2014 at 12:12 AM, Summers Pittman <supittma at redhat.com 
> <mailto:supittma at redhat.com>> wrote:
>
>     TL;DR; Watch this repo over the next few days :
>
>     https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
>
>     Currently I am researching integrating the sync client technology that
>     DanBev, LolQuist et al have been working on into Android all proper
>     like.  Danbev wrote a POC demo a while ago* which uses the Java
>     websocket client. 
>
>
> what java client was used?
>
>     This seems to work "OK" but there is a lot of work
>     getting websockets working right on Android. 
>
>
> +1
>
>     However, Google has a two
>     way messaging protocol built into Google Play Services on top of GCM.
>     This is the technology I am trying to introduce to the sync systems in
>     this branch.
>
>     This branch includes a fork of the server library and a fork of the
>     client library which interact with GCM on the client and XMPP on the
>     server side.  Right now it compiles and not much else. However,
>     because
>     the server is decoupled from the connection handling, adding in the
>     correct hooks has been rather simple.  There are going to be some
>     issues
>     to hammer out once this gets past "compiling" and makes it into
>     "demoable".
>
>     First, the server does not receive implicit connect/disconnect
>     messages
>     from Google per device.  Google does send Ack/Nack messages however so
>     with some bookkeeping connections/shadows/etc can be properly
>     maintained.    There is a similar mechanism on the client side;
>     however,
>     we may need to expand the sync protocol to include some kind of
>     heartbeat.
>
>     Second, the sync server isn't multitenant.  This means that until we
>     figure out how to merge, things listening to WebSockets don't hear
>     things listening to XMPP or see updates from one to the other.
>
>
> on our sync-server, can't have have different "endpoints" (e.g. xmpp, 
> websocket),
> that all connect to its heart, the Netty-based DiffSync engine?
>
>
>     Finally, Google Play Services is not FOSS by any stretch of the
>     imagination.  However, having a single connection managed by the OS is
>     great for usability, speed of development, battery life, etc so I feel
>     like this is more getting mileage out of the chunk of my soul I tossed
>     in the black Googley shredder for UPS and less of a deal breaker.
>
>
> not sure I follow here
Google Play Services is proprietary software.  I would prefer to keep as 
much stuff open source as possible.  Since we have already agreed that 
leaning on GPS is OK, I don't feel as bad about using it again.
>
>
>     As I've said right now, today, this code is work in progress.  Soon it
>     will be proof of concept and we can discuss how to work around these
>     issues and merge the ideas back into mainline.
>
>
> looking forward to that.
>
>
>
>     --
>     Summers Pittman
>     >>Phone:404 941 4698
>     >>Java is my crack.
>
>     PS: WebSocket's biggest problems are maintaining connections and
>     performing message redelivery in a sporatic connection scenario.
>     This is
>     one of those things which is a lot of work to get right both on
>     our end
>     as service providers and on the developer's end as consumers.
>     Additionally, Android L is going to include a lot more end user
>     configurability which will affect when/how messages are delivered. 
>
>
> any link to share?
http://www.androidcentral.com/android-l-preview-battery-and-power-management

Specifically I had the Job Scheduler APIs in mind.

>     To
>     do WebSockets right we will have to respect those settings as
>     well.  It
>     is my assumption (we all know what that means) that Google Play
>     Services
>     will correctly enforce data/power settings out of the box as well as
>     correctly maintain messaging connections and delivery.
>
>
> instead of having our Android lib do a WS connection (including all 
> the required work for maintaining etc), we could leverage the XMPP 
> from GCM.
> That's the prefered route you are suggesting, right ?
Yes.  XMPP is only exposed on the server side.  On the client side it 
looks like Push notifications and calling a send method on the gcm client.
>
>
> ANDROID   <----> GCM <------> Sync-Server
>
>
> This would allow us, to do more than we do atm on "pure" push 
> notifications, via GCM. In this scenario we can do a two way 
> communication:
> Android client can send data to Sync-Server (via GCM), and receive 
> "diff" from the server, via GCM.
Yes.
>
>
> -Matthias
>
>     _______________________________________________
>     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


-- 
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/20141014/baa81b0a/attachment.html 

From daniel at passos.me  Tue Oct 14 10:36:53 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 14 Oct 2014 11:36:53 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
Message-ID: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>

Hi,

I?d like to run a new release of our parent/bom.

Here is some changes related to newer versions:

   - AEROGEAR-1526 - Update Android Support library version
   <https://issues.jboss.org/browse/AEROGEAR-1526>
   - AEROGEAR-1525 - Remove unnecessary dependencies
   <https://issues.jboss.org/browse/AEROGEAR-1525>
   - AEROGEAR-1524 - Change Android Maven Central stub to real Android
   library from Maven SDK deploy
   <https://issues.jboss.org/browse/AEROGEAR-1524>
   - AEROGEAR-1527 - Move gcm server and json simple from android bom to bom
   <https://issues.jboss.org/browse/AEROGEAR-1527>

Feel free to test it. I have plan to release it next thursday.

The staging repo is here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/

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

From matzew at apache.org  Tue Oct 14 15:47:00 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 14 Oct 2014 21:47:00 +0200
Subject: [aerogear-dev] Sync on Android
In-Reply-To: <543D272D.2070907@redhat.com>
References: <543C4E64.9020802@redhat.com>
	<CAAg5f2RXeo4pK_V=iNp3jEtxhykGqHyUs-FdvUf+5LqvP9BNiQ@mail.gmail.com>
	<543D272D.2070907@redhat.com>
Message-ID: <CAAg5f2SeDE9sZyhP9zZnyQhFLQWYZ_nkaAz=MW193Ae-wmNehg@mail.gmail.com>

On Tue, Oct 14, 2014 at 3:37 PM, Summers Pittman <supittma at redhat.com>
wrote:

>  I'll skip the questions DanBev Answered.
>
>
> On 10/14/2014 03:46 AM, Matthias Wessendorf wrote:
>
>
>
> On Tue, Oct 14, 2014 at 12:12 AM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> TL;DR; Watch this repo over the next few days :
>>
>> https://github.com/secondsun/aerogear-sync-server/tree/xmpp-diff-sync
>>
>> Currently I am researching integrating the sync client technology that
>> DanBev, LolQuist et al have been working on into Android all proper
>> like.  Danbev wrote a POC demo a while ago* which uses the Java
>> websocket client.
>
>
>  what java client was used?
>
>
>
>
>> This seems to work "OK" but there is a lot of work
>> getting websockets working right on Android.
>
>
>  +1
>
>
>> However, Google has a two
>> way messaging protocol built into Google Play Services on top of GCM.
>> This is the technology I am trying to introduce to the sync systems in
>> this branch.
>>
>> This branch includes a fork of the server library and a fork of the
>> client library which interact with GCM on the client and XMPP on the
>> server side.  Right now it compiles and not much else.  However, because
>> the server is decoupled from the connection handling, adding in the
>> correct hooks has been rather simple.  There are going to be some issues
>> to hammer out once this gets past "compiling" and makes it into
>> "demoable".
>>
>> First, the server does not receive implicit connect/disconnect messages
>> from Google per device.  Google does send Ack/Nack messages however so
>> with some bookkeeping connections/shadows/etc can be properly
>> maintained.    There is a similar mechanism on the client side; however,
>> we may need to expand the sync protocol to include some kind of heartbeat.
>>
>> Second, the sync server isn't multitenant.  This means that until we
>> figure out how to merge, things listening to WebSockets don't hear
>> things listening to XMPP or see updates from one to the other.
>>
>
>  on our sync-server, can't have have different "endpoints" (e.g. xmpp,
> websocket),
> that all connect to its heart, the Netty-based DiffSync engine?
>
>
>
>>
>> Finally, Google Play Services is not FOSS by any stretch of the
>> imagination.  However, having a single connection managed by the OS is
>> great for usability, speed of development, battery life, etc so I feel
>> like this is more getting mileage out of the chunk of my soul I tossed
>> in the black Googley shredder for UPS and less of a deal breaker.
>>
>
>  not sure I follow here
>
> Google Play Services is proprietary software.  I would prefer to keep as
> much stuff open source as possible.
>

ah, ok

Since we have already agreed that leaning on GPS is OK, I don't feel as bad
> about using it again.
>

yeah, I agree it's not a bad thing to leverage that


>
>
>
>>
>> As I've said right now, today, this code is work in progress.  Soon it
>> will be proof of concept and we can discuss how to work around these
>> issues and merge the ideas back into mainline.
>>
>
>  looking forward to that.
>
>
>>
>>
>> --
>> Summers Pittman
>> >>Phone:404 941 4698
>> >>Java is my crack.
>>
>> PS: WebSocket's biggest problems are maintaining connections and
>> performing message redelivery in a sporatic connection scenario. This is
>> one of those things which is a lot of work to get right both on our end
>> as service providers and on the developer's end as consumers.
>> Additionally, Android L is going to include a lot more end user
>> configurability which will affect when/how messages are delivered.
>
>
>  any link to share?
>
>
> http://www.androidcentral.com/android-l-preview-battery-and-power-management
>
> Specifically I had the Job Scheduler APIs in mind.
>
>
>
>> To
>> do WebSockets right we will have to respect those settings as well.  It
>> is my assumption (we all know what that means) that Google Play Services
>> will correctly enforce data/power settings out of the box as well as
>> correctly maintain messaging connections and delivery.
>>
>
>  instead of having our Android lib do a WS connection (including all the
> required work for maintaining etc), we could leverage the XMPP from GCM.
> That's the prefered route you are suggesting, right ?
>
> Yes.  XMPP is only exposed on the server side.  On the client side it
> looks like Push notifications and calling a send method on the gcm client.
>

sounds good.


>
>
>
>  ANDROID   <----> GCM <------> Sync-Server
>
>
>  This would allow us, to do more than we do atm on "pure" push
> notifications, via GCM. In this scenario we can do a two way communication:
>  Android client can send data to Sync-Server (via GCM), and receive
> "diff" from the server, via GCM.
>
> Yes.
>

sounds good!


>
>
>
>  -Matthias
>
>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Wed Oct 15 03:42:08 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 15 Oct 2014 09:42:08 +0200
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <543298AF.7060201@redhat.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
	<543298AF.7060201@redhat.com>
Message-ID: <CAAg5f2Tf-8rfh5x+jEUOiTMVQ_4-i8H=ZnF4cU2aRRp9QOfdXA@mail.gmail.com>

On Mon, Oct 6, 2014 at 3:27 PM, Summers Pittman <supittma at redhat.com> wrote:

>  On 10/06/2014 05:45 AM, Corinne Krych wrote:
>
> Hello Guys,
>
>  Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we
> worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a
> backend to demo Keycloak too.
>
>  Main idea is that for OAuth2 we demo external providers: Google,
> Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it
> with a web-app too. So that?s once the photo get uploaded you can view on
> desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js
> adapter). See backend demo [1]
>
>  @summers, passos: It would be nice to have an Android similar demo, wdyt?
>
> Shouldn't be a problem :)  More demos are always fun and will be a good
> thing to give the 2.0 code a in use test.
>

as a happy user of iOS' Share-n-Shoot, I fully agree. Having such an
Android app would be nice!
Also, good point, this app would be a good test for the 2.0 code line!

I have file a feature request for this to track it fure 2.0.x development:
https://issues.jboss.org/browse/AGDROID-301

Greetings,
Matthias


>  @lfryc @lholmquist should we use keyclaok.js only or is there a way to
> use ag.js? btw, your review is welcome on the js-angular part.
>
>  ++
> Corinne
>
>  [1]
> https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
>
>  PS: do you like kittens?
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141015/52adbc20/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 111801 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141015/52adbc20/attachment-0001.png 

From daniel at passos.me  Wed Oct 15 11:34:02 2014
From: daniel at passos.me (Daniel Passos)
Date: Wed, 15 Oct 2014 12:34:02 -0300
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <CAAg5f2Tf-8rfh5x+jEUOiTMVQ_4-i8H=ZnF4cU2aRRp9QOfdXA@mail.gmail.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
	<543298AF.7060201@redhat.com>
	<CAAg5f2Tf-8rfh5x+jEUOiTMVQ_4-i8H=ZnF4cU2aRRp9QOfdXA@mail.gmail.com>
Message-ID: <CAKjsGbvMtKrG_eDbQ4RsHCqTzdzrj=cQ=D+wbiL5ct23ay7avg@mail.gmail.com>

Hi ALL

We just started it. It will help us to test our library and find some bugs.

-- Passos

On Wed, Oct 15, 2014 at 4:42 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, Oct 6, 2014 at 3:27 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>  On 10/06/2014 05:45 AM, Corinne Krych wrote:
>>
>> Hello Guys,
>>
>>  Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we
>> worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a
>> backend to demo Keycloak too.
>>
>>  Main idea is that for OAuth2 we demo external providers: Google,
>> Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it
>> with a web-app too. So that?s once the photo get uploaded you can view on
>> desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js
>> adapter). See backend demo [1]
>>
>>  @summers, passos: It would be nice to have an Android similar demo,
>> wdyt?
>>
>> Shouldn't be a problem :)  More demos are always fun and will be a good
>> thing to give the 2.0 code a in use test.
>>
>
> as a happy user of iOS' Share-n-Shoot, I fully agree. Having such an
> Android app would be nice!
> Also, good point, this app would be a good test for the 2.0 code line!
>
> I have file a feature request for this to track it fure 2.0.x development:
> https://issues.jboss.org/browse/AGDROID-301
>
> Greetings,
> Matthias
>
>
>>  @lfryc @lholmquist should we use keyclaok.js only or is there a way to
>> use ag.js? btw, your review is welcome on the js-angular part.
>>
>>  ++
>> Corinne
>>
>>  [1]
>> https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
>>
>>  PS: do you like kittens?
>>
>>
>> _______________________________________________
>> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Summers Pittman
>> >>Phone:404 941 4698
>> >>Java is my crack.
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141015/814596f4/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 111801 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141015/814596f4/attachment-0001.png 

From corinnekrych at gmail.com  Wed Oct 15 12:06:38 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Wed, 15 Oct 2014 18:06:38 +0200
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <CAKjsGbvMtKrG_eDbQ4RsHCqTzdzrj=cQ=D+wbiL5ct23ay7avg@mail.gmail.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
	<543298AF.7060201@redhat.com>
	<CAAg5f2Tf-8rfh5x+jEUOiTMVQ_4-i8H=ZnF4cU2aRRp9QOfdXA@mail.gmail.com>
	<CAKjsGbvMtKrG_eDbQ4RsHCqTzdzrj=cQ=D+wbiL5ct23ay7avg@mail.gmail.com>
Message-ID: <CAL8vO=cXMrR8j-V+TLme567RtCnP4Z87XkU5iqxZ+cSGuGDc8A@mail.gmail.com>

Cool !

On 15 October 2014 17:34, Daniel Passos <daniel at passos.me> wrote:

> Hi ALL
>
> We just started it. It will help us to test our library and find some bugs.
>
> -- Passos
>
> On Wed, Oct 15, 2014 at 4:42 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Mon, Oct 6, 2014 at 3:27 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>  On 10/06/2014 05:45 AM, Corinne Krych wrote:
>>>
>>> Hello Guys,
>>>
>>>  Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we
>>> worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a
>>> backend to demo Keycloak too.
>>>
>>>  Main idea is that for OAuth2 we demo external providers: Google,
>>> Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it
>>> with a web-app too. So that?s once the photo get uploaded you can view on
>>> desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js
>>> adapter). See backend demo [1]
>>>
>>>  @summers, passos: It would be nice to have an Android similar demo,
>>> wdyt?
>>>
>>> Shouldn't be a problem :)  More demos are always fun and will be a good
>>> thing to give the 2.0 code a in use test.
>>>
>>
>> as a happy user of iOS' Share-n-Shoot, I fully agree. Having such an
>> Android app would be nice!
>> Also, good point, this app would be a good test for the 2.0 code line!
>>
>> I have file a feature request for this to track it fure 2.0.x development:
>> https://issues.jboss.org/browse/AGDROID-301
>>
>> Greetings,
>> Matthias
>>
>>
>>>  @lfryc @lholmquist should we use keyclaok.js only or is there a way to
>>> use ag.js? btw, your review is welcome on the js-angular part.
>>>
>>>  ++
>>> Corinne
>>>
>>>  [1]
>>> https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
>>>
>>>  PS: do you like kittens?
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> --
>>> Summers Pittman
>>> >>Phone:404 941 4698
>>> >>Java is my crack.
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20141015/f793b8ca/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 111801 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141015/f793b8ca/attachment-0001.png 

From matzew at apache.org  Wed Oct 15 16:59:17 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 15 Oct 2014 22:59:17 +0200
Subject: [aerogear-dev] OAuth2 demo app, let's use Shoot'nShare!
In-Reply-To: <CAKjsGbvMtKrG_eDbQ4RsHCqTzdzrj=cQ=D+wbiL5ct23ay7avg@mail.gmail.com>
References: <7CCFBF1F-247C-4400-A42A-7DEE568B86E6@gmail.com>
	<543298AF.7060201@redhat.com>
	<CAAg5f2Tf-8rfh5x+jEUOiTMVQ_4-i8H=ZnF4cU2aRRp9QOfdXA@mail.gmail.com>
	<CAKjsGbvMtKrG_eDbQ4RsHCqTzdzrj=cQ=D+wbiL5ct23ay7avg@mail.gmail.com>
Message-ID: <CAAg5f2TrBzJaY1VC0Q1xtRdZwEnET5GCZ=VEs4=Kw6RhbPUeRg@mail.gmail.com>

On Wed, Oct 15, 2014 at 5:34 PM, Daniel Passos <daniel at passos.me> wrote:

> Hi ALL
>
> We just started it. It will help us to test our library and find some bugs.
>

perfect! please include me on PRs for review and testing :)


>
> -- Passos
>
> On Wed, Oct 15, 2014 at 4:42 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Mon, Oct 6, 2014 at 3:27 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>  On 10/06/2014 05:45 AM, Corinne Krych wrote:
>>>
>>> Hello Guys,
>>>
>>>  Aerogear iOS 2.0 release main focus being on OAuth2, this relase, we
>>> worked on an OAuth2 demo. We actually reuse Shoot app and extend it with a
>>> backend to demo Keycloak too.
>>>
>>>  Main idea is that for OAuth2 we demo external providers: Google,
>>> Facebook (and Twitter should come next)  and Keycloak. We?ve enhanced it
>>> with a web-app too. So that?s once the photo get uploaded you can view on
>>> desktop web-app. It?s nice to demo the 2 keyclaok adapters (wildfly and js
>>> adapter). See backend demo [1]
>>>
>>>  @summers, passos: It would be nice to have an Android similar demo,
>>> wdyt?
>>>
>>> Shouldn't be a problem :)  More demos are always fun and will be a good
>>> thing to give the 2.0 code a in use test.
>>>
>>
>> as a happy user of iOS' Share-n-Shoot, I fully agree. Having such an
>> Android app would be nice!
>> Also, good point, this app would be a good test for the 2.0 code line!
>>
>> I have file a feature request for this to track it fure 2.0.x development:
>> https://issues.jboss.org/browse/AGDROID-301
>>
>> Greetings,
>> Matthias
>>
>>
>>>  @lfryc @lholmquist should we use keyclaok.js only or is there a way to
>>> use ag.js? btw, your review is welcome on the js-angular part.
>>>
>>>  ++
>>> Corinne
>>>
>>>  [1]
>>> https://github.com/corinnekrych/aerogear-backend-cookbook/blob/master/Shoot/README.md
>>>
>>>  PS: do you like kittens?
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> --
>>> Summers Pittman
>>> >>Phone:404 941 4698
>>> >>Java is my crack.
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141015/bf9ca04b/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 111801 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141015/bf9ca04b/attachment-0001.png 

From corinnekrych at gmail.com  Thu Oct 16 02:32:55 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 16 Oct 2014 08:32:55 +0200
Subject: [aerogear-dev] iOS AeroGear 1.6.1 is out!
Message-ID: <4F4447E7-F0DD-4EC4-AEE1-F1715B416098@gmail.com>

Hello iOS lovers,
 
We're glad to announce that AeroGear-iOS 1.6.1 is out. 
This minor release is mainly about upgrading and supporting iOS8 with Xcode 6. See JIRA tickets [1]. This release is the last one in 1.x series, next release will be 2.0.0.
 
You can use either Xcode5 or the latest Xcode 6.1 to compile your code using AseroGear-iOS 1.6.1 libs. The Xcode template to generate your project can be used with Xcode 5.1 or with Xcode6.1. 
 
Enjoy and let us know how you like it :)
 
++
Corinne && Christos
[1] https://issues.jboss.org/browse/AGIOS-281?jql=fixVersion%20%3D%201.6.1%20AND%20project%20%3D%20AGIOS

 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/dda19fa9/attachment.bin 

From matzew at apache.org  Thu Oct 16 03:52:27 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 16 Oct 2014 09:52:27 +0200
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
Message-ID: <CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>

looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but we
do have a 0.2.8 tag
https://github.com/aerogear/aerogear-parent/blob/master/pom.xml

Noticed when I wanted to merge
https://github.com/aerogear/aerogear-parent/pull/28

You mind pushing the master changes, from the release plugin ?



On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:

> Hi,
>
> I?d like to run a new release of our parent/bom.
>
> Here is some changes related to newer versions:
>
>    - AEROGEAR-1526 - Update Android Support library version
>    <https://issues.jboss.org/browse/AEROGEAR-1526>
>    - AEROGEAR-1525 - Remove unnecessary dependencies
>    <https://issues.jboss.org/browse/AEROGEAR-1525>
>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
>    library from Maven SDK deploy
>    <https://issues.jboss.org/browse/AEROGEAR-1524>
>    - AEROGEAR-1527 - Move gcm server and json simple from android bom to
>    bom <https://issues.jboss.org/browse/AEROGEAR-1527>
>
> Feel free to test it. I have plan to release it next thursday.
>
> The staging repo is here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
>
> ? Passos
> ?
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From daniel at passos.me  Thu Oct 16 06:08:19 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 16 Oct 2014 07:08:19 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
Message-ID: <CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>

Hi Matthias,

Of course, not sure if it's the correct but in my flow I only push it to
repo, after release it, so, we can revert it or add something like this[1]
without dirtying the repository

I have 2 questions

1) Should I push it when I stage a version?

2) Should I add this[1] in 0.2.8 version?

[1] https://github.com/aerogear/aerogear-parent/pull/28

-- Passos


On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but we
> do have a 0.2.8 tag
> https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
>
> Noticed when I wanted to merge
> https://github.com/aerogear/aerogear-parent/pull/28
>
> You mind pushing the master changes, from the release plugin ?
>
>
>
> On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:
>
>> Hi,
>>
>> I?d like to run a new release of our parent/bom.
>>
>> Here is some changes related to newer versions:
>>
>>    - AEROGEAR-1526 - Update Android Support library version
>>    <https://issues.jboss.org/browse/AEROGEAR-1526>
>>    - AEROGEAR-1525 - Remove unnecessary dependencies
>>    <https://issues.jboss.org/browse/AEROGEAR-1525>
>>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
>>    library from Maven SDK deploy
>>    <https://issues.jboss.org/browse/AEROGEAR-1524>
>>    - AEROGEAR-1527 - Move gcm server and json simple from android bom to
>>    bom <https://issues.jboss.org/browse/AEROGEAR-1527>
>>
>> Feel free to test it. I have plan to release it next thursday.
>>
>> The staging repo is here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
>>
>> ? Passos
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/1226c734/attachment.html 

From matzew at apache.org  Thu Oct 16 06:10:51 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 16 Oct 2014 12:10:51 +0200
Subject: [aerogear-dev] roadmap - OAuth2 work
Message-ID: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>

Hello team!

While the Android and iOS team working on OAuth2 libraries and demos, the
next logical victim for a wider OAuth2 support would be our Apache Cordova
project!

I see it's part of our Cordova roadmap ([1]), but I think it should not be
nested underneath OTP. Instead we should have an "AeroGear Cordova OAuth2"
repo/project, which ships an OAuth2 plugin, leveraging the native
Android/iOS libraries. For the demo, to me, it sounds like it would be good
to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
Keycloak) as well.

Not sure exactly on the timing for this, but I think once the Android and
iOS teams agree their libraries are in a solid state*, it would be a good
time to rethink the roadmap regarding OAuth2 and our Apache Cordova project.

Any thoughts?

-Matthias

* The Android team is currently working on an Android version of
"Shoot-n-Share" to test the library and finding potential bugs.


[1]
http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
[2] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html


-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 16 06:14:10 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 16 Oct 2014 12:14:10 +0200
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
Message-ID: <CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>

On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me> wrote:

> Hi Matthias,
>
> Of course, not sure if it's the correct but in my flow I only push it to
> repo, after release it, so, we can revert it or add something like this[1]
> without dirtying the repository
>

perhaps we than should change the flow here:
https://github.com/aerogear/collateral/wiki/Release-Process-(Java)


>
> I have 2 questions
>
> 1) Should I push it when I stage a version?
>

That's what the guide says. I didn't write it, but I think if we need to,
we can always 're-think' rules :) we are flexible :)


>
> 2) Should I add this[1] in 0.2.8 version?
>

Oh, yah! that would be eggxtremely nice :-)

-M



>
> [1] https://github.com/aerogear/aerogear-parent/pull/28
>
> -- Passos
>
>
> On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but we
>> do have a 0.2.8 tag
>> https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
>>
>> Noticed when I wanted to merge
>> https://github.com/aerogear/aerogear-parent/pull/28
>>
>> You mind pushing the master changes, from the release plugin ?
>>
>>
>>
>> On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:
>>
>>> Hi,
>>>
>>> I?d like to run a new release of our parent/bom.
>>>
>>> Here is some changes related to newer versions:
>>>
>>>    - AEROGEAR-1526 - Update Android Support library version
>>>    <https://issues.jboss.org/browse/AEROGEAR-1526>
>>>    - AEROGEAR-1525 - Remove unnecessary dependencies
>>>    <https://issues.jboss.org/browse/AEROGEAR-1525>
>>>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
>>>    library from Maven SDK deploy
>>>    <https://issues.jboss.org/browse/AEROGEAR-1524>
>>>    - AEROGEAR-1527 - Move gcm server and json simple from android bom
>>>    to bom <https://issues.jboss.org/browse/AEROGEAR-1527>
>>>
>>> Feel free to test it. I have plan to release it next thursday.
>>>
>>> The staging repo is here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
>>>
>>> ? Passos
>>>
>>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From daniel at passos.me  Thu Oct 16 06:28:18 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 16 Oct 2014 07:28:18 -0300
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
Message-ID: <CAKjsGbsUdFsLVPAsP8jsen3UfPPBmzwKZ+QLOzGCN3p6SQofuQ@mail.gmail.com>

+1

On Thu, Oct 16, 2014 at 7:10 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello team!
>
> While the Android and iOS team working on OAuth2 libraries and demos, the
> next logical victim for a wider OAuth2 support would be our Apache Cordova
> project!
>
> I see it's part of our Cordova roadmap ([1]), but I think it should not be
> nested underneath OTP. Instead we should have an "AeroGear Cordova OAuth2"
> repo/project, which ships an OAuth2 plugin, leveraging the native
> Android/iOS libraries. For the demo, to me, it sounds like it would be good
> to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
> Keycloak) as well.
>
> Not sure exactly on the timing for this, but I think once the Android and
> iOS teams agree their libraries are in a solid state*, it would be a good
> time to rethink the roadmap regarding OAuth2 and our Apache Cordova project.
>
> Any thoughts?
>
> -Matthias
>
> * The Android team is currently working on an Android version of
> "Shoot-n-Share" to test the library and finding potential bugs.
>
>
> [1]
> http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
> [2] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/19935fa7/attachment.html 

From daniel.bevenius at gmail.com  Thu Oct 16 06:34:21 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Thu, 16 Oct 2014 12:34:21 +0200
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
Message-ID: <CAFJm-3EhaTjjL6hcBh84qt4tHiFu6b62=oeM3kGppHaFGhkozg@mail.gmail.com>

+1

On 16 October 2014 12:10, Matthias Wessendorf <matzew at apache.org> wrote:

> Hello team!
>
> While the Android and iOS team working on OAuth2 libraries and demos, the
> next logical victim for a wider OAuth2 support would be our Apache Cordova
> project!
>
> I see it's part of our Cordova roadmap ([1]), but I think it should not be
> nested underneath OTP. Instead we should have an "AeroGear Cordova OAuth2"
> repo/project, which ships an OAuth2 plugin, leveraging the native
> Android/iOS libraries. For the demo, to me, it sounds like it would be good
> to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
> Keycloak) as well.
>
> Not sure exactly on the timing for this, but I think once the Android and
> iOS teams agree their libraries are in a solid state*, it would be a good
> time to rethink the roadmap regarding OAuth2 and our Apache Cordova project.
>
> Any thoughts?
>
> -Matthias
>
> * The Android team is currently working on an Android version of
> "Shoot-n-Share" to test the library and finding potential bugs.
>
>
> [1]
> http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
> [2] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/84d785b0/attachment.html 

From daniel at passos.me  Thu Oct 16 06:39:36 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 16 Oct 2014 07:39:36 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
Message-ID: <CAKjsGbsy+cw9NTskJ3BJTkmO6DwKXE7J7cLjHcVHUjq0M-S9Bg@mail.gmail.com>

On Thu, Oct 16, 2014 at 7:14 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me> wrote:
>
>> Hi Matthias,
>>
>> Of course, not sure if it's the correct but in my flow I only push it to
>> repo, after release it, so, we can revert it or add something like this[1]
>> without dirtying the repository
>>
>
> perhaps we than should change the flow here:
> https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
>
>
>>
>> I have 2 questions
>>
>> 1) Should I push it when I stage a version?
>>
>
> That's what the guide says. I didn't write it, but I think if we need to,
> we can always 're-think' rules :) we are flexible :)
>

If team agrees with this flow, I update the doc


> 2) Should I add this[1] in 0.2.8 version?
>>
>
> Oh, yah! that would be eggxtremely nice :-)
>

I'm on it.


>
> -M
>
>>
>> [1] https://github.com/aerogear/aerogear-parent/pull/28
>>
>> -- Passos
>>
>>
>> On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but
>>> we do have a 0.2.8 tag
>>> https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
>>>
>>> Noticed when I wanted to merge
>>> https://github.com/aerogear/aerogear-parent/pull/28
>>>
>>> You mind pushing the master changes, from the release plugin ?
>>>
>>>
>>>
>>> On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:
>>>
>>>> Hi,
>>>>
>>>> I?d like to run a new release of our parent/bom.
>>>>
>>>> Here is some changes related to newer versions:
>>>>
>>>>    - AEROGEAR-1526 - Update Android Support library version
>>>>    <https://issues.jboss.org/browse/AEROGEAR-1526>
>>>>    - AEROGEAR-1525 - Remove unnecessary dependencies
>>>>    <https://issues.jboss.org/browse/AEROGEAR-1525>
>>>>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
>>>>    library from Maven SDK deploy
>>>>    <https://issues.jboss.org/browse/AEROGEAR-1524>
>>>>    - AEROGEAR-1527 - Move gcm server and json simple from android bom
>>>>    to bom <https://issues.jboss.org/browse/AEROGEAR-1527>
>>>>
>>>> Feel free to test it. I have plan to release it next thursday.
>>>>
>>>> The staging repo is here:
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
>>>>
>>>> ? Passos
>>>>
>>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/2f9644b9/attachment.html 

From daniel at passos.me  Thu Oct 16 06:49:48 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 16 Oct 2014 07:49:48 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAKjsGbsy+cw9NTskJ3BJTkmO6DwKXE7J7cLjHcVHUjq0M-S9Bg@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
	<CAKjsGbsy+cw9NTskJ3BJTkmO6DwKXE7J7cLjHcVHUjq0M-S9Bg@mail.gmail.com>
Message-ID: <CAKjsGbsE9c5f6LQEiPNeoMW3hU1BD7=N4vbS7nJPowESEPoppw@mail.gmail.com>

Hi ALL,

I just stage it again to include this[1]

The staging repo is here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4031/

Feel free test it and let me know about the release by Friday, so we can
upload the bits to maven central over the weekend.

[1] https://github.com/aerogear/aerogear-parent/pull/28

-- Passos


On Thu, Oct 16, 2014 at 7:39 AM, Daniel Passos <daniel at passos.me> wrote:

>
>
> On Thu, Oct 16, 2014 at 7:14 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me> wrote:
>>
>>> Hi Matthias,
>>>
>>> Of course, not sure if it's the correct but in my flow I only push it to
>>> repo, after release it, so, we can revert it or add something like this[1]
>>> without dirtying the repository
>>>
>>
>> perhaps we than should change the flow here:
>> https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
>>
>>
>>>
>>> I have 2 questions
>>>
>>> 1) Should I push it when I stage a version?
>>>
>>
>> That's what the guide says. I didn't write it, but I think if we need to,
>> we can always 're-think' rules :) we are flexible :)
>>
>
> If team agrees with this flow, I update the doc
>
>
>> 2) Should I add this[1] in 0.2.8 version?
>>>
>>
>> Oh, yah! that would be eggxtremely nice :-)
>>
>
> I'm on it.
>
>
>>
>> -M
>>
>>>
>>> [1] https://github.com/aerogear/aerogear-parent/pull/28
>>>
>>> -- Passos
>>>
>>>
>>> On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but
>>>> we do have a 0.2.8 tag
>>>> https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
>>>>
>>>> Noticed when I wanted to merge
>>>> https://github.com/aerogear/aerogear-parent/pull/28
>>>>
>>>> You mind pushing the master changes, from the release plugin ?
>>>>
>>>>
>>>>
>>>> On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I?d like to run a new release of our parent/bom.
>>>>>
>>>>> Here is some changes related to newer versions:
>>>>>
>>>>>    - AEROGEAR-1526 - Update Android Support library version
>>>>>    <https://issues.jboss.org/browse/AEROGEAR-1526>
>>>>>    - AEROGEAR-1525 - Remove unnecessary dependencies
>>>>>    <https://issues.jboss.org/browse/AEROGEAR-1525>
>>>>>    - AEROGEAR-1524 - Change Android Maven Central stub to real
>>>>>    Android library from Maven SDK deploy
>>>>>    <https://issues.jboss.org/browse/AEROGEAR-1524>
>>>>>    - AEROGEAR-1527 - Move gcm server and json simple from android bom
>>>>>    to bom <https://issues.jboss.org/browse/AEROGEAR-1527>
>>>>>
>>>>> Feel free to test it. I have plan to release it next thursday.
>>>>>
>>>>> The staging repo is here:
>>>>>
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
>>>>>
>>>>> ? Passos
>>>>>
>>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/b7b0ea73/attachment-0001.html 

From bruno at abstractj.org  Thu Oct 16 06:50:51 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 16 Oct 2014 07:50:51 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
Message-ID: <20141016105051.GA93240@abstractj.org>

On 2014-10-16, Daniel Passos wrote:
> Hi Matthias,
>
> Of course, not sure if it's the correct but in my flow I only push it to
> repo, after release it, so, we can revert it or add something like this[1]
> without dirtying the repository
>
> I have 2 questions
>
> 1) Should I push it when I stage a version?

I don't think so. Part of our release process is: push the tag first,
stage and after release, push the changes -
https://github.com/aerogear/collateral/wiki/Release-Process-(Java)

It make the process easy to revert changes, if something goes wrong you
just need to cancel the release and delete the tag.

>
> 2) Should I add this[1] in 0.2.8 version?
>
> [1] https://github.com/aerogear/aerogear-parent/pull/28

I think this is pretty much coordinated with the team, once you start
the release process, no more changes should be added until we release
and push the commits related to it.

>
> -- Passos
>
>
> On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> > looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but we
> > do have a 0.2.8 tag
> > https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
> >
> > Noticed when I wanted to merge
> > https://github.com/aerogear/aerogear-parent/pull/28
> >
> > You mind pushing the master changes, from the release plugin ?
> >
> >
> >
> > On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:
> >
> >> Hi,
> >>
> >> I?d like to run a new release of our parent/bom.
> >>
> >> Here is some changes related to newer versions:
> >>
> >>    - AEROGEAR-1526 - Update Android Support library version
> >>    <https://issues.jboss.org/browse/AEROGEAR-1526>
> >>    - AEROGEAR-1525 - Remove unnecessary dependencies
> >>    <https://issues.jboss.org/browse/AEROGEAR-1525>
> >>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
> >>    library from Maven SDK deploy
> >>    <https://issues.jboss.org/browse/AEROGEAR-1524>
> >>    - AEROGEAR-1527 - Move gcm server and json simple from android bom to
> >>    bom <https://issues.jboss.org/browse/AEROGEAR-1527>
> >>
> >> Feel free to test it. I have plan to release it next thursday.
> >>
> >> The staging repo is here:
> >>
> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
> >>
> >> ? Passos
> >>
> >

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct 16 06:52:00 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 16 Oct 2014 07:52:00 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
Message-ID: <20141016105200.GB93240@abstractj.org>

On 2014-10-16, Matthias Wessendorf wrote:
> On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me> wrote:
>
> > Hi Matthias,
> >
> > Of course, not sure if it's the correct but in my flow I only push it to
> > repo, after release it, so, we can revert it or add something like this[1]
> > without dirtying the repository
> >
>
> perhaps we than should change the flow here:
> https://github.com/aerogear/collateral/wiki/Release-Process-(Java)

To me, this is a bad idea. If you change the flow and something is
messed up, our repositories will end up with a lot of reverts.

>
>
> >
> > I have 2 questions
> >
> > 1) Should I push it when I stage a version?
> >
>
> That's what the guide says. I didn't write it, but I think if we need to,
> we can always 're-think' rules :) we are flexible :)
>
>
> >
> > 2) Should I add this[1] in 0.2.8 version?
> >
>
> Oh, yah! that would be eggxtremely nice :-)
>
> -M
>
>
>
> >
> > [1] https://github.com/aerogear/aerogear-parent/pull/28
> >
> > -- Passos
> >
> >
> > On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> >> looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but we
> >> do have a 0.2.8 tag
> >> https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
> >>
> >> Noticed when I wanted to merge
> >> https://github.com/aerogear/aerogear-parent/pull/28
> >>
> >> You mind pushing the master changes, from the release plugin ?
> >>
> >>
> >>
> >> On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:
> >>
> >>> Hi,
> >>>
> >>> I?d like to run a new release of our parent/bom.
> >>>
> >>> Here is some changes related to newer versions:
> >>>
> >>>    - AEROGEAR-1526 - Update Android Support library version
> >>>    <https://issues.jboss.org/browse/AEROGEAR-1526>
> >>>    - AEROGEAR-1525 - Remove unnecessary dependencies
> >>>    <https://issues.jboss.org/browse/AEROGEAR-1525>
> >>>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
> >>>    library from Maven SDK deploy
> >>>    <https://issues.jboss.org/browse/AEROGEAR-1524>
> >>>    - AEROGEAR-1527 - Move gcm server and json simple from android bom
> >>>    to bom <https://issues.jboss.org/browse/AEROGEAR-1527>
> >>>
> >>> Feel free to test it. I have plan to release it next thursday.
> >>>
> >>> The staging repo is here:
> >>>
> >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
> >>>
> >>> ? Passos
> >>>
> >>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct 16 06:52:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 16 Oct 2014 07:52:32 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAKjsGbsy+cw9NTskJ3BJTkmO6DwKXE7J7cLjHcVHUjq0M-S9Bg@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
	<CAKjsGbsy+cw9NTskJ3BJTkmO6DwKXE7J7cLjHcVHUjq0M-S9Bg@mail.gmail.com>
Message-ID: <20141016105232.GC93240@abstractj.org>

On 2014-10-16, Daniel Passos wrote:
> On Thu, Oct 16, 2014 at 7:14 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> >
> >
> > On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me> wrote:
> >
> >> Hi Matthias,
> >>
> >> Of course, not sure if it's the correct but in my flow I only push it to
> >> repo, after release it, so, we can revert it or add something like this[1]
> >> without dirtying the repository
> >>
> >
> > perhaps we than should change the flow here:
> > https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
> >
> >
> >>
> >> I have 2 questions
> >>
> >> 1) Should I push it when I stage a version?
> >>
> >
> > That's what the guide says. I didn't write it, but I think if we need to,
> > we can always 're-think' rules :) we are flexible :)
> >
>
> If team agrees with this flow, I update the doc

-1

>
>
> > 2) Should I add this[1] in 0.2.8 version?
> >>
> >
> > Oh, yah! that would be eggxtremely nice :-)
> >
>
> I'm on it.
>
>
> >
> > -M
> >
> >>
> >> [1] https://github.com/aerogear/aerogear-parent/pull/28
> >>
> >> -- Passos
> >>
> >>
> >> On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
> >> wrote:
> >>
> >>> looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but
> >>> we do have a 0.2.8 tag
> >>> https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
> >>>
> >>> Noticed when I wanted to merge
> >>> https://github.com/aerogear/aerogear-parent/pull/28
> >>>
> >>> You mind pushing the master changes, from the release plugin ?
> >>>
> >>>
> >>>
> >>> On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> I?d like to run a new release of our parent/bom.
> >>>>
> >>>> Here is some changes related to newer versions:
> >>>>
> >>>>    - AEROGEAR-1526 - Update Android Support library version
> >>>>    <https://issues.jboss.org/browse/AEROGEAR-1526>
> >>>>    - AEROGEAR-1525 - Remove unnecessary dependencies
> >>>>    <https://issues.jboss.org/browse/AEROGEAR-1525>
> >>>>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
> >>>>    library from Maven SDK deploy
> >>>>    <https://issues.jboss.org/browse/AEROGEAR-1524>
> >>>>    - AEROGEAR-1527 - Move gcm server and json simple from android bom
> >>>>    to bom <https://issues.jboss.org/browse/AEROGEAR-1527>
> >>>>
> >>>> Feel free to test it. I have plan to release it next thursday.
> >>>>
> >>>> The staging repo is here:
> >>>>
> >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
> >>>>
> >>>> ? Passos
> >>>>
> >>>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Thu Oct 16 06:58:22 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 16 Oct 2014 07:58:22 -0300
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
Message-ID: <20141016105822.GD93240@abstractj.org>

Hi Matthias, I'm reviewing ALL the bits related to OAuth2 into our
project, including Cordova, please see
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Security-Meeting-minutes-td9339.html

The Jira for tracking the work is:
https://issues.jboss.org/browse/AGSEC-180

On 2014-10-16, Matthias Wessendorf wrote:
> Hello team!
>
> While the Android and iOS team working on OAuth2 libraries and demos, the
> next logical victim for a wider OAuth2 support would be our Apache Cordova
> project!
>
> I see it's part of our Cordova roadmap ([1]), but I think it should not be
> nested underneath OTP. Instead we should have an "AeroGear Cordova OAuth2"
> repo/project, which ships an OAuth2 plugin, leveraging the native
> Android/iOS libraries. For the demo, to me, it sounds like it would be good
> to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
> Keycloak) as well.
>
> Not sure exactly on the timing for this, but I think once the Android and
> iOS teams agree their libraries are in a solid state*, it would be a good
> time to rethink the roadmap regarding OAuth2 and our Apache Cordova project.
>
> Any thoughts?
>
> -Matthias
>
> * The Android team is currently working on an Android version of
> "Shoot-n-Share" to test the library and finding potential bugs.
>
>
> [1]
> http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
> [2] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Thu Oct 16 06:59:40 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 16 Oct 2014 12:59:40 +0200
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <20141016105051.GA93240@abstractj.org>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<20141016105051.GA93240@abstractj.org>
Message-ID: <CAAg5f2RAt3Wf3W8FVj4ovs5FDYBDK5SuF=KHkemSiujnoh8XBg@mail.gmail.com>

On Thu, Oct 16, 2014 at 12:50 PM, Bruno Oliveira <bruno at abstractj.org>
wrote:

> On 2014-10-16, Daniel Passos wrote:
> > Hi Matthias,
> >
> > Of course, not sure if it's the correct but in my flow I only push it to
> > repo, after release it, so, we can revert it or add something like
> this[1]
> > without dirtying the repository
> >
> > I have 2 questions
> >
> > 1) Should I push it when I stage a version?
>
> I don't think so. Part of our release process is: push the tag first,
> stage and after release, push the changes -
> https://github.com/aerogear/collateral/wiki/Release-Process-(Java)


yeah, there is this recommendation:

====
*Note 2:* You only want to do this once your staging time has ended and
tests have been successful.
====

In the past I pushed the version update to master, before staging, after
the "mvn release:perform" has been executed successful.

But yeah, in case something would have gone wrong, during the stating
period, I'd have needed to revert that :)

I think the current process, with the above recommendation, works well for
us

-M


>
>
> It make the process easy to revert changes, if something goes wrong you
> just need to cancel the release and delete the tag.
>
> >
> > 2) Should I add this[1] in 0.2.8 version?
> >
> > [1] https://github.com/aerogear/aerogear-parent/pull/28
>
> I think this is pretty much coordinated with the team, once you start
> the release process, no more changes should be added until we release
> and push the commits related to it.
>
> >
> > -- Passos
> >
> >
> > On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> > > looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but
> we
> > > do have a 0.2.8 tag
> > > https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
> > >
> > > Noticed when I wanted to merge
> > > https://github.com/aerogear/aerogear-parent/pull/28
> > >
> > > You mind pushing the master changes, from the release plugin ?
> > >
> > >
> > >
> > > On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel at passos.me>
> wrote:
> > >
> > >> Hi,
> > >>
> > >> I?d like to run a new release of our parent/bom.
> > >>
> > >> Here is some changes related to newer versions:
> > >>
> > >>    - AEROGEAR-1526 - Update Android Support library version
> > >>    <https://issues.jboss.org/browse/AEROGEAR-1526>
> > >>    - AEROGEAR-1525 - Remove unnecessary dependencies
> > >>    <https://issues.jboss.org/browse/AEROGEAR-1525>
> > >>    - AEROGEAR-1524 - Change Android Maven Central stub to real Android
> > >>    library from Maven SDK deploy
> > >>    <https://issues.jboss.org/browse/AEROGEAR-1524>
> > >>    - AEROGEAR-1527 - Move gcm server and json simple from android bom
> to
> > >>    bom <https://issues.jboss.org/browse/AEROGEAR-1527>
> > >>
> > >> Feel free to test it. I have plan to release it next thursday.
> > >>
> > >> The staging repo is here:
> > >>
> > >>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/
> > >>
> > >> ? Passos
> > >>
> > >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 16 07:10:27 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 16 Oct 2014 13:10:27 +0200
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <20141016105822.GD93240@abstractj.org>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
	<20141016105822.GD93240@abstractj.org>
Message-ID: <CAAg5f2Tp996+yfALGmC83WhG-C0sxEfoCb75boi8OL0NPknELA@mail.gmail.com>

Perfect!

just added an epic for OAuth2 on AGCORDOVA and linked it to AGSEC-180 ([1]).

[1] https://issues.jboss.org/browse/AGCORDOVA-35


On Thu, Oct 16, 2014 at 12:58 PM, Bruno Oliveira <bruno at abstractj.org>
wrote:

> Hi Matthias, I'm reviewing ALL the bits related to OAuth2 into our
> project, including Cordova, please see
>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Security-Meeting-minutes-td9339.html
>
> The Jira for tracking the work is:
> https://issues.jboss.org/browse/AGSEC-180
>
> On 2014-10-16, Matthias Wessendorf wrote:
> > Hello team!
> >
> > While the Android and iOS team working on OAuth2 libraries and demos, the
> > next logical victim for a wider OAuth2 support would be our Apache
> Cordova
> > project!
> >
> > I see it's part of our Cordova roadmap ([1]), but I think it should not
> be
> > nested underneath OTP. Instead we should have an "AeroGear Cordova
> OAuth2"
> > repo/project, which ships an OAuth2 plugin, leveraging the native
> > Android/iOS libraries. For the demo, to me, it sounds like it would be
> good
> > to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
> > Keycloak) as well.
> >
> > Not sure exactly on the timing for this, but I think once the Android and
> > iOS teams agree their libraries are in a solid state*, it would be a good
> > time to rethink the roadmap regarding OAuth2 and our Apache Cordova
> project.
> >
> > Any thoughts?
> >
> > -Matthias
> >
> > * The Android team is currently working on an Android version of
> > "Shoot-n-Share" to test the library and finding potential bugs.
> >
> >
> > [1]
> >
> http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
> > [2]
> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Thu Oct 16 07:13:37 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 16 Oct 2014 13:13:37 +0200
Subject: [aerogear-dev] [CORDOVA] Push Plugin and branches
Message-ID: <CAD_dpu0DLV1AEBBMaPZvrXRuqhBDBSkn6VDU6BaYS7tEGgwvoQ@mail.gmail.com>

Hi !

Currently the Push Plugin repo [1] hasn't any branches.
Like UPS, I propose that master point to 1.1 so we will be able to merge
the Windows PR there and that we create a 1.0.x branch that matches the
state of UPS 1.0.x ?

Sounds good ?

Seb

[1] https://github.com/aerogear/aerogear-pushplugin-cordova
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/a7691f84/attachment.html 

From matzew at apache.org  Thu Oct 16 07:15:01 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 16 Oct 2014 13:15:01 +0200
Subject: [aerogear-dev] [CORDOVA] Push Plugin and branches
In-Reply-To: <CAD_dpu0DLV1AEBBMaPZvrXRuqhBDBSkn6VDU6BaYS7tEGgwvoQ@mail.gmail.com>
References: <CAD_dpu0DLV1AEBBMaPZvrXRuqhBDBSkn6VDU6BaYS7tEGgwvoQ@mail.gmail.com>
Message-ID: <CAAg5f2Q9uVUyAJF-ko3KFrY=+sk3i2zoELiq+DhgR+vH1MU0Tg@mail.gmail.com>

On Thu, Oct 16, 2014 at 1:13 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hi !
>
> Currently the Push Plugin repo [1] hasn't any branches.
> Like UPS, I propose that master point to 1.1 so we will be able to merge
> the Windows PR there and that we create a 1.0.x branch that matches the
> state of UPS 1.0.x ?
>

That's fine!


>
> Sounds good ?
>
> Seb
>
> [1] https://github.com/aerogear/aerogear-pushplugin-cordova
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141016/2a0fb761/attachment.html 

From avibelli at redhat.com  Thu Oct 16 07:20:54 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Thu, 16 Oct 2014 04:20:54 -0700 (PDT)
Subject: [aerogear-dev] [CORDOVA] Push Plugin and branches
In-Reply-To: <CAD_dpu0DLV1AEBBMaPZvrXRuqhBDBSkn6VDU6BaYS7tEGgwvoQ@mail.gmail.com>
References: <CAD_dpu0DLV1AEBBMaPZvrXRuqhBDBSkn6VDU6BaYS7tEGgwvoQ@mail.gmail.com>
Message-ID: <1413458454422-9483.post@n5.nabble.com>

Sebastien Blanc wrote
> Hi !
> 
> Currently the Push Plugin repo [1] hasn't any branches.
> Like UPS, I propose that master point to 1.1 so we will be able to merge
> the Windows PR there and that we create a 1.0.x branch that matches the
> state of UPS 1.0.x ?
> 
> Sounds good ?
> 
> Seb
> 
> [1] https://github.com/aerogear/aerogear-pushplugin-cordova
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

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

Sounds excellent!
Andrea




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-CORDOVA-Push-Plugin-and-branches-tp9481p9483.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From bruno at abstractj.org  Thu Oct 16 07:21:33 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 16 Oct 2014 08:21:33 -0300
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <CAAg5f2Tp996+yfALGmC83WhG-C0sxEfoCb75boi8OL0NPknELA@mail.gmail.com>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
	<20141016105822.GD93240@abstractj.org>
	<CAAg5f2Tp996+yfALGmC83WhG-C0sxEfoCb75boi8OL0NPknELA@mail.gmail.com>
Message-ID: <20141016112133.GF93240@abstractj.org>

Thank you

On 2014-10-16, Matthias Wessendorf wrote:
> Perfect!
>
> just added an epic for OAuth2 on AGCORDOVA and linked it to AGSEC-180 ([1]).
>
> [1] https://issues.jboss.org/browse/AGCORDOVA-35
>
>
> On Thu, Oct 16, 2014 at 12:58 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
> > Hi Matthias, I'm reviewing ALL the bits related to OAuth2 into our
> > project, including Cordova, please see
> >
> > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Security-Meeting-minutes-td9339.html
> >
> > The Jira for tracking the work is:
> > https://issues.jboss.org/browse/AGSEC-180
> >
> > On 2014-10-16, Matthias Wessendorf wrote:
> > > Hello team!
> > >
> > > While the Android and iOS team working on OAuth2 libraries and demos, the
> > > next logical victim for a wider OAuth2 support would be our Apache
> > Cordova
> > > project!
> > >
> > > I see it's part of our Cordova roadmap ([1]), but I think it should not
> > be
> > > nested underneath OTP. Instead we should have an "AeroGear Cordova
> > OAuth2"
> > > repo/project, which ships an OAuth2 plugin, leveraging the native
> > > Android/iOS libraries. For the demo, to me, it sounds like it would be
> > good
> > > to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
> > > Keycloak) as well.
> > >
> > > Not sure exactly on the timing for this, but I think once the Android and
> > > iOS teams agree their libraries are in a solid state*, it would be a good
> > > time to rethink the roadmap regarding OAuth2 and our Apache Cordova
> > project.
> > >
> > > Any thoughts?
> > >
> > > -Matthias
> > >
> > > * The Android team is currently working on an Android version of
> > > "Shoot-n-Share" to test the library and finding potential bugs.
> > >
> > >
> > > [1]
> > >
> > http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
> > > [2]
> > http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From corinnekrych at gmail.com  Thu Oct 16 07:42:10 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 16 Oct 2014 13:42:10 +0200
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <20141016112133.GF93240@abstractj.org>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
	<20141016105822.GD93240@abstractj.org>
	<CAAg5f2Tp996+yfALGmC83WhG-C0sxEfoCb75boi8OL0NPknELA@mail.gmail.com>
	<20141016112133.GF93240@abstractj.org>
Message-ID: <8D9AC777-6D7C-4EBC-8B9A-3B4BADEC71A9@gmail.com>

On iOS side aerogear-ios-oauth2 (and its dependent aerogear-ios-http) is ready. 
@edewit let?s sync next week on iOS plugin.
++
Corinne
On 16 Oct 2014, at 13:21, Bruno Oliveira <bruno at abstractj.org> wrote:

> Thank you
> 
> On 2014-10-16, Matthias Wessendorf wrote:
>> Perfect!
>> 
>> just added an epic for OAuth2 on AGCORDOVA and linked it to AGSEC-180 ([1]).
>> 
>> [1] https://issues.jboss.org/browse/AGCORDOVA-35
>> 
>> 
>> On Thu, Oct 16, 2014 at 12:58 PM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>> 
>>> Hi Matthias, I'm reviewing ALL the bits related to OAuth2 into our
>>> project, including Cordova, please see
>>> 
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Security-Meeting-minutes-td9339.html
>>> 
>>> The Jira for tracking the work is:
>>> https://issues.jboss.org/browse/AGSEC-180
>>> 
>>> On 2014-10-16, Matthias Wessendorf wrote:
>>>> Hello team!
>>>> 
>>>> While the Android and iOS team working on OAuth2 libraries and demos, the
>>>> next logical victim for a wider OAuth2 support would be our Apache
>>> Cordova
>>>> project!
>>>> 
>>>> I see it's part of our Cordova roadmap ([1]), but I think it should not
>>> be
>>>> nested underneath OTP. Instead we should have an "AeroGear Cordova
>>> OAuth2"
>>>> repo/project, which ships an OAuth2 plugin, leveraging the native
>>>> Android/iOS libraries. For the demo, to me, it sounds like it would be
>>> good
>>>> to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
>>>> Keycloak) as well.
>>>> 
>>>> Not sure exactly on the timing for this, but I think once the Android and
>>>> iOS teams agree their libraries are in a solid state*, it would be a good
>>>> time to rethink the roadmap regarding OAuth2 and our Apache Cordova
>>> project.
>>>> 
>>>> Any thoughts?
>>>> 
>>>> -Matthias
>>>> 
>>>> * The Android team is currently working on an Android version of
>>>> "Shoot-n-Share" to test the library and finding potential bugs.
>>>> 
>>>> 
>>>> [1]
>>>> 
>>> http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
>>>> [2]
>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
>>>> 
>>>> 
>>>> --
>>>> Matthias Wessendorf
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> --
>>> 
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>> 
>> 
>> 
>> --
>> Matthias Wessendorf
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/9b920935/attachment-0001.bin 

From scm.blanc at gmail.com  Thu Oct 16 08:27:42 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 16 Oct 2014 14:27:42 +0200
Subject: [aerogear-dev] [CORDOVA] Push Plugin and branches
In-Reply-To: <1413458454422-9483.post@n5.nabble.com>
References: <CAD_dpu0DLV1AEBBMaPZvrXRuqhBDBSkn6VDU6BaYS7tEGgwvoQ@mail.gmail.com>
	<1413458454422-9483.post@n5.nabble.com>
Message-ID: <CAD_dpu2Wkd6eQDu43YSiWwtondzzCwTZouqdNvHeMvf4=Qe6SA@mail.gmail.com>

FYI  Branch 1.0.x has been created and master contains now version 1..1.0



On Thu, Oct 16, 2014 at 1:20 PM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Sebastien Blanc wrote
> > Hi !
> >
> > Currently the Push Plugin repo [1] hasn't any branches.
> > Like UPS, I propose that master point to 1.1 so we will be able to merge
> > the Windows PR there and that we create a 1.0.x branch that matches the
> > state of UPS 1.0.x ?
> >
> > Sounds good ?
> >
> > Seb
> >
> > [1] https://github.com/aerogear/aerogear-pushplugin-cordova
> >
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> Sounds excellent!
> Andrea
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-CORDOVA-Push-Plugin-and-branches-tp9481p9483.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/20141016/6959f5bb/attachment.html 

From corinnekrych at gmail.com  Thu Oct 16 15:24:13 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 16 Oct 2014 21:24:13 +0200
Subject: [aerogear-dev] iOS AeroGear 2.0.0 is on its way
Message-ID: <00B13D34-0AC1-4798-BE9F-58437C54569B@gmail.com>

Hello Swift lovers,
 
AeroGear iOS 2.0.0 is coming soon? It?s ready for you to test and it's all in Swift.

But what does it mean for AerGear iOS users?
 
More than just a Swift version, 2.0.0 brings major changes:
- modularization: AeroGear-iOS repo is splitted in several smaller libs. 
- deprecated Pipe: http calls use lean aerogear-ios-http directly built on top of NSURLSession offering a convenient API for accessing RESTful services. [1]
- enhance OAuth2 module with support for Google, Facebook, Keyclaok and a pluggable system to provide support for your own favourite provider. [2]
- backend demo for Keycloak OAuth2 integration. Check out Shoot'nShare demo, read this blog post for more details. [3]
- and Swift based: we've been working on it since Swift birth, last june, we went through updating code base to support latest Xcode6.1 version. Come and share the Swift adventure with us, give it a trial and send us feedback.

++
Corinne && Christos
[1] https://github.com/aerogear/aerogear-ios-http
[2] https://github.com/aerogear/aerogear-ios-oauth2
[3] http://corinnekrych.org/2014/10/aerogear-with-keycloak-oauth2-friends.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141016/45763833/attachment.bin 

From qmx at qmx.me  Thu Oct 16 22:09:40 2014
From: qmx at qmx.me (Douglas Campos)
Date: Thu, 16 Oct 2014 23:09:40 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
Message-ID: <20141017020940.GE71845@darkstar.local>

On Thu, Oct 16, 2014 at 12:14:10PM +0200, Matthias Wessendorf wrote:
> On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me> wrote:
> 
> > Hi Matthias,
> >
> > Of course, not sure if it's the correct but in my flow I only push it to
> > repo, after release it, so, we can revert it or add something like this[1]
> > without dirtying the repository
> >
> 
> perhaps we than should change the flow here:
> https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
-1

Tags are somehow easier to update without leaving a trail of failed
attempts. Once you push to master, it just becomes noise and reverts.

-- 
qmx

From chris.hale at me.com  Fri Oct 17 00:59:32 2014
From: chris.hale at me.com (chale)
Date: Thu, 16 Oct 2014 21:59:32 -0700 (PDT)
Subject: [aerogear-dev] setting up aerogear behind nginx proxy
Message-ID: <1413521972011-9489.post@n5.nabble.com>

Hi,
    I need some help.  I am trying to setup aerogear behind a nginx proxy
server that has ssl enabled and I am running into issues.  Anytime i try to
go to /ag-push I see this in the logs 

RROR [org.apache.catalina.connector.CoyoteAdapter]
(http--10.128.93.235-8080-5) An exception or error occurred in the container
during the request processing: java.lang.RuntimeException: Unable to resolve
realm public key remotely, status = 403
	at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:69)
[keycloak-adapter-core-1.0-final.jar:]
	at
org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:55)
[keycloak-adapter-core-1.0-final.jar:]
	at
org.keycloak.adapters.as7.AuthenticatedActionsValve.invoke(AuthenticatedActionsValve.java:45)
[keycloak-as7-adapter-1.0-final.jar:]
	at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
[jbossweb-7.0.13.Final.jar:]
	at
org.keycloak.adapters.as7.KeycloakAuthenticatorValve.invoke(KeycloakAuthenticatorValve.java:135)
[keycloak-as7-adapter-1.0-final.jar:]
	at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[jbossweb-7.0.13.Final.jar:]
	at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.13.Final.jar:]
	at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.13.Final.jar:]
	at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[jbossweb-7.0.13.Final.jar:]
	at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.13.Final.jar:]
	at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]

Does anyone have any advice or experience on how to go about setting up
aerogear behind an nginx proxy?



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Fri Oct 17 01:29:48 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 17 Oct 2014 07:29:48 +0200
Subject: [aerogear-dev] setting up aerogear behind nginx proxy
In-Reply-To: <1413521972011-9489.post@n5.nabble.com>
References: <1413521972011-9489.post@n5.nabble.com>
Message-ID: <CAAg5f2RadS0+BaAQUsnmTvdDsOOHrmD3eMH=gCfXhy=Et7GO=A@mail.gmail.com>

Hi Chris!

thanks for trying the UnifiedPush Server. I have never tried to run the UPS
behind a (ngnix) proxy. Does the same config work w/o the proxy? The stack
above says "Unable to resolve realm public key remotely", so I am wondering
if the Keycoak Auth-Server is deployed as well.

In the meantime I'll ask our Keycloak friends if they have any experience
on this.

Thanks,
Matthias

On Fri, Oct 17, 2014 at 6:59 AM, chale <chris.hale at me.com> wrote:

> Hi,
>     I need some help.  I am trying to setup aerogear behind a nginx proxy
> server that has ssl enabled and I am running into issues.  Anytime i try to
> go to /ag-push I see this in the logs
>
> RROR [org.apache.catalina.connector.CoyoteAdapter]
> (http--10.128.93.235-8080-5) An exception or error occurred in the
> container
> during the request processing: java.lang.RuntimeException: Unable to
> resolve
> realm public key remotely, status = 403
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:69)
> [keycloak-adapter-core-1.0-final.jar:]
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:55)
> [keycloak-adapter-core-1.0-final.jar:]
>         at
>
> org.keycloak.adapters.as7.AuthenticatedActionsValve.invoke(AuthenticatedActionsValve.java:45)
> [keycloak-as7-adapter-1.0-final.jar:]
>         at
>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.keycloak.adapters.as7.KeycloakAuthenticatorValve.invoke(KeycloakAuthenticatorValve.java:135)
> [keycloak-as7-adapter-1.0-final.jar:]
>         at
>
> org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
> [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
>         at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> [jbossweb-7.0.13.Final.jar:]
>         at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> [jbossweb-7.0.13.Final.jar:]
>         at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
> [jbossweb-7.0.13.Final.jar:]
>         at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
> [jbossweb-7.0.13.Final.jar:]
>         at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
>
> Does anyone have any advice or experience on how to go about setting up
> aerogear behind an nginx proxy?
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489.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/20141017/b19039ce/attachment.html 

From chris.hale at me.com  Fri Oct 17 01:38:36 2014
From: chris.hale at me.com (chale)
Date: Thu, 16 Oct 2014 22:38:36 -0700 (PDT)
Subject: [aerogear-dev] setting up aerogear behind nginx proxy
In-Reply-To: <CAAg5f2RadS0+BaAQUsnmTvdDsOOHrmD3eMH=gCfXhy=Et7GO=A@mail.gmail.com>
References: <1413521972011-9489.post@n5.nabble.com>
	<CAAg5f2RadS0+BaAQUsnmTvdDsOOHrmD3eMH=gCfXhy=Et7GO=A@mail.gmail.com>
Message-ID: <1C9981E0376945CAA8492605D1B1FA7A@me.com>

I am having a little more positive progress and a few more useful things to report from me trying to get this working.  
The logs below aren?t an issue anymore.  Here is how i now have things setup.  

I have nginx setup and running on port 443 and my nginx config looks like this
location / {
        if ($http_user_agent ~ ^$) {
#                return 403;
        }

        proxy_pass http://10.128.93.235:8080/;
        proxy_redirect off;

        proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto "https";
proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
       proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }



I seem to be able to login if i choose http://myserver.com  but if i try and do https://myserver.com/ag-push  

I get a message that is saying we are sorry Invalid redirect_uri. .    

In looking at the http requests I am seeing  
/auth/realms/aerogear/tokens/login url cause a 500

Any way to troubleshoot why its giving a 500?

Thanks in advance,




--  
Chris Hale
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Friday, October 17, 2014 at 12:31 AM, Matthias Wessendorf [via aerogear-dev] wrote:

> Hi Chris!
>  
> thanks for trying the UnifiedPush Server. I have never tried to run the UPS behind a (ngnix) proxy. Does the same config work w/o the proxy? The stack above says "Unable to resolve realm public key remotely", so I am wondering if the Keycoak Auth-Server is deployed as well.
>  
> In the meantime I'll ask our Keycloak friends if they have any experience on this.
>  
> Thanks,
> Matthias
>  
>  
> On Fri, Oct 17, 2014 at 6:59 AM, chale <[hidden email] (/user/SendEmail.jtp?type=node&node=9490&i=0)> wrote:
> > Hi,
> >     I need some help.  I am trying to setup aerogear behind a nginx proxy
> > server that has ssl enabled and I am running into issues.  Anytime i try to
> > go to /ag-push I see this in the logs
> >  
> > RROR [org.apache.catalina.connector.CoyoteAdapter]
> > (http--10.128.93.235-8080-5) An exception or error occurred in the container
> > during the request processing: java.lang.RuntimeException: Unable to resolve
> > realm public key remotely, status = 403
> >         at
> > org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:69)
> > [keycloak-adapter-core-1.0-final.jar:]
> >         at
> > org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:55)
> > [keycloak-adapter-core-1.0-final.jar:]
> >         at
> > org.keycloak.adapters.as7.AuthenticatedActionsValve.invoke(AuthenticatedActionsValve.java:45)
> > [keycloak-as7-adapter-1.0-final.jar:]
> >         at
> > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
> > [jbossweb-7.0.13.Final.jar:]
> >         at
> > org.keycloak.adapters.as7.KeycloakAuthenticatorValve.invoke(KeycloakAuthenticatorValve.java:135)
> > [keycloak-as7-adapter-1.0-final.jar:]
> >         at
> > org.jboss.as.web.security.SecurityContextAssociationValve.invoke (http://web.security.SecurityContextAssociationValve.invoke)(SecurityContextAssociationValve.java:153)
> > [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> >         at
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> > [jbossweb-7.0.13.Final.jar:]
> >         at
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > [jbossweb-7.0.13.Final.jar:]
> >         at
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> > [jbossweb-7.0.13.Final.jar:]
> >         at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> > [jbossweb-7.0.13.Final.jar:]
> >         at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> > [jbossweb-7.0.13.Final.jar:]
> >         at
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
> > [jbossweb-7.0.13.Final.jar:]
> >         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
> > [jbossweb-7.0.13.Final.jar:]
> >         at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> >  
> > Does anyone have any advice or experience on how to go about setting up
> > aerogear behind an nginx proxy?
> >  
> >  
> >  
> > --
> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489.html
> > Sent from the aerogear-dev mailing list archive at Nabble.com (http://Nabble.com).
> > _______________________________________________
> > aerogear-dev mailing list
> > [hidden email] (/user/SendEmail.jtp?type=node&node=9490&i=1)
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>  
>  
>  
> --  
> Matthias Wessendorf  
>  
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf  
> _______________________________________________  
> aerogear-dev mailing list  
> [hidden email] (/user/SendEmail.jtp?type=node&node=9490&i=2)  
> 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/setting-up-aerogear-behind-nginx-proxy-tp9489p9490.html  
> To unsubscribe from setting up aerogear behind nginx proxy, click here (http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=9489&code=Y2hyaXMuaGFsZUBtZS5jb218OTQ4OXwtMTIxOTIzODgyMg==).
> 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.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: http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489p9491.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/20141016/6477c1ac/attachment-0001.html 

From matzew at apache.org  Fri Oct 17 02:08:08 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 17 Oct 2014 08:08:08 +0200
Subject: [aerogear-dev] setting up aerogear behind nginx proxy
In-Reply-To: <1C9981E0376945CAA8492605D1B1FA7A@me.com>
References: <1413521972011-9489.post@n5.nabble.com>
	<CAAg5f2RadS0+BaAQUsnmTvdDsOOHrmD3eMH=gCfXhy=Et7GO=A@mail.gmail.com>
	<1C9981E0376945CAA8492605D1B1FA7A@me.com>
Message-ID: <CAAg5f2QiV3jKz1KpvuM1CZ5svWYm7eumD1oqSHGhjM5K1h=auw@mail.gmail.com>

Hey Chris!

glad to hear about the progress :)

regarding the "Invalid redirect_uri", looks like something goes wrong with
the redirect/ forward.
On the page were you get the login form (or the Invalid redirect_uri), can
you compare the URL in the browser ?
(especially the part after the &redirect_uri param).

On the 500, any stack trace there?

Thanks,
Matthias


On Fri, Oct 17, 2014 at 7:38 AM, chale <chris.hale at me.com> wrote:

> I am having a little more positive progress and a few more useful things
> to report from me trying to get this working.
> The logs below aren?t an issue anymore.  Here is how i now have things
> setup.
>
> I have nginx setup and running on port 443 and my nginx config looks like
> this
> location / {
>         if ($http_user_agent ~ ^$) {
> #                return 403;
>         }
>
>         proxy_pass http://10.128.93.235:8080/;
>         proxy_redirect off;
>
>         proxy_set_header Host $host;
> proxy_set_header X-Forwarded-Proto "https";
> proxy_set_header X-Forwarded-Host $host;
>         proxy_set_header X-Forwarded-Server $host;
>        proxy_set_header X-Real-IP $remote_addr;
>         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>     }
>
>
> I seem to be able to login if i choose http://myserver.com  but if i try
> and do https://myserver.com/ag-push
>
> I get a message that is saying we are sorry Invalid redirect_uri. .
>
> In looking at the http requests I am seeing
> /auth/realms/aerogear/tokens/login url cause a 500
>
> Any way to troubleshoot why its giving a 500?
>
> Thanks in advance,
>
>
>
>
> --
> Chris Hale
> Sent with Sparrow <http://www.sparrowmailapp.com/?sig>
>
> On Friday, October 17, 2014 at 12:31 AM, Matthias Wessendorf [via
> aerogear-dev] wrote:
>
>  Hi Chris!
>
> thanks for trying the UnifiedPush Server. I have never tried to run the
> UPS behind a (ngnix) proxy. Does the same config work w/o the proxy? The
> stack above says "Unable to resolve realm public key remotely", so I am
> wondering if the Keycoak Auth-Server is deployed as well.
>
> In the meantime I'll ask our Keycloak friends if they have any experience
> on this.
>
> Thanks,
> Matthias
>
> On Fri, Oct 17, 2014 at 6:59 AM, chale <[hidden email]
> <http://user/SendEmail.jtp?type=node&node=9490&i=0>> wrote:
>
> Hi,
>     I need some help.  I am trying to setup aerogear behind a nginx proxy
> server that has ssl enabled and I am running into issues.  Anytime i try to
> go to /ag-push I see this in the logs
>
> RROR [org.apache.catalina.connector.CoyoteAdapter]
> (http--10.128.93.235-8080-5) An exception or error occurred in the
> container
> during the request processing: java.lang.RuntimeException: Unable to
> resolve
> realm public key remotely, status = 403
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:69)
> [keycloak-adapter-core-1.0-final.jar:]
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:55)
> [keycloak-adapter-core-1.0-final.jar:]
>         at
>
> org.keycloak.adapters.as7.AuthenticatedActionsValve.invoke(AuthenticatedActionsValve.java:45)
> [keycloak-as7-adapter-1.0-final.jar:]
>         at
>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.keycloak.adapters.as7.KeycloakAuthenticatorValve.invoke(KeycloakAuthenticatorValve.java:135)
> [keycloak-as7-adapter-1.0-final.jar:]
>         at
> org.jboss.as.web.security.SecurityContextAssociationValve.invoke
> (SecurityContextAssociationValve.java:153)
> [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
>         at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> [jbossweb-7.0.13.Final.jar:]
>         at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> [jbossweb-7.0.13.Final.jar:]
>         at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> [jbossweb-7.0.13.Final.jar:]
>         at
>
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
> [jbossweb-7.0.13.Final.jar:]
>         at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
> [jbossweb-7.0.13.Final.jar:]
>         at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
>
> Does anyone have any advice or experience on how to go about setting up
> aerogear behind an nginx proxy?
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=9490&i=1>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=9490&i=2>
> 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/setting-up-aerogear-behind-nginx-proxy-tp9489p9490.html
>  To unsubscribe from setting up aerogear behind nginx proxy, 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.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] setting up aerogear
> behind nginx proxy
> <http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489p9491.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
>



-- 
Matthias Wessendorf

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

From stian at redhat.com  Fri Oct 17 02:35:36 2014
From: stian at redhat.com (Stian Thorgersen)
Date: Fri, 17 Oct 2014 02:35:36 -0400 (EDT)
Subject: [aerogear-dev] setting up aerogear behind nginx proxy
In-Reply-To: <CAAg5f2QiV3jKz1KpvuM1CZ5svWYm7eumD1oqSHGhjM5K1h=auw@mail.gmail.com>
References: <1413521972011-9489.post@n5.nabble.com>
	<CAAg5f2RadS0+BaAQUsnmTvdDsOOHrmD3eMH=gCfXhy=Et7GO=A@mail.gmail.com>
	<1C9981E0376945CAA8492605D1B1FA7A@me.com>
	<CAAg5f2QiV3jKz1KpvuM1CZ5svWYm7eumD1oqSHGhjM5K1h=auw@mail.gmail.com>
Message-ID: <1929066917.70404400.1413527736910.JavaMail.zimbra@redhat.com>

Hi Chris,

Can you copy/paste the full URL where you get the 'invalid redirect_uri' message?

For details about setting up reverse proxy with Keycloak look at http://docs.jboss.org/keycloak/docs/1.0.2.Final/userguide/html/server-installation.html#d4e298. Key things are X-Forwarded-For and X-Forwarded-Proto which it looks like you've added, but you also need to do some changes to standalone.xml.

----- Original Message -----
> From: "Matthias Wessendorf" <matzew at apache.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Friday, 17 October, 2014 8:08:08 AM
> Subject: Re: [aerogear-dev] setting up aerogear behind nginx proxy
> 
> Hey Chris!
> 
> glad to hear about the progress :)
> 
> regarding the "Invalid redirect_uri", looks like something goes wrong with
> the redirect/ forward.
> On the page were you get the login form (or the Invalid redirect_uri), can
> you compare the URL in the browser ?
> (especially the part after the &redirect_uri param).
> 
> On the 500, any stack trace there?
> 
> Thanks,
> Matthias
> 
> 
> On Fri, Oct 17, 2014 at 7:38 AM, chale < chris.hale at me.com > wrote:
> 
> 
> 
> I am having a little more positive progress and a few more useful things to
> report from me trying to get this working.
> The logs below aren?t an issue anymore. Here is how i now have things setup.
> 
> I have nginx setup and running on port 443 and my nginx config looks like
> this
> location / {
> if ($http_user_agent ~ ^$) {
> # return 403;
> }
> 
> proxy_pass http://10.128.93.235:8080/ ;
> proxy_redirect off;
> 
> proxy_set_header Host $host;
> proxy_set_header X-Forwarded-Proto "https";
> proxy_set_header X-Forwarded-Host $host;
> proxy_set_header X-Forwarded-Server $host;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> }
> 
> 
> I seem to be able to login if i choose http://myserver.com but if i try and
> do https://myserver.com/ag-push
> 
> I get a message that is saying we are sorry Invalid redirect_uri. .
> 
> In looking at the http requests I am seeing
> /auth/realms/aerogear/tokens/login url cause a 500
> 
> Any way to troubleshoot why its giving a 500?
> 
> Thanks in advance,
> 
> 
> 
> 
> --
> Chris Hale
> Sent with Sparrow
> 
> 
> 
> On Friday, October 17, 2014 at 12:31 AM, Matthias Wessendorf [via
> aerogear-dev] wrote:
> 
> 
> Hi Chris!
> 
> thanks for trying the UnifiedPush Server. I have never tried to run the UPS
> behind a (ngnix) proxy. Does the same config work w/o the proxy? The stack
> above says "Unable to resolve realm public key remotely", so I am wondering
> if the Keycoak Auth-Server is deployed as well.
> 
> In the meantime I'll ask our Keycloak friends if they have any experience on
> this.
> 
> Thanks,
> Matthias
> 
> On Fri, Oct 17, 2014 at 6:59 AM, chale < [hidden email] > wrote:
> 
> 
> 
> Hi,
> I need some help. I am trying to setup aerogear behind a nginx proxy
> server that has ssl enabled and I am running into issues. Anytime i try to
> go to /ag-push I see this in the logs
> 
> RROR [org.apache.catalina.connector.CoyoteAdapter]
> (http--10.128.93.235-8080-5) An exception or error occurred in the container
> during the request processing: java.lang.RuntimeException: Unable to resolve
> realm public key remotely, status = 403
> at
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:69)
> [keycloak-adapter-core-1.0-final.jar:]
> at
> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:55)
> [keycloak-adapter-core-1.0-final.jar:]
> at
> org.keycloak.adapters.as7.AuthenticatedActionsValve.invoke(AuthenticatedActionsValve.java:45)
> [keycloak-as7-adapter-1.0-final.jar:]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.keycloak.adapters.as7.KeycloakAuthenticatorValve.invoke(KeycloakAuthenticatorValve.java:135)
> [keycloak-as7-adapter-1.0-final.jar:]
> at
> org.jboss.as . web.security.SecurityContextAssociationValve.invoke
> (SecurityContextAssociationValve.java:153)
> [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
> [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
> [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> 
> Does anyone have any advice or experience on how to go about setting up
> aerogear behind an nginx proxy?
> 
> 
> 
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-nginx-proxy-tp9489.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
> 
> 
> 
> --
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> 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/setting-up-aerogear-behind-nginx-proxy-tp9489p9490.html
> To unsubscribe from setting up aerogear behind nginx proxy, click here .
> NAML
> 
> 
> 
> View this message in context: Re: [aerogear-dev] setting up aerogear behind
> nginx proxy
> 
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> --
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From matzew at apache.org  Fri Oct 17 04:35:02 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 17 Oct 2014 10:35:02 +0200
Subject: [aerogear-dev] UPS new release (1.0.2)
Message-ID: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>

hello,

I'd like to release 1.0.2 by end of the month. Here is the JIRA for
tracking 1.0.2:
https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081

the biggest improvement will the be new user/role (developer), and where an
Admin can see/manage all apps, of all 'developers'.

Besides that, the release contains improvements and taking up new
dependencies, such as Keycloak 1.0.2

Any comments? I will adjust the roadmap early next week

-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Fri Oct 17 05:43:19 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 17 Oct 2014 02:43:19 -0700 (PDT)
Subject: [aerogear-dev] UPS new release (1.0.2)
In-Reply-To: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
References: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
Message-ID: <1413538999207.4d5e0569@Nodemailer>

Sounds good

?

abstractj
PGP: 0x84DC9914

On Fri, Oct 17, 2014 at 5:35 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> hello,
> I'd like to release 1.0.2 by end of the month. Here is the JIRA for
> tracking 1.0.2:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081
> the biggest improvement will the be new user/role (developer), and where an
> Admin can see/manage all apps, of all 'developers'.
> Besides that, the release contains improvements and taking up new
> dependencies, such as Keycloak 1.0.2
> Any comments? I will adjust the roadmap early next week
> -- 
> Matthias Wessendorf
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141017/2957163b/attachment.html 

From lukas.fryc at gmail.com  Fri Oct 17 06:08:05 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Fri, 17 Oct 2014 12:08:05 +0200
Subject: [aerogear-dev] UPS new release (1.0.2)
In-Reply-To: <1413538999207.4d5e0569@Nodemailer>
References: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
	<1413538999207.4d5e0569@Nodemailer>
Message-ID: <CAEroY34fe+DvMF6A-NpQjkcgDn-siuMNemhm4w=yKjmdM-BTfA@mail.gmail.com>

+1 sounds good

On Fri, Oct 17, 2014 at 11:43 AM, Bruno Oliveira <bruno at abstractj.org>
wrote:

> Sounds good
> ?
>
> abstractj
> PGP: 0x84DC9914
>
>
> On Fri, Oct 17, 2014 at 5:35 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> hello,
>>
>> I'd like to release 1.0.2 by end of the month. Here is the JIRA for
>> tracking 1.0.2:
>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081
>>
>> the biggest improvement will the be new user/role (developer), and where
>> an Admin can see/manage all apps, of all 'developers'.
>>
>> Besides that, the release contains improvements and taking up new
>> dependencies, such as Keycloak 1.0.2
>>
>> Any comments? I will adjust the roadmap early next week
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/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/20141017/eaab00c8/attachment.html 

From daniel at passos.me  Fri Oct 17 08:31:02 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 17 Oct 2014 09:31:02 -0300
Subject: [aerogear-dev] Releasing new parent/bom (0.2.8)
In-Reply-To: <20141017020940.GE71845@darkstar.local>
References: <CAKjsGbv4iPn4Q9SCP7Prd-gHxO21jX1aDORCJQAQxJ6EeiCgmA@mail.gmail.com>
	<CAAg5f2SYG+NAgCP5ENB1kR=-jGM3Urwe8bMfzed5-yOZ3RkjHg@mail.gmail.com>
	<CAKjsGbvzmt1+yKomXz27261hiB9cwQUs047FJSw4hUqY45qJLA@mail.gmail.com>
	<CAAg5f2S2e7iohJoxGgiOs413fdP0HUa79ThB0hUfA96ifOBq3w@mail.gmail.com>
	<20141017020940.GE71845@darkstar.local>
Message-ID: <CAKjsGbtczQL+dN40ENgVBM6XnrzDmzKiRTV1Sa_xZ2fjVtp3+g@mail.gmail.com>

I just release it to maven central.

-- Passos

On Thu, Oct 16, 2014 at 11:09 PM, Douglas Campos <qmx at qmx.me> wrote:

> On Thu, Oct 16, 2014 at 12:14:10PM +0200, Matthias Wessendorf wrote:
> > On Thu, Oct 16, 2014 at 12:08 PM, Daniel Passos <daniel at passos.me>
> wrote:
> >
> > > Hi Matthias,
> > >
> > > Of course, not sure if it's the correct but in my flow I only push it
> to
> > > repo, after release it, so, we can revert it or add something like
> this[1]
> > > without dirtying the repository
> > >
> >
> > perhaps we than should change the flow here:
> > https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
> -1
>
> Tags are somehow easier to update without leaving a trail of failed
> attempts. Once you push to master, it just becomes noise and reverts.
>
> --
> qmx
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141017/23a5ed04/attachment.html 

From daniel at passos.me  Fri Oct 17 08:32:05 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 17 Oct 2014 09:32:05 -0300
Subject: [aerogear-dev] UPS new release (1.0.2)
In-Reply-To: <CAEroY34fe+DvMF6A-NpQjkcgDn-siuMNemhm4w=yKjmdM-BTfA@mail.gmail.com>
References: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
	<1413538999207.4d5e0569@Nodemailer>
	<CAEroY34fe+DvMF6A-NpQjkcgDn-siuMNemhm4w=yKjmdM-BTfA@mail.gmail.com>
Message-ID: <CAKjsGbsKAvm4OavDr-dHN-NM_eebSfqXJgBax-HtRSYMxRWYqw@mail.gmail.com>

+1

On Fri, Oct 17, 2014 at 7:08 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> +1 sounds good
>
> On Fri, Oct 17, 2014 at 11:43 AM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> Sounds good
>> ?
>>
>> abstractj
>> PGP: 0x84DC9914
>>
>>
>> On Fri, Oct 17, 2014 at 5:35 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> hello,
>>>
>>> I'd like to release 1.0.2 by end of the month. Here is the JIRA for
>>> tracking 1.0.2:
>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081
>>>
>>> the biggest improvement will the be new user/role (developer), and where
>>> an Admin can see/manage all apps, of all 'developers'.
>>>
>>> Besides that, the release contains improvements and taking up new
>>> dependencies, such as Keycloak 1.0.2
>>>
>>> Any comments? I will adjust the roadmap early next week
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20141017/df978833/attachment.html 

From qmx at qmx.me  Fri Oct 17 09:56:09 2014
From: qmx at qmx.me (Douglas Campos)
Date: Fri, 17 Oct 2014 10:56:09 -0300
Subject: [aerogear-dev] UPS new release (1.0.2)
In-Reply-To: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
References: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
Message-ID: <20141017135609.GF71845@darkstar.local>

+1 go for it!


-- 
qmx

From daniel.bevenius at gmail.com  Fri Oct 17 10:00:25 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 17 Oct 2014 16:00:25 +0200
Subject: [aerogear-dev] UPS new release (1.0.2)
In-Reply-To: <CAKjsGbsKAvm4OavDr-dHN-NM_eebSfqXJgBax-HtRSYMxRWYqw@mail.gmail.com>
References: <CAAg5f2RrbN4BMOrZ_BXO2TFe-+GAg-9CFO2-uByzW54vj0cCdw@mail.gmail.com>
	<1413538999207.4d5e0569@Nodemailer>
	<CAEroY34fe+DvMF6A-NpQjkcgDn-siuMNemhm4w=yKjmdM-BTfA@mail.gmail.com>
	<CAKjsGbsKAvm4OavDr-dHN-NM_eebSfqXJgBax-HtRSYMxRWYqw@mail.gmail.com>
Message-ID: <CAFJm-3EB+oC045=eG8EQULQtYozR8xz8GCbruX2KN74kQrN69Q@mail.gmail.com>

+1

On 17 October 2014 14:32, Daniel Passos <daniel at passos.me> wrote:

> +1
>
> On Fri, Oct 17, 2014 at 7:08 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
>> +1 sounds good
>>
>> On Fri, Oct 17, 2014 at 11:43 AM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>>
>>> Sounds good
>>> ?
>>>
>>> abstractj
>>> PGP: 0x84DC9914
>>>
>>>
>>> On Fri, Oct 17, 2014 at 5:35 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> hello,
>>>>
>>>> I'd like to release 1.0.2 by end of the month. Here is the JIRA for
>>>> tracking 1.0.2:
>>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081
>>>>
>>>> the biggest improvement will the be new user/role (developer), and
>>>> where an Admin can see/manage all apps, of all 'developers'.
>>>>
>>>> Besides that, the release contains improvements and taking up new
>>>> dependencies, such as Keycloak 1.0.2
>>>>
>>>> Any comments? I will adjust the roadmap early next week
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20141017/1e25e4da/attachment.html 

From daniel.bevenius at gmail.com  Sat Oct 18 08:37:15 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Sat, 18 Oct 2014 14:37:15 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3GbV-MF-Kf6depMEokRv73=OopBTic=zsW6k87aPeOBTA@mail.gmail.com>

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

From chris.hale at me.com  Sat Oct 18 18:12:39 2014
From: chris.hale at me.com (Chris Hale)
Date: Sat, 18 Oct 2014 17:12:39 -0500
Subject: [aerogear-dev] Anyone have experience with Node Send Client
Message-ID: <96AA903D8BB541F193E1C524777B5F61@me.com>

I have been trying the node send client and all I am getting when testing is a error code of 411.  Anybody have troubleshooting advice or knowledge about this type of error? 

Thanks in advance, 

-- 
Chris Hale
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

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

From lholmqui at redhat.com  Sat Oct 18 18:19:10 2014
From: lholmqui at redhat.com (Luke Holmquist)
Date: Sat, 18 Oct 2014 18:19:10 -0400 (EDT)
Subject: [aerogear-dev] Anyone have experience with Node Send Client
In-Reply-To: <96AA903D8BB541F193E1C524777B5F61@me.com>
References: <96AA903D8BB541F193E1C524777B5F61@me.com>
Message-ID: <55DCC498-3080-4B9C-9C34-B16797EB0EB8@redhat.com>

Hey man.  

Could you maybe send some code snippets or a gist. 

Sent from my iPhone

> On Oct 18, 2014, at 6:14 PM, Chris Hale <chris.hale at me.com> wrote:
> 
> I have been trying the node send client and all I am getting when testing is a error code of 411.  Anybody have troubleshooting advice or knowledge about this type of error?
> 
> Thanks in advance,
> 
> -- 
> Chris Hale
> Sent with Sparrow
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141018/f4ad18a4/attachment.html 

From matzew at apache.org  Sun Oct 19 06:14:42 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Sun, 19 Oct 2014 12:14:42 +0200
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3GbV-MF-Kf6depMEokRv73=OopBTic=zsW6k87aPeOBTA@mail.gmail.com>
References: <CAFJm-3GbV-MF-Kf6depMEokRv73=OopBTic=zsW6k87aPeOBTA@mail.gmail.com>
Message-ID: <CAAg5f2RbLLU99NkiCHidvzCutUVuEd4xm1NEFnJ3F0CSvEeXmQ@mail.gmail.com>

Thansk Dan,

since I will be traveling, I added a few items to the agenda already

On Sat, Oct 18, 2014 at 2:37 PM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> Agenda:
> http://oksoclap.com/p/aerogear-team-mgt-20141020
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141019/d3cdf888/attachment.html 

From chris.hale at me.com  Sun Oct 19 09:25:19 2014
From: chris.hale at me.com (Chris Hale)
Date: Sun, 19 Oct 2014 08:25:19 -0500
Subject: [aerogear-dev] Anyone have experience with Node Send Client
In-Reply-To: <55DCC498-3080-4B9C-9C34-B16797EB0EB8@redhat.com>
References: <96AA903D8BB541F193E1C524777B5F61@me.com>
	<55DCC498-3080-4B9C-9C34-B16797EB0EB8@redhat.com>
Message-ID: <D7B213EB9E9B4B9E9FB08C27BB184316@me.com>

I ended up fixing the code problem and submitted a pull request for the bug in the node send client. 

Thanks  

-- 
Chris Hale
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Saturday, October 18, 2014 at 5:19 PM, Luke Holmquist wrote:

> Hey man.  
> 
> Could you maybe send some code snippets or a gist. 
> 
> Sent from my iPhone
> 
> On Oct 18, 2014, at 6:14 PM, Chris Hale <chris.hale at me.com (mailto:chris.hale at me.com)> wrote:
> 
> > I have been trying the node send client and all I am getting when testing is a error code of 411.  Anybody have troubleshooting advice or knowledge about this type of error? 
> > 
> > Thanks in advance, 
> > 
> > -- 
> > Chris Hale
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > 
> > _______________________________________________
> > 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
> 
> 


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

From matzew at apache.org  Sun Oct 19 12:14:05 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Sun, 19 Oct 2014 18:14:05 +0200
Subject: [aerogear-dev] Using the UnifiedPush Server
Message-ID: <CAAg5f2ScmQ2dtnLkOm12OLRMPEMLA2ms27DOTGRQxCmdpiGwcA@mail.gmail.com>

hello,

if you are using the UnifedPush Server, feel free to add your
company/project to this new wiki page:

https://github.com/aerogear/aerogear-unifiedpush-server/wiki/Users-of-the-UnifiedPush-Server

Thanks :-)

-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Mon Oct 20 04:10:12 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 20 Oct 2014 10:10:12 +0200
Subject: [aerogear-dev] Branching the Java Sender (1.1 and 1.0.x)
Message-ID: <CAD_dpu3zcDW0G40naQdxGYvd5wA5T15bg-X2-9xsXoCf0Mgi8g@mail.gmail.com>

Hi folk !

Like we did it for the UPS and the Cordova Push plugin, I have just created
a 1.0.x branch for the UnifiedPush Java Sender[1], the master point to 1.1

sebi



[1] https://github.com/aerogear/aerogear-unifiedpush-java-client/tree/1.0.x
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/7d1f40d7/attachment.html 

From matzew at apache.org  Mon Oct 20 04:14:50 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 20 Oct 2014 10:14:50 +0200
Subject: [aerogear-dev] Branching the Java Sender (1.1 and 1.0.x)
In-Reply-To: <CAD_dpu3zcDW0G40naQdxGYvd5wA5T15bg-X2-9xsXoCf0Mgi8g@mail.gmail.com>
References: <CAD_dpu3zcDW0G40naQdxGYvd5wA5T15bg-X2-9xsXoCf0Mgi8g@mail.gmail.com>
Message-ID: <CAAg5f2S=yB8TOSMFqJZSpdbidXrmZv=PNVpOx+CZ0Cqa=7BuJA@mail.gmail.com>

yeah, sounds reasonable, especially with the new sender REST API coming in
1.1.x

-M

On Mon, Oct 20, 2014 at 10:10 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hi folk !
>
> Like we did it for the UPS and the Cordova Push plugin, I have just
> created a 1.0.x branch for the UnifiedPush Java Sender[1], the master point
> to 1.1
>
> sebi
>
>
>
> [1]
> https://github.com/aerogear/aerogear-unifiedpush-java-client/tree/1.0.x
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141020/2c3d7570/attachment.html 

From scm.blanc at gmail.com  Mon Oct 20 04:20:14 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 20 Oct 2014 10:20:14 +0200
Subject: [aerogear-dev] Branching the Java Sender (1.1 and 1.0.x)
In-Reply-To: <CAAg5f2S=yB8TOSMFqJZSpdbidXrmZv=PNVpOx+CZ0Cqa=7BuJA@mail.gmail.com>
References: <CAD_dpu3zcDW0G40naQdxGYvd5wA5T15bg-X2-9xsXoCf0Mgi8g@mail.gmail.com>
	<CAAg5f2S=yB8TOSMFqJZSpdbidXrmZv=PNVpOx+CZ0Cqa=7BuJA@mail.gmail.com>
Message-ID: <CAD_dpu19vg5KR1iuDhaYeQBKy7_dy82BZ1FOKFg+d3EwADTokA@mail.gmail.com>

On Mon, Oct 20, 2014 at 10:14 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> yeah, sounds reasonable, especially with the new sender REST API coming in
> 1.1.x
>
eggxactly , that was the main reason ;)

>
> -M
>
> On Mon, Oct 20, 2014 at 10:10 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Hi folk !
>>
>> Like we did it for the UPS and the Cordova Push plugin, I have just
>> created a 1.0.x branch for the UnifiedPush Java Sender[1], the master point
>> to 1.1
>>
>> sebi
>>
>>
>>
>> [1]
>> https://github.com/aerogear/aerogear-unifiedpush-java-client/tree/1.0.x
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20141020/4dc5ba23/attachment.html 

From corinnekrych at gmail.com  Mon Oct 20 04:40:14 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 20 Oct 2014 10:40:14 +0200
Subject: [aerogear-dev] iOS meeting to prepare 2.1 release
Message-ID: <83AC41B1-3276-47CC-A179-945B180C75B0@gmail.com>

Hello iOS world!

Our next iOS meeting we will focus on organizing 2.1 release.
Be warmed it could be a long list of JIRAs in it. For now here is a skeleton of meeting agenda (to be completed):
http://oksoclap.com/p/planning_ios_2.1

Let?s meet Tuesday 21st October 4pm (CEST - UTC + 2hours) on IRC #aerogear
See you all there.

++
Corinne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/8ce7e710/attachment.bin 

From lukas.fryc at gmail.com  Mon Oct 20 07:58:51 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 20 Oct 2014 13:58:51 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
Message-ID: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>

Hey guys,

I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as
Firefox OS using our Cordova plugin.

But as you know, with FFOS it is not that simple - since SimplePush
protocol allows to transfer just incremental versions, we are not able to
deliver any interesting message.

UnifiedPush Server could be a correct place where we unify and shield our
users from this limitation:


my idea is storing the message on UPS under the SimplePush endpoint URL.
Once the message with version reaches the client, he would contact UPS to
retrieve this message under a key ( pushEndpoint, version ).

The messages could have default built-in TTL to allow periodic cleanup.

What do you think?


Cheers,

~ Lukas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/3de64b94/attachment.html 

From matzew at apache.org  Mon Oct 20 08:06:31 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 20 Oct 2014 14:06:31 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
Message-ID: <CAAg5f2S381nNt22EdboBBX1uP1b=9ozsSuNvF86ew-2bgrBHJg@mail.gmail.com>

not sure. but perhaps worth to look into this for 1.1x

Oh, aren't the new SimplePush specs (or was it WebPush) defining richer
payloads, like we know from Android or iOS?

On Monday, October 20, 2014, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hey guys,
>
> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as
> Firefox OS using our Cordova plugin.
>
> But as you know, with FFOS it is not that simple - since SimplePush
> protocol allows to transfer just incremental versions, we are not able to
> deliver any interesting message.
>
> UnifiedPush Server could be a correct place where we unify and shield our
> users from this limitation:
>
>
> my idea is storing the message on UPS under the SimplePush endpoint URL.
> Once the message with version reaches the client, he would contact UPS to
> retrieve this message under a key ( pushEndpoint, version ).
>
> The messages could have default built-in TTL to allow periodic cleanup.
>
> What do you think?
>
>
> Cheers,
>
> ~ Lukas
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/c0ba2ea2/attachment.html 

From edewit at redhat.com  Mon Oct 20 08:07:36 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 20 Oct 2014 14:07:36 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
Message-ID: <1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>

Hi Luk??,

I like that idea, because in the end our goal is to unify. And I think that the simple push protocol will be changed in the future to allow for ?normal? message sending. So we could fallback afterwards.

Cheers,
	Erik Jan

On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hey guys,
> 
> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as Firefox OS using our Cordova plugin.
> 
> But as you know, with FFOS it is not that simple - since SimplePush protocol allows to transfer just incremental versions, we are not able to deliver any interesting message.
> 
> UnifiedPush Server could be a correct place where we unify and shield our users from this limitation:
> 
> 
> my idea is storing the message on UPS under the SimplePush endpoint URL. Once the message with version reaches the client, he would contact UPS to retrieve this message under a key ( pushEndpoint, version ).
> 
> The messages could have default built-in TTL to allow periodic cleanup.
> 
> What do you think?
> 
> 
> Cheers,
> 
> ~ Lukas
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From lholmqui at redhat.com  Mon Oct 20 08:40:29 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 20 Oct 2014 08:40:29 -0400
Subject: [aerogear-dev] database migration
In-Reply-To: <20141013043103.GC56451@darkstar.local>
References: <AF6339FC-1106-4A12-864B-7649F415CA33@redhat.com>
	<CAAg5f2Sd9AJKRN=uZTFh8D1KK1EAuc8N0w+t3hvpzP-zjjn5Pg@mail.gmail.com>
	<1331427146.62808801.1412668633586.JavaMail.zimbra@redhat.com>
	<CAAg5f2SwcLYFu9unN24Muke-oNRs_oSMzaCMRm+fDjXhfcDd0w@mail.gmail.com>
	<1999658546.63027404.1412686763673.JavaMail.zimbra@redhat.com>
	<DBBFE1C0-DDBC-43E1-BC86-1B60F4CFA174@redhat.com>
	<1862184835.63049258.1412687518710.JavaMail.zimbra@redhat.com>
	<91B9B026-7646-4C4B-928D-93FC2E4FED25@redhat.com>
	<20141013043103.GC56451@darkstar.local>
Message-ID: <F57F55F2-211F-42C7-AB13-9EBBA940419A@redhat.com>


> On Oct 13, 2014, at 12:31 AM, Douglas Campos <qmx at qmx.me> wrote:
> 
> On Tue, Oct 07, 2014 at 03:20:19PM +0200, Erik Jan de Wit wrote:
>> On 7 Oct,2014, at 15:11 , Stian Thorgersen <stian at redhat.com> wrote:
>> 
>>>> FlywayDB uses SQL directly, so we have to deal with differences between
>>>> databases ourselves. IMO that renders it useless!
>>>> 
>>>> liquibase it is, and let?s not use xml for the change sets ;)
>>> 
>>> Why not XML?
>>> 
>> 
>> We hate XML
> While I do hate XML too, in this case their xsd's are kickass on
> validating stuff for us. (happy liquibase user here too)
> 
> I'd say "embrace the darkness^H^H^HXML unless we have a huge reason to
> avoid it.
This reminds me of Luke asking Yoda if the Dark is Stronger.

?NO!,  quicker, more seductive"


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



From lukas.fryc at gmail.com  Mon Oct 20 08:51:36 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 20 Oct 2014 14:51:36 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
Message-ID: <CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>

Awesome, great to hear that SimplePush will get a native support for a full
message content.

As Erik said, in the meantime, we could unify this behavior.
I have created the associated issue:
https://issues.jboss.org/browse/AGPUSH-1073

On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi Luk??,
>
> I like that idea, because in the end our goal is to unify. And I think
> that the simple push protocol will be changed in the future to allow
> for ?normal? message sending. So we could fallback afterwards.
>
> Cheers,
> Erik Jan
>
> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
> Hey guys,
>
> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as
> Firefox OS using our Cordova plugin.
>
> But as you know, with FFOS it is not that simple - since SimplePush
> protocol allows to transfer just incremental versions, we are not able to
> deliver any interesting message.
>
> UnifiedPush Server could be a correct place where we unify and shield our
> users from this limitation:
>
>
> my idea is storing the message on UPS under the SimplePush endpoint URL.
> Once the message with version reaches the client, he would contact UPS to
> retrieve this message under a key ( pushEndpoint, version ).
>
> The messages could have default built-in TTL to allow periodic cleanup.
>
> What do you think?
>
>
> Cheers,
>
> ~ Lukas
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/e82e07ea/attachment.html 

From supittma at redhat.com  Mon Oct 20 08:52:34 2014
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 20 Oct 2014 08:52:34 -0400
Subject: [aerogear-dev] General Android Updates
Message-ID: <54450592.8050602@redhat.com>


Last week was a big week.

* Merged last PR from out "Alpha" list
* Android L released
* Maven Android Plugin 4.0-rc.1 migration begun
  * Deprecates apklib
  * Introduces new project layout
* Travis builds on  multiple JDKs now.

We continued work on sync and started work on Shoot and Share.  This led 
to the discovery of some issues with the module system and Gradle. The 
aar builds produced by our current build system don't handle 
dependencies correctly. This problem doesn't seem to exist in the 
4.0-rc.1 plugin.  Also the 4.0 project structure is compatible with the 
Gradle project structure which *SHOULD* make interacting with Android 
Studio better.

This week we are tackling several big issues/tasks at once.

* Updating all of the Travis builds to use multi-JDK
* Updating all of the projects to MAP 4.0-rc.1
* Updating all of the projects to API level 21.


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


From scm.blanc at gmail.com  Mon Oct 20 08:59:07 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 20 Oct 2014 14:59:07 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
Message-ID: <CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>

I'm just worried about storing the message, for stuff like privacy, for
instance. Let's make a really short TTL or better let's delete the mesage
right after it has been retrieved.


On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Awesome, great to hear that SimplePush will get a native support for a
> full message content.
>
> As Erik said, in the meantime, we could unify this behavior.
> I have created the associated issue:
> https://issues.jboss.org/browse/AGPUSH-1073
>
>
> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> Hi Luk??,
>>
>> I like that idea, because in the end our goal is to unify. And I think
>> that the simple push protocol will be changed in the future to allow
>> for ?normal? message sending. So we could fallback afterwards.
>>
>> Cheers,
>> Erik Jan
>>
>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>>
>> Hey guys,
>>
>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as
>> Firefox OS using our Cordova plugin.
>>
>> But as you know, with FFOS it is not that simple - since SimplePush
>> protocol allows to transfer just incremental versions, we are not able to
>> deliver any interesting message.
>>
>> UnifiedPush Server could be a correct place where we unify and shield our
>> users from this limitation:
>>
>>
>> my idea is storing the message on UPS under the SimplePush endpoint URL.
>> Once the message with version reaches the client, he would contact UPS to
>> retrieve this message under a key ( pushEndpoint, version ).
>>
>> The messages could have default built-in TTL to allow periodic cleanup.
>>
>> What do you think?
>>
>>
>> Cheers,
>>
>> ~ Lukas
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/2dd35c38/attachment.html 

From lukas.fryc at gmail.com  Mon Oct 20 09:08:02 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 20 Oct 2014 15:08:02 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
Message-ID: <CAEroY34hNYC+QfUkmjFjfc8e1h7v08OW0TAAPvt5Ltru4AudCA@mail.gmail.com>

Removing after retrieval was the idea, I ve noted that in the JIRA.

I believe that push messages themselves are not really secure, since you
hand over each message to third-party without encryption.
If we leave push message encryption up to app developer, then SimplePush is
no different, or is it?

On Mon, Oct 20, 2014 at 2:59 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> I'm just worried about storing the message, for stuff like privacy, for
> instance. Let's make a really short TTL or better let's delete the mesage
> right after it has been retrieved.
>

>
> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
>> Awesome, great to hear that SimplePush will get a native support for a
>> full message content.
>>
>> As Erik said, in the meantime, we could unify this behavior.
>> I have created the associated issue:
>> https://issues.jboss.org/browse/AGPUSH-1073
>>
>>
>> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> Hi Luk??,
>>>
>>> I like that idea, because in the end our goal is to unify. And I think
>>> that the simple push protocol will be changed in the future to allow
>>> for ?normal? message sending. So we could fallback afterwards.
>>>
>>> Cheers,
>>> Erik Jan
>>>
>>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>>>
>>> Hey guys,
>>>
>>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
>>> as Firefox OS using our Cordova plugin.
>>>
>>> But as you know, with FFOS it is not that simple - since SimplePush
>>> protocol allows to transfer just incremental versions, we are not able to
>>> deliver any interesting message.
>>>
>>> UnifiedPush Server could be a correct place where we unify and shield
>>> our users from this limitation:
>>>
>>>
>>> my idea is storing the message on UPS under the SimplePush endpoint URL.
>>> Once the message with version reaches the client, he would contact UPS to
>>> retrieve this message under a key ( pushEndpoint, version ).
>>>
>>> The messages could have default built-in TTL to allow periodic cleanup.
>>>
>>> What do you think?
>>>
>>>
>>> Cheers,
>>>
>>> ~ Lukas
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/69a9d09a/attachment-0001.html 

From lholmqui at redhat.com  Mon Oct 20 09:25:15 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 20 Oct 2014 09:25:15 -0400
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
Message-ID: <A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>

I vote no for this.

I think storing messages, for any period of time is bad.

I think SimplePush should stay ?Simple? and we should follow the spec on this. 

> On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> I'm just worried about storing the message, for stuff like privacy, for instance. Let's make a really short TTL or better let's delete the mesage right after it has been retrieved.
> 
> 
> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com <mailto:lukas.fryc at gmail.com>> wrote:
> Awesome, great to hear that SimplePush will get a native support for a full message content.
> 
> As Erik said, in the meantime, we could unify this behavior.
> I have created the associated issue: https://issues.jboss.org/browse/AGPUSH-1073 <https://issues.jboss.org/browse/AGPUSH-1073>
> 
> 
> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com <mailto:edewit at redhat.com>> wrote:
> Hi Luk??,
> 
> I like that idea, because in the end our goal is to unify. And I think that the simple push protocol will be changed in the future to allow for ?normal? message sending. So we could fallback afterwards.
> 
> Cheers,
> 	Erik Jan
> 
> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com <mailto:lukas.fryc at gmail.com>> wrote:
> 
>> Hey guys,
>> 
>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as Firefox OS using our Cordova plugin.
>> 
>> But as you know, with FFOS it is not that simple - since SimplePush protocol allows to transfer just incremental versions, we are not able to deliver any interesting message.
>> 
>> UnifiedPush Server could be a correct place where we unify and shield our users from this limitation:
>> 
>> 
>> my idea is storing the message on UPS under the SimplePush endpoint URL. Once the message with version reaches the client, he would contact UPS to retrieve this message under a key ( pushEndpoint, version ).
>> 
>> The messages could have default built-in TTL to allow periodic cleanup.
>> 
>> What do you think?
>> 
>> 
>> Cheers,
>> 
>> ~ Lukas
>> _______________________________________________
>> 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>
> 
> _______________________________________________
> 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>
> 
> 
> _______________________________________________
> 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>
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/821471d2/attachment.html 

From daniel.bevenius at gmail.com  Mon Oct 20 09:43:30 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 20 Oct 2014 15:43:30 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
	<A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
Message-ID: <CAFJm-3Ek+DpkxhxRd75WuVDxS_GLPXw7n-9iJZ8ZHbFFJZS7gw@mail.gmail.com>

>Oh, aren't the new SimplePush specs (or was it WebPush) defining richer
payloads, like we know from Android or iOS?
That is for WebPush, I'm not aware of any message payload (besides a
version/timestamp) for SimplePush.

On 20 October 2014 15:25, Lucas Holmquist <lholmqui at redhat.com> wrote:

> I vote no for this.
>
> I think storing messages, for any period of time is bad.
>
> I think SimplePush should stay ?Simple? and we should follow the spec on
> this.
>
> On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> I'm just worried about storing the message, for stuff like privacy, for
> instance. Let's make a really short TTL or better let's delete the mesage
> right after it has been retrieved.
>
>
> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
>> Awesome, great to hear that SimplePush will get a native support for a
>> full message content.
>>
>> As Erik said, in the meantime, we could unify this behavior.
>> I have created the associated issue:
>> https://issues.jboss.org/browse/AGPUSH-1073
>>
>>
>> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> Hi Luk??,
>>>
>>> I like that idea, because in the end our goal is to unify. And I think
>>> that the simple push protocol will be changed in the future to allow
>>> for ?normal? message sending. So we could fallback afterwards.
>>>
>>> Cheers,
>>> Erik Jan
>>>
>>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>>>
>>> Hey guys,
>>>
>>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
>>> as Firefox OS using our Cordova plugin.
>>>
>>> But as you know, with FFOS it is not that simple - since SimplePush
>>> protocol allows to transfer just incremental versions, we are not able to
>>> deliver any interesting message.
>>>
>>> UnifiedPush Server could be a correct place where we unify and shield
>>> our users from this limitation:
>>>
>>>
>>> my idea is storing the message on UPS under the SimplePush endpoint URL.
>>> Once the message with version reaches the client, he would contact UPS to
>>> retrieve this message under a key ( pushEndpoint, version ).
>>>
>>> The messages could have default built-in TTL to allow periodic cleanup.
>>>
>>> What do you think?
>>>
>>>
>>> Cheers,
>>>
>>> ~ Lukas
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/c038bd9c/attachment.html 

From lukas.fryc at gmail.com  Mon Oct 20 09:44:02 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 20 Oct 2014 15:44:02 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
	<A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
Message-ID: <CAEroY37+G3M5HtQEeeK361zofABGbSknrgGBEZfeL2RLBvX9ag@mail.gmail.com>

Clarification: this was meant as UnifiedPushClient extension, rather then
SimplePush's one (bad wording)

On Mon, Oct 20, 2014 at 3:25 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

> I vote no for this.
>
> I think storing messages, for any period of time is bad.
>
> I think SimplePush should stay ?Simple? and we should follow the spec on
> this.
>
> On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> I'm just worried about storing the message, for stuff like privacy, for
> instance. Let's make a really short TTL or better let's delete the mesage
> right after it has been retrieved.
>
>
> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
>> Awesome, great to hear that SimplePush will get a native support for a
>> full message content.
>>
>> As Erik said, in the meantime, we could unify this behavior.
>> I have created the associated issue:
>> https://issues.jboss.org/browse/AGPUSH-1073
>>
>>
>> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> Hi Luk??,
>>>
>>> I like that idea, because in the end our goal is to unify. And I think
>>> that the simple push protocol will be changed in the future to allow
>>> for ?normal? message sending. So we could fallback afterwards.
>>>
>>> Cheers,
>>> Erik Jan
>>>
>>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>>>
>>> Hey guys,
>>>
>>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
>>> as Firefox OS using our Cordova plugin.
>>>
>>> But as you know, with FFOS it is not that simple - since SimplePush
>>> protocol allows to transfer just incremental versions, we are not able to
>>> deliver any interesting message.
>>>
>>> UnifiedPush Server could be a correct place where we unify and shield
>>> our users from this limitation:
>>>
>>>
>>> my idea is storing the message on UPS under the SimplePush endpoint URL.
>>> Once the message with version reaches the client, he would contact UPS to
>>> retrieve this message under a key ( pushEndpoint, version ).
>>>
>>> The messages could have default built-in TTL to allow periodic cleanup.
>>>
>>> What do you think?
>>>
>>>
>>> Cheers,
>>>
>>> ~ Lukas
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/f489806b/attachment-0001.html 

From lholmqui at redhat.com  Mon Oct 20 09:46:50 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 20 Oct 2014 09:46:50 -0400
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY37+G3M5HtQEeeK361zofABGbSknrgGBEZfeL2RLBvX9ag@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
	<A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
	<CAEroY37+G3M5HtQEeeK361zofABGbSknrgGBEZfeL2RLBvX9ag@mail.gmail.com>
Message-ID: <4BF09CAF-5D93-4B6F-A9F0-F83CFCCF0CCF@redhat.com>


> On Oct 20, 2014, at 9:44 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> 
> Clarification: this was meant as UnifiedPushClient extension, rather then SimplePush's one (bad wording)

i think i might still be a no,  because of storing messages

> 
> On Mon, Oct 20, 2014 at 3:25 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> I vote no for this.
> 
> I think storing messages, for any period of time is bad.
> 
> I think SimplePush should stay ?Simple? and we should follow the spec on this. 
> 
>> On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <scm.blanc at gmail.com <mailto:scm.blanc at gmail.com>> wrote:
>> 
>> I'm just worried about storing the message, for stuff like privacy, for instance. Let's make a really short TTL or better let's delete the mesage right after it has been retrieved.
>> 
>> 
>> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com <mailto:lukas.fryc at gmail.com>> wrote:
>> Awesome, great to hear that SimplePush will get a native support for a full message content.
>> 
>> As Erik said, in the meantime, we could unify this behavior.
>> I have created the associated issue: https://issues.jboss.org/browse/AGPUSH-1073 <https://issues.jboss.org/browse/AGPUSH-1073>
>> 
>> 
>> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com <mailto:edewit at redhat.com>> wrote:
>> Hi Luk??,
>> 
>> I like that idea, because in the end our goal is to unify. And I think that the simple push protocol will be changed in the future to allow for ?normal? message sending. So we could fallback afterwards.
>> 
>> Cheers,
>> 	Erik Jan
>> 
>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com <mailto:lukas.fryc at gmail.com>> wrote:
>> 
>>> Hey guys,
>>> 
>>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as Firefox OS using our Cordova plugin.
>>> 
>>> But as you know, with FFOS it is not that simple - since SimplePush protocol allows to transfer just incremental versions, we are not able to deliver any interesting message.
>>> 
>>> UnifiedPush Server could be a correct place where we unify and shield our users from this limitation:
>>> 
>>> 
>>> my idea is storing the message on UPS under the SimplePush endpoint URL. Once the message with version reaches the client, he would contact UPS to retrieve this message under a key ( pushEndpoint, version ).
>>> 
>>> The messages could have default built-in TTL to allow periodic cleanup.
>>> 
>>> What do you think?
>>> 
>>> 
>>> Cheers,
>>> 
>>> ~ Lukas
>>> _______________________________________________
>>> 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>
>> 
>> _______________________________________________
>> 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>
>> 
>> 
>> _______________________________________________
>> 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>
>> 
>> _______________________________________________
>> 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>
> 
> _______________________________________________
> 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>
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/5f979627/attachment.html 

From jrconlin at gmail.com  Mon Oct 20 10:03:21 2014
From: jrconlin at gmail.com (jr conlin)
Date: Mon, 20 Oct 2014 07:03:21 -0700
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
Message-ID: <54451629.20704@gmail.com>

FYI, Officially, the predecessor for SimplePush will be WebPush,
https://datatracker.ietf.org/wg/webpush/charter/
which runs on top of HTTP2
http://http2.github.io/

Unofficially, data is kind of a pain in the patootie, but obviously
really handy to have. There are security and privacy issues a-plenty
when dealing with data storage (HIPPA & subpoenas come to mind in the
US.) Internally, we're kicking around the idea of allowing data, but not
allowing storage, (so a device would only get data if it was actively
connected. If it was offline, it would only get the version number
update when it reconnected).

I'm also interested in what y'all come up with.

On 10/20/2014 4:58 AM, Luk?? Fry? wrote:
> Hey guys,
>
> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
> as Firefox OS using our Cordova plugin.
>
> But as you know, with FFOS it is not that simple - since SimplePush
> protocol allows to transfer just incremental versions, we are not able
> to deliver any interesting message.
>
> UnifiedPush Server could be a correct place where we unify and shield
> our users from this limitation:
>
>
> my idea is storing the message on UPS under the SimplePush endpoint
> URL. Once the message with version reaches the client, he would
> contact UPS to retrieve this message under a key ( pushEndpoint,
> version ).
>
> The messages could have default built-in TTL to allow periodic cleanup.
>
> What do you think?
>
>
> Cheers,
>
> ~ Lukas
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From lukas.fryc at gmail.com  Mon Oct 20 10:06:26 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 20 Oct 2014 16:06:26 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <4BF09CAF-5D93-4B6F-A9F0-F83CFCCF0CCF@redhat.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
	<A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
	<CAEroY37+G3M5HtQEeeK361zofABGbSknrgGBEZfeL2RLBvX9ag@mail.gmail.com>
	<4BF09CAF-5D93-4B6F-A9F0-F83CFCCF0CCF@redhat.com>
Message-ID: <CAEroY37gJ=6CAMK9nCT+iHm2obmFpwNmdW6-qnjr4uGojziFgw@mail.gmail.com>

I understand the implications,

but are you worried about storing messages per se or rather fact that UPS
would need to store anything?

Storing messages is required part in case of SimplePush deployment - all
other networks can be approached as fire&forget.

While up to the point you start to use SImplePush you are free of managing
custom storage and exposing your storage endpoint to the client, at that
point you simply have to -> ouch, that hurts.

---

In case this does not get into UPS, I would suggest at least having
interceptor on UPS side that would enable extension developers to plug such
a storage (we are limited by a fact that Push Sender does not know an
endpoint URL, actually it does not have any connection to Sender at all, so
there are limited options to connect those two).

Or maybe he can even do that today with JAX-RS interceptors? :-)

On Mon, Oct 20, 2014 at 3:46 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

>
> On Oct 20, 2014, at 9:44 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
> Clarification: this was meant as UnifiedPushClient extension, rather then
> SimplePush's one (bad wording)
>
>
> i think i might still be a no,  because of storing messages
>
>
> On Mon, Oct 20, 2014 at 3:25 PM, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
>> I vote no for this.
>>
>> I think storing messages, for any period of time is bad.
>>
>> I think SimplePush should stay ?Simple? and we should follow the spec on
>> this.
>>
>> On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>> I'm just worried about storing the message, for stuff like privacy, for
>> instance. Let's make a really short TTL or better let's delete the mesage
>> right after it has been retrieved.
>>
>>
>> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>>
>>> Awesome, great to hear that SimplePush will get a native support for a
>>> full message content.
>>>
>>> As Erik said, in the meantime, we could unify this behavior.
>>> I have created the associated issue:
>>> https://issues.jboss.org/browse/AGPUSH-1073
>>>
>>>
>>> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
>>> wrote:
>>>
>>>> Hi Luk??,
>>>>
>>>> I like that idea, because in the end our goal is to unify. And I think
>>>> that the simple push protocol will be changed in the future to allow
>>>> for ?normal? message sending. So we could fallback afterwards.
>>>>
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>>>>
>>>> Hey guys,
>>>>
>>>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
>>>> as Firefox OS using our Cordova plugin.
>>>>
>>>> But as you know, with FFOS it is not that simple - since SimplePush
>>>> protocol allows to transfer just incremental versions, we are not able to
>>>> deliver any interesting message.
>>>>
>>>> UnifiedPush Server could be a correct place where we unify and shield
>>>> our users from this limitation:
>>>>
>>>>
>>>> my idea is storing the message on UPS under the SimplePush endpoint
>>>> URL. Once the message with version reaches the client, he would contact UPS
>>>> to retrieve this message under a key ( pushEndpoint, version ).
>>>>
>>>> The messages could have default built-in TTL to allow periodic cleanup.
>>>>
>>>> What do you think?
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> ~ Lukas
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141020/358a7567/attachment-0001.html 

From cvasilak at gmail.com  Mon Oct 20 10:18:25 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 20 Oct 2014 17:18:25 +0300
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3GbV-MF-Kf6depMEokRv73=OopBTic=zsW6k87aPeOBTA@mail.gmail.com>
References: <CAFJm-3GbV-MF-Kf6depMEokRv73=OopBTic=zsW6k87aPeOBTA@mail.gmail.com>
Message-ID: <C1F095D3-959D-4506-BDE9-10811111DDC0@gmail.com>

fyi,

meeting minutes:

<jbott>	 Meeting ended Mon Oct 20 14:13:57 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-10-20-14.00.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-20-14.00.txt
 <jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-20-14.00.log.html


On Oct 18, 2014, at 3:37 PM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

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

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

From lukas.fryc at gmail.com  Mon Oct 20 10:18:51 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 20 Oct 2014 16:18:51 +0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <54451629.20704@gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<54451629.20704@gmail.com>
Message-ID: <CAEroY355-4ELXi9gbSS2GG302+jHS=3=ikS_Gvy6zKa27hidKA@mail.gmail.com>

You are right, guys, with storing the messages, we are hitting the security
implications that I didn't think about.

Right now they have to be handled by third-party providers, but in this
case, we would need to encrypt data, pass certification, etc, that is
rather a target for internal infrastructure than a cloud service.

We could probably come with an encryption model that would allow only given
SimplePush retrieve the message, involving client's private key and version
number, but question is whether that is worth the trouble and complexity.

On Mon, Oct 20, 2014 at 4:03 PM, jr conlin <jrconlin at gmail.com> wrote:

> FYI, Officially, the predecessor for SimplePush will be WebPush,
> https://datatracker.ietf.org/wg/webpush/charter/
> which runs on top of HTTP2
> http://http2.github.io/
>
> Unofficially, data is kind of a pain in the patootie, but obviously
> really handy to have. There are security and privacy issues a-plenty
> when dealing with data storage (HIPPA & subpoenas come to mind in the
> US.) Internally, we're kicking around the idea of allowing data, but not
> allowing storage, (so a device would only get data if it was actively
> connected. If it was offline, it would only get the version number
> update when it reconnected).
>
> I'm also interested in what y'all come up with.
>
> On 10/20/2014 4:58 AM, Luk?? Fry? wrote:
> > Hey guys,
> >
> > I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
> > as Firefox OS using our Cordova plugin.
> >
> > But as you know, with FFOS it is not that simple - since SimplePush
> > protocol allows to transfer just incremental versions, we are not able
> > to deliver any interesting message.
> >
> > UnifiedPush Server could be a correct place where we unify and shield
> > our users from this limitation:
> >
> >
> > my idea is storing the message on UPS under the SimplePush endpoint
> > URL. Once the message with version reaches the client, he would
> > contact UPS to retrieve this message under a key ( pushEndpoint,
> > version ).
> >
> > The messages could have default built-in TTL to allow periodic cleanup.
> >
> > What do you think?
> >
> >
> > Cheers,
> >
> > ~ Lukas
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/88950d1f/attachment.html 

From lholmqui at redhat.com  Mon Oct 20 10:36:34 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 20 Oct 2014 10:36:34 -0400
Subject: [aerogear-dev] AeroGear.js 2.0.0-beta1
In-Reply-To: <CAAg5f2TUTXxj8AyB8d07UCpO0+AYezO6aDeUTFurYczN6OJyPQ@mail.gmail.com>
References: <B85217D1-66D1-43AF-81C3-0B84DD1DAB74@redhat.com>
	<CAAg5f2TUTXxj8AyB8d07UCpO0+AYezO6aDeUTFurYczN6OJyPQ@mail.gmail.com>
Message-ID: <43A710C5-2CC9-422C-9AB0-4F82801CA9B8@redhat.com>


> On Oct 11, 2014, at 5:38 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> Sounds good!
> 
> regarding "Pipeline"  and "Authentication" do we have a doc that helps to migrate away?

currently no.  wondering if this should just be in the blog post,  or in something in the readme or on Aerogear.org

> 
> On Sat, Oct 11, 2014 at 4:01 AM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> The first beta release of AeroGear.js 2.0 <https://github.com/aerogear/aerogear-js/releases/tag/2.0.0-beta1> is out and ready for you to test it!
> 
> There's been a bunch of changes that could possibly break existing code as well as some things that have been removed.
> 
> Pipeline
> 
> It was deteremined that Pipeline and pipes did not add much value since it was basically a wrapper on top of jQuery Ajax.
> 
> So Pipeline and pipes have been completely removed in 2.0
> 
> If this was something that you used, they will still live on in the 1.X branch
> 
> Authentication
> 
> Similar to Pipeline, the Auth module didn't really add any value to the library, so this has also been removed.
> 
> Again It will live on in the 1.X branch
> 
> Datamanager
> 
> One of the big things that has changed in Datamanager is that it is no longer dependent on jQuery.
> 
> The other thing is that we have fully embraced es6 Promises. Which means we have removed callbacks.
> 
> For the IndexedDB and WebSQL adapters, the auto param has now been updated to default to true. This means that you no longer have to excplitly call open.
> 
> So instead of doing something like this:
> 
> idbStore.open(...).then(function () {
>     idbStore.read(...)
> });
> You can now just do
> 
> idbStore.read(...)
> Ajax Promises
> 
> We also updated the internal Ajax library to just use promises also.
> 
> This is used by both the UnifiedPush SDK and the Authz OAuth2 module.
> 
> Since ES6 promises only have 1 return value we return an object with this signature:
> 
> {
>     data: dataOrError, - the data or an error
>     statusText: statusText, - the status of the response
>     agXHR: request - the xhr request object
> };
> Cookbook Examples
> 
> The cookbook examples have also been updated with the 2.0.0 beta1 version and can be found in this branch <https://github.com/aerogear/aerogear-js-cookbook/tree/2-beta1>
> Integration Tests
> 
> Last but not least the Integration tests have been completly reworked, thanks to lfryc!!!
> 
> The PR's for these are https://github.com/aerogear/aerogear-js-integration/pull/12 <https://github.com/aerogear/aerogear-js-integration/pull/12>
> and
> 
> https://github.com/aerogear/aerogear-js/pull/150 <https://github.com/aerogear/aerogear-js/pull/150>
> Release Notes - AeroGear JavaScript - Version 2.0.0
> 
> Bug
> 
> [AGJS-184 <https://issues.jboss.org/browse/AGJS-184>] - Vertx and SimplePush integration tests execution issues
> Feature Request
> 
> [AGJS-201 <https://issues.jboss.org/browse/AGJS-201>] - XMLHttpRequest#response not implemented in Sinon.JS lib & authentication unit tests fail
> [AGJS-251 <https://issues.jboss.org/browse/AGJS-251>] - DataManager - Auto connect options should default to true
> Task
> 
> [AGJS-189 <https://issues.jboss.org/browse/AGJS-189>] - Review DevDependencies Versions
> [AGJS-211 <https://issues.jboss.org/browse/AGJS-211>] - Rework Integration Tests from the ground up
> [AGJS-228 <https://issues.jboss.org/browse/AGJS-228>] - Deprecate Pipeline
> [AGJS-229 <https://issues.jboss.org/browse/AGJS-229>] - Deprecate Authentication Module
> [AGJS-232 <https://issues.jboss.org/browse/AGJS-232>] - Remove AeroGear.isArray method from core
> [AGJS-233 <https://issues.jboss.org/browse/AGJS-233>] - Remove pipeline integration tests
> [AGJS-234 <https://issues.jboss.org/browse/AGJS-234>] - Promisify Library
> [AGJS-242 <https://issues.jboss.org/browse/AGJS-242>] - Update cookbook examples with deprecation notices, etc...
> [AGJS-248 <https://issues.jboss.org/browse/AGJS-248>] - Move the SimplePush and UnifiedPush examples to the real js-cookbook
> Sub-task
> 
> [AGJS-42 <https://issues.jboss.org/browse/AGJS-42>] - Remove jQuery dependency from DataManager; embrace Promises instead
> [AGJS-162 <https://issues.jboss.org/browse/AGJS-162>] - Remove jQuery Dependency from Auth
> [AGJS-212 <https://issues.jboss.org/browse/AGJS-212>] - Update to express 4
> [AGJS-231 <https://issues.jboss.org/browse/AGJS-231>] - Update Authz cookbook example without pipeline
> [AGJS-235 <https://issues.jboss.org/browse/AGJS-235>] - Promisify Datamanager
> [AGJS-236 <https://issues.jboss.org/browse/AGJS-236>] - Promisfy Crypto
> [AGJS-237 <https://issues.jboss.org/browse/AGJS-237>] - Promisfy Notifier
> [AGJS-238 <https://issues.jboss.org/browse/AGJS-238>] - Promisfy UnifiedPush client
> [AGJS-239 <https://issues.jboss.org/browse/AGJS-239>] - Promisfy Authorization
> [AGJS-240 <https://issues.jboss.org/browse/AGJS-240>] - Promisfy SimplePush
> [AGJS-243 <https://issues.jboss.org/browse/AGJS-243>] - Add deprecation Notice for Pipeline Cookbook example
> [AGJS-244 <https://issues.jboss.org/browse/AGJS-244>] - Add deprecation notice on Auth cookbook example
> [AGJS-245 <https://issues.jboss.org/browse/AGJS-245>] - Promisify AeroGear.ajax
> [AGJS-246 <https://issues.jboss.org/browse/AGJS-246>] - Update unified push example to use just promises
> [AGJS-247 <https://issues.jboss.org/browse/AGJS-247>] - Update Datamanager example to use promises not callbacks
> 
> 
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141020/47703955/attachment-0001.html 

From jrconlin at gmail.com  Mon Oct 20 11:28:11 2014
From: jrconlin at gmail.com (JR Conlin)
Date: Mon, 20 Oct 2014 08:28:11 -0700
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY355-4ELXi9gbSS2GG302+jHS=3=ikS_Gvy6zKa27hidKA@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>	<54451629.20704@gmail.com>
	<CAEroY355-4ELXi9gbSS2GG302+jHS=3=ikS_Gvy6zKa27hidKA@mail.gmail.com>
Message-ID: <54452A0B.6060600@gmail.com>

Heh, even that can be tricky. Generally, people will get encryption
wrong. Plus, the encrypted data block will (at least ideally) be an
indecipherable bunch of random bytes. That means that the server should
not be able to read it, or confirm that the data was actually encrypted.
Sadly, this means that someone could "encrypt" with ROT13 and the server
couldn't really verify. Then there's the problem of key distribution,
which is an absolute nightmare to do properly.

The reason that we have version (and I'll be honest, I kinda fought that
for a pretty long time too) is because it's the very least amount of
meaningful data that can be exchanged between two parties via a third
without too many issues.

I'm not a lawyer, nor do I play one on TV, nor do I even pretend to
understand international law, but I can tell you that various global
government agencies can require networks to provide anything from data
dumps to "pen registry" devices (a device that records all data
exchanges), often under orders to not disclose the fact that these
devices have occurred. For some sites, that's just the cost of doing
business, but also explains why the paranoid prefer sites like SpiderOak
(which does a fantastic job making damn sure that they can't read your
data at all).

I'll also be honest, for Mozilla, not handling data is VERY cost
effective. Not dealing with data makes things scale amazingly well for
astoundingly little, so we're doubly inclined to make data "someone
else's problem".

Ultimately, though, our customers are the ones that make the decision
about whether or not Data is worth all this. They've pretty much said
that they want data. We're trying  to balance that within the WebPush
protocol, and by making data optional and disposable within SimplePush. 
(Again, nothing 100% there, we're still debating it internally.) It's
also possible to do secure data exchange between parties using zero
knowledge key exchanges via things like JPAKE, but customer acceptance
of that sort of thing can be difficult.

Still, more brains == better things, so if there's a brilliant, as yet
undiscovered solution out there, it's definitely worth thinking about.

On 2014/10/20 7:18 AM, Luk?? Fry? wrote:
> You are right, guys, with storing the messages, we are hitting the
> security implications that I didn't think about.
>
> Right now they have to be handled by third-party providers, but in
> this case, we would need to encrypt data, pass certification, etc,
> that is rather a target for internal infrastructure than a cloud service.
>
> We could probably come with an encryption model that would allow only
> given SimplePush retrieve the message, involving client's private key
> and version number, but question is whether that is worth the trouble
> and complexity.
>
> On Mon, Oct 20, 2014 at 4:03 PM, jr conlin <jrconlin at gmail.com
> <mailto:jrconlin at gmail.com>> wrote:
>
>     FYI, Officially, the predecessor for SimplePush will be WebPush,
>     https://datatracker.ietf.org/wg/webpush/charter/
>     which runs on top of HTTP2
>     http://http2.github.io/
>
>     Unofficially, data is kind of a pain in the patootie, but obviously
>     really handy to have. There are security and privacy issues a-plenty
>     when dealing with data storage (HIPPA & subpoenas come to mind in the
>     US.) Internally, we're kicking around the idea of allowing data,
>     but not
>     allowing storage, (so a device would only get data if it was actively
>     connected. If it was offline, it would only get the version number
>     update when it reconnected).
>
>     I'm also interested in what y'all come up with.
>
>     On 10/20/2014 4:58 AM, Luk?? Fry? wrote:
>     > Hey guys,
>     >
>     > I'm working on a demo of UPS pushing to iOS, Android, Windows,
>     as well
>     > as Firefox OS using our Cordova plugin.
>     >
>     > But as you know, with FFOS it is not that simple - since SimplePush
>     > protocol allows to transfer just incremental versions, we are
>     not able
>     > to deliver any interesting message.
>     >
>     > UnifiedPush Server could be a correct place where we unify and
>     shield
>     > our users from this limitation:
>     >
>     >
>     > my idea is storing the message on UPS under the SimplePush endpoint
>     > URL. Once the message with version reaches the client, he would
>     > contact UPS to retrieve this message under a key ( pushEndpoint,
>     > version ).
>     >
>     > The messages could have default built-in TTL to allow periodic
>     cleanup.
>     >
>     > What do you think?
>     >
>     >
>     > Cheers,
>     >
>     > ~ Lukas
>     >
>     >
>     > _______________________________________________
>     > 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
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/7a31fa5e/attachment.html 

From cvasilak at gmail.com  Mon Oct 20 11:59:22 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 20 Oct 2014 18:59:22 +0300
Subject: [aerogear-dev] Announcing AeroGear-iOS 2.0
Message-ID: <E20AB48E-BAB8-466E-952C-E0A9705AC715@gmail.com>

Hi all,

today we are proud to announce AeroGear-iOS 2.0 codename ?Swift?. It was not long time ago, at WWDC 2014, where Apple announced the Swift programming language and took developers by surprise, and for a good reason. It provides a modern and familiar syntax that borrows proven concepts from various languages (including functional ones). Developers who were reluctant to try objective-c because of it?s C and C++ heritage and it?s somehow ?obscure' syntax, now have a reason to look again (and judging from their responses liked what they saw)

As apple stated in their blog [1]

"Swift is ready to use today, in brand new apps or alongside your proven Objective-C code. We have big plans for the Swift language, including improvements to syntax, and powerful new features..?

We immediately understood the importance of the new language and jumped in. Today we are releasing the first 'fruits' of our endeavour, and in particular:

- aerogear-ios-http [2]
  A networking library built on top of NSURLSession offering a convenient API for accessing RESTful services, performing download/upload (including multipart) as well as extension points to provide your own serialisers for request / response (with JSON serialisers be the default)
- aerogear-ios-oauth2 [3]
 An OAuth2 module build on top of 'aerogear-ios-http?  supporting common providers such as Google, Facebook and our own JBoss solution Keycloak[4] . A pluggable system is also provided so external developers you plug-in their own support for their favorite provider. You can read more of this integration (including a screencast) on the excellent blog post written from my friend Corinne [5]
-aerogear-ios-push [7]
 If you are using AeroGear Unified Push Server[8] and our iOS push-sdk in your objective-c applications, we are happy to announce that we have ported the SDK to Swift including all our demos[9] and quick starts[10]. No more messing with 'Bridging Headers' and the like. Just drag and drop the framework in your own application and you are ready to go.
-aerogear-ios-httpstub [11]
A handy networking stub library written entirely in swift developed to support our efforts, but it can be possible proved useful in your own projects too.

Now, regarding our 1.6.x branch of aerogear-ios we have decided to cease the development of that branch (apart from critical bug fixes) and focus all our efforts in porting the libraries to Swift. Already the base functionality has been ported (and hopefully improved) but we still have a long way to go. Most importantly our OTP and Crypto functionality libraries haven?t been ported yet (but we are planning to), but still they are useful on their own right in your objective-c projects (or in Swift if you decide to go with a mixed environment)

Last but not least,
Swift as a language is improving rapidly and only recently has been tagged as an 1.0 release[12]. Real world usage though showed that still has a long way to go. As an iOS team though we will work hard to update our ?current? and ?future? libraries with latest developments so expect to see frequent releases in that front.

So give our libraries and demos[13] a try, we will be happy to hear your thoughts and suggestions.

Enjoy!

++
Corinne && Christos


[1] https://developer.apple.com/swift/blog/?id=2
[2] https://github.com/aerogear/aerogear-ios-http/tree/0.1
[3] https://github.com/aerogear/aerogear-ios-oauth2/tree/0.1
[4] http://keycloak.jboss.org
[5] http://corinnekrych.org/2014/10/aerogear-with-keycloak-oauth2-friends.html
[7] https://github.com/aerogear/aerogear-ios-push/zipball/2.0.0
[8] http://aerogear.org/push/
[9] https://github.com/aerogear/aerogear-push-helloworld/tree/swift/ios-swift
[10] https://github.com/aerogear/aerogear-push-quickstarts/tree/swift
[11] https://github.com/aerogear/aerogear-ios-httpstub/tree/0.1
[12] https://developer.apple.com/swift/blog/?id=14
[13] https://github.com/aerogear/aerogear-ios-cookbook
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/1cce6afc/attachment.html 

From lholmqui at redhat.com  Mon Oct 20 12:03:06 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 20 Oct 2014 12:03:06 -0400
Subject: [aerogear-dev] Announcing AeroGear-iOS 2.0
In-Reply-To: <E20AB48E-BAB8-466E-952C-E0A9705AC715@gmail.com>
References: <E20AB48E-BAB8-466E-952C-E0A9705AC715@gmail.com>
Message-ID: <0963B3BF-B942-4C83-AC94-CF5A5E8CF32D@redhat.com>

Awesome!!
> On Oct 20, 2014, at 11:59 AM, Christos Vasilakis <cvasilak at gmail.com> wrote:
> 
> Hi all,
> 
> today we are proud to announce AeroGear-iOS 2.0 codename ?Swift?. It was not long time ago, at WWDC 2014, where Apple announced the Swift programming language and took developers by surprise, and for a good reason. It provides a modern and familiar syntax that borrows proven concepts from various languages (including functional ones). Developers who were reluctant to try objective-c because of it?s C and C++ heritage and it?s somehow ?obscure' syntax, now have a reason to look again (and judging from their responses liked what they saw)
> 
> As apple stated in their blog [1]
> 
> "Swift is ready to use today, in brand new apps or alongside your proven Objective-C code. We have big plans for the Swift language, including improvements to syntax, and powerful new features..?
> 
> We immediately understood the importance of the new language and jumped in. Today we are releasing the first 'fruits' of our endeavour, and in particular:
> 
> - aerogear-ios-http [2]
>   A networking library built on top of NSURLSession offering a convenient API for accessing RESTful services, performing download/upload (including multipart) as well as extension points to provide your own serialisers for request / response (with JSON serialisers be the default)
> - aerogear-ios-oauth2 [3]
>  An OAuth2 module build on top of 'aerogear-ios-http?  supporting common providers such as Google, Facebook and our own JBoss solution Keycloak[4] . A pluggable system is also provided so external developers you plug-in their own support for their favorite provider. You can read more of this integration (including a screencast) on the excellent blog post written from my friend Corinne [5]
> -aerogear-ios-push [7]
>  If you are using AeroGear Unified Push Server[8] and our iOS push-sdk in your objective-c applications, we are happy to announce that we have ported the SDK to Swift including all our demos[9] and quick starts[10]. No more messing with 'Bridging Headers' and the like. Just drag and drop the framework in your own application and you are ready to go.
> -aerogear-ios-httpstub [11]
> A handy networking stub library written entirely in swift developed to support our efforts, but it can be possible proved useful in your own projects too.
> 
> Now, regarding our 1.6.x branch of aerogear-ios we have decided to cease the development of that branch (apart from critical bug fixes) and focus all our efforts in porting the libraries to Swift. Already the base functionality has been ported (and hopefully improved) but we still have a long way to go. Most importantly our OTP and Crypto functionality libraries haven?t been ported yet (but we are planning to), but still they are useful on their own right in your objective-c projects (or in Swift if you decide to go with a mixed environment)
> 
> Last but not least,
> Swift as a language is improving rapidly and only recently has been tagged as an 1.0 release[12]. Real world usage though showed that still has a long way to go. As an iOS team though we will work hard to update our ?current? and ?future? libraries with latest developments so expect to see frequent releases in that front.
> 
> So give our libraries and demos[13] a try, we will be happy to hear your thoughts and suggestions.
> 
> Enjoy!
> 
> ++
> Corinne && Christos
> 
> 
> [1] https://developer.apple.com/swift/blog/?id=2 <https://developer.apple.com/swift/blog/?id=2>
> [2] https://github.com/aerogear/aerogear-ios-http/tree/0.1 <https://github.com/aerogear/aerogear-ios-http/tree/0.1>
> [3] https://github.com/aerogear/aerogear-ios-oauth2/tree/0.1 <https://github.com/aerogear/aerogear-ios-oauth2/tree/0.1>
> [4] http://keycloak.jboss.org <http://keycloak.jboss.org/>
> [5] http://corinnekrych.org/2014/10/aerogear-with-keycloak-oauth2-friends.html <http://corinnekrych.org/2014/10/aerogear-with-keycloak-oauth2-friends.html>
> [7] https://github.com/aerogear/aerogear-ios-push/zipball/2.0.0 <https://github.com/aerogear/aerogear-ios-push/zipball/2.0.0>
> [8] http://aerogear.org/push/ <http://aerogear.org/push/>
> [9] https://github.com/aerogear/aerogear-push-helloworld/tree/swift/ios-swift <https://github.com/aerogear/aerogear-push-helloworld/tree/swift/ios-swift>
> [10] https://github.com/aerogear/aerogear-push-quickstarts/tree/swift <https://github.com/aerogear/aerogear-push-quickstarts/tree/swift>
> [11] https://github.com/aerogear/aerogear-ios-httpstub/tree/0.1 <https://github.com/aerogear/aerogear-ios-httpstub/tree/0.1>
> [12] https://developer.apple.com/swift/blog/?id=14 <https://developer.apple.com/swift/blog/?id=14>
> [13] https://github.com/aerogear/aerogear-ios-cookbook <https://github.com/aerogear/aerogear-ios-cookbook>_______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From daniel.bevenius at gmail.com  Mon Oct 20 14:01:06 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 20 Oct 2014 20:01:06 +0200
Subject: [aerogear-dev] Announcing AeroGear-iOS 2.0
In-Reply-To: <0963B3BF-B942-4C83-AC94-CF5A5E8CF32D@redhat.com>
References: <E20AB48E-BAB8-466E-952C-E0A9705AC715@gmail.com>
	<0963B3BF-B942-4C83-AC94-CF5A5E8CF32D@redhat.com>
Message-ID: <CAFJm-3F+YFLP4xACENTObRpQUycp9Y9keVbUf=Eb056D84ZVNQ@mail.gmail.com>

Great work!

On 20 October 2014 18:03, Lucas Holmquist <lholmqui at redhat.com> wrote:

> Awesome!!
>
> On Oct 20, 2014, at 11:59 AM, Christos Vasilakis <cvasilak at gmail.com>
> wrote:
>
> Hi all,
>
> today we are proud to announce AeroGear-iOS 2.0 codename ?Swift?. It was
> not long time ago, at WWDC 2014, where Apple announced the Swift
> programming language and took developers by surprise, and for a good
> reason. It provides a modern and familiar syntax that borrows proven
> concepts from various languages (including functional ones). Developers who
> were reluctant to try objective-c because of it?s C and C++ heritage and
> it?s somehow ?obscure' syntax, now have a reason to look again (and judging
> from their responses liked what they saw)
>
> As apple stated in their blog [1]
>
> *"Swift is ready to use today, in brand new apps or alongside your proven
> Objective-C code. We have big plans for the Swift language, including
> improvements to syntax, and powerful new features..?*
>
> We immediately understood the importance of the new language and jumped
> in. Today we are releasing the first 'fruits' of our endeavour, and in
> particular:
>
> - *aerogear-ios-http* [2]
>   A networking library built on top of NSURLSession offering a convenient
> API for accessing RESTful services, performing download/upload (including
> multipart) as well as extension points to provide your own serialisers for
> request / response (with JSON serialisers be the default)
> - *aerogear-ios-oauth2 *[3]
>  An OAuth2 module build on top of 'aerogear-ios-http?  supporting common
> providers such as Google, Facebook and our own JBoss solution Keycloak[4] .
> A pluggable system is also provided so external developers you plug-in
> their own support for their favorite provider. You can read more of this
> integration (including a screencast) on the excellent blog post written
> from my friend Corinne [5]
> -*aerogear-ios-push [7]*
>  If you are using AeroGear Unified Push Server[8] and our iOS push-sdk in
> your objective-c applications, we are happy to announce that we have ported
> the SDK to Swift including all our demos[9] and quick starts[10]. No more
> messing with 'Bridging Headers' and the like. Just drag and drop the
> framework in your own application and you are ready to go.
> -*aerogear-ios-httpstub [11]*
> A handy networking stub library written entirely in swift developed to
> support our efforts, but it can be possible proved useful in your own
> projects too.
>
> Now, regarding our 1.6.x branch of aerogear-ios we have decided to cease
> the development of that branch (apart from critical bug fixes) and focus
> all our efforts in porting the libraries to Swift. Already the base
> functionality has been ported (and hopefully improved) but we still have a
> long way to go. Most importantly our OTP and Crypto functionality libraries
> haven?t been ported yet (but we are planning to), but still they are useful
> on their own right in your objective-c projects (or in Swift if you decide
> to go with a mixed environment)
>
> Last but not least,
> Swift as a language is improving rapidly and only recently has been tagged
> as an 1.0 release[12]. Real world usage though showed that still has a long
> way to go. As an iOS team though we will work hard to update our ?current?
> and ?future? libraries with latest developments so expect to see frequent
> releases in that front.
>
> So give our libraries and demos[13] a try, we will be happy to hear your
> thoughts and suggestions.
>
> Enjoy!
>
> ++
> Corinne && Christos
>
>
> [1] https://developer.apple.com/swift/blog/?id=2
> [2] https://github.com/aerogear/aerogear-ios-http/tree/0.1
> [3] https://github.com/aerogear/aerogear-ios-oauth2/tree/0.1
> [4] http://keycloak.jboss.org
> [5]
> http://corinnekrych.org/2014/10/aerogear-with-keycloak-oauth2-friends.html
> [7] https://github.com/aerogear/aerogear-ios-push/zipball/2.0.0
> [8] http://aerogear.org/push/
> [9]
> https://github.com/aerogear/aerogear-push-helloworld/tree/swift/ios-swift
> [10] https://github.com/aerogear/aerogear-push-quickstarts/tree/swift
> [11] https://github.com/aerogear/aerogear-ios-httpstub/tree/0.1
> [12] https://developer.apple.com/swift/blog/?id=14
> [13] https://github.com/aerogear/aerogear-ios-cookbook
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141020/149efbfa/attachment.html 

From daniel at passos.me  Mon Oct 20 18:01:25 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 20 Oct 2014 20:01:25 -0200
Subject: [aerogear-dev] Problems to setup UPS
Message-ID: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>

Hey Guys,

Today I?ve spend a lot of time (without success), trying test #408
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/408> using a
new JBoss AS 7.1/Wildfly 8.1.0 installations
Using Java version ?1.7.0_45?
------------------------------
JBoss AS 7.1 Generate the UnifiedPush Database and Datasource

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
--file=../databases/h2-database-config.cli
#1 data-source add --name=UnifiedPushDS --driver-name=h2
--jndi-name=java:jboss/datasources/UnifiedPushDS
--connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
--user-name=sa --password=sa --use-ccm=true
#2 data-source enable --name=UnifiedPushDS
The batch executed successfully.

Deployment

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? mvn jboss-as:deploy -Pas7

Server Log

19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-8) MSC00001: Failed to start service
jboss.deployment.unit."ag-push.war".WeldService:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."ag-push.war".WeldService:
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
dependencies for type [HttpServletRequest] with qualifiers [@Default]
at injection point [[parameter 1] of [constructor] @Inject public
org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
    at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
[@Default] at injection point [[parameter 1] of [constructor] @Inject
public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
    at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
    at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
    ... 5 more

Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
--file=../databases/h2-database-config.cli
The batch failed with the following error (you are remaining in the
batch editing mode to have a chance to correct the error):
{"JBAS014653: Composite operation failed and was rolled back. Steps
that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
failed: Service jboss.data-source-config.UnifiedPushDS is already
registered"}}

Server Log

19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
(MSC service thread 1-2) JBAS010400: Bound data source
[java:jboss/datasources/UnifiedPushDS]
19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 1) JBAS014612: Operation ("add") failed -
address: ([
    ("subsystem" => "datasources"),
    ("data-source" => "UnifiedPushDS")
]): org.jboss.msc.service.DuplicateServiceException: Service
jboss.data-source-config.UnifiedPushDS is already registered
    at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
    at org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at java.security.AccessController.doPrivileged(Native Method)
[rt.jar:1.7.0_45]
    at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_45]
    at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
[wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
[wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.1.1.Final.jar:2.1.1.Final]

19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
(MSC service thread 1-7) JBAS010409: Unbound data source
[java:jboss/datasources/UnifiedPushDS]

Deployment

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? mvn wildfly:deploy -Pwildfly
.
.
.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] UnifiedPush Auth Server ........................... SUCCESS [10.217s]
[INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE [4.306s]
[INFO] UnifiedPush Servers Parent ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.561s
[INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
[INFO] Final Memory: 35M/367M
[INFO] ------------------------------------------------------------------------

Server Log

19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-4) MSC000001: Failed to start service
jboss.undertow.deployment.default-server.default-host./auth:
org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth: Failed to
start service
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.RuntimeException: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
    at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
    at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
    at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
    at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
    at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
    at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
    at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
    at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
    at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    ... 3 more
Caused by: javax.persistence.PersistenceException: Unable to build
entity manager factory
    at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
    at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
    at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
    at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
    at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
    at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
    at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
    at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
    at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
    at org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
    at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
    at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
    at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
    at org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
    at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
    at org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
    at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method) [rt.jar:1.7.0_45]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
[rt.jar:1.7.0_45]
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
[rt.jar:1.7.0_45]
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
[rt.jar:1.7.0_45]
    at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
    ... 15 more
Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
JNDI name [java:jboss/datasources/UnifiedPushDS]
    at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
    at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
    at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
    at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
    at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
    at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
    at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
    at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
    at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
    ... 36 more
Caused by: javax.naming.NameNotFoundException:
datasources/UnifiedPushDS -- service
jboss.naming.context.java.jboss.datasources.UnifiedPushDS
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
    at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
    at javax.naming.InitialContext.lookup(InitialContext.java:415)
[rt.jar:1.7.0_45]
    at javax.naming.InitialContext.lookup(InitialContext.java:415)
[rt.jar:1.7.0_45]
    at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
    ... 52 more

19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 1) JBAS014613: Operation ("deploy")
failed - address: ([("deployment" => "auth-server.war")]) - failure
description: {"JBAS014671: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./auth" =>
"org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth: Failed to
start service
    Caused by: java.lang.RuntimeException: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
    Caused by: javax.persistence.PersistenceException: Unable to build
entity manager factory
    Caused by: org.hibernate.engine.jndi.JndiException: Unable to
lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
    Caused by: javax.naming.NameNotFoundException:
datasources/UnifiedPushDS -- service
jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
with the following failure message:
{"JBAS014671: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./auth" =>
"org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth: Failed to
start service
    Caused by: java.lang.RuntimeException: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
    Caused by: javax.persistence.PersistenceException: Unable to build
entity manager factory
    Caused by: org.hibernate.engine.jndi.JndiException: Unable to
lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
    Caused by: javax.naming.NameNotFoundException:
datasources/UnifiedPushDS -- service
jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}

Using java version ?1.8.0_25?
------------------------------
JBoss AS 7.1

I can not start JBoss AS 7.1 using Java 8

[passos]: ~
? ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
-b 0.0.0.0
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final

  JAVA: java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
-Djboss.server.default.config=standalone.xml

=========================================================================

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
"Brontes" starting

Wildfly 8.1.0 Deploy

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? mvn wildfly:deploy -Pwildfly

Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
deploy against EAP, but I'm not sure that matters given the error
looks to be JDK/path/version-based.
[ERROR] Failed to execute goal
org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
(deploy) on project switchyard-validate-xml: Execution deploy of goal
org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
one of its dependencies could not be resolved: Could not find artifact
sun.jdk:jconsole:jar:jdk at specified path
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
-> [Help 1]

I found the same problem in SwitchYard quickstart
<https://issues.jboss.org/browse/SWITCHYARD-2315>

? Passos
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141020/34f64efa/attachment-0001.html 

From bruno at abstractj.org  Mon Oct 20 22:02:08 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 21 Oct 2014 00:02:08 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
Message-ID: <20141021020208.GA15719@abstractj.org>

Good morning Passos, would you mind to try the following steps?

- WildFly 8.1.0

1. remove any previous installation of WildFly to make sure that we're
dealing with a fresh environment
2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
3. Start WildFly
4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
5. cp servers/auth-server/target/auth-server.war $JBOSS_HOME/standalone/deployments
6. cp servers/ups-wildfly/target/ag-push.war $JBOSS_HOME/standalone/deployments


Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
fresh setup.

I know manual deploy is not awesome, but help us to debug what's goign
on.

On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
this, thanks for testing.



On 2014-10-20, Daniel Passos wrote:
> Hey Guys,
>
> Today I?ve spend a lot of time (without success), trying test #408
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408> using a
> new JBoss AS 7.1/Wildfly 8.1.0 installations
> Using Java version ?1.7.0_45?
> ------------------------------
> JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> [git:pr/408]
> ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
> --file=../databases/h2-database-config.cli
> #1 data-source add --name=UnifiedPushDS --driver-name=h2
> --jndi-name=java:jboss/datasources/UnifiedPushDS
> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
> --user-name=sa --password=sa --use-ccm=true
> #2 data-source enable --name=UnifiedPushDS
> The batch executed successfully.
>
> Deployment
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> [git:pr/408]
> ? mvn jboss-as:deploy -Pas7
>
> Server Log
>
> 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
> 1-8) MSC00001: Failed to start service
> jboss.deployment.unit."ag-push.war".WeldService:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."ag-push.war".WeldService:
> org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
> dependencies for type [HttpServletRequest] with qualifiers [@Default]
> at injection point [[parameter 1] of [constructor] @Inject public
> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>     at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_45]
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [rt.jar:1.7.0_45]
>     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
> Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
> [@Default] at injection point [[parameter 1] of [constructor] @Inject
> public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>     at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>     at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>     at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>     at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>     at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>     at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>     at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>     at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>     ... 5 more
>
> Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> [git:pr/408]
> ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
> --file=../databases/h2-database-config.cli
> The batch failed with the following error (you are remaining in the
> batch editing mode to have a chance to correct the error):
> {"JBAS014653: Composite operation failed and was rolled back. Steps
> that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
> failed: Service jboss.data-source-config.UnifiedPushDS is already
> registered"}}
>
> Server Log
>
> 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
> (MSC service thread 1-2) JBAS010400: Bound data source
> [java:jboss/datasources/UnifiedPushDS]
> 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
> (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
> address: ([
>     ("subsystem" => "datasources"),
>     ("data-source" => "UnifiedPushDS")
> ]): org.jboss.msc.service.DuplicateServiceException: Service
> jboss.data-source-config.UnifiedPushDS is already registered
>     at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>     at org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>     at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at java.security.AccessController.doPrivileged(Native Method)
> [rt.jar:1.7.0_45]
>     at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_45]
>     at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
> [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
> [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>     at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
> [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_45]
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [rt.jar:1.7.0_45]
>     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>
> 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
> (MSC service thread 1-7) JBAS010409: Unbound data source
> [java:jboss/datasources/UnifiedPushDS]
>
> Deployment
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> [git:pr/408]
> ? mvn wildfly:deploy -Pwildfly
> .
> .
> .
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] UnifiedPush Auth Server ........................... SUCCESS [10.217s]
> [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE [4.306s]
> [INFO] UnifiedPush Servers Parent ........................ SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 15.561s
> [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
> [INFO] Final Memory: 35M/367M
> [INFO] ------------------------------------------------------------------------
>
> Server Log
>
> 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
> 1-4) MSC000001: Failed to start service
> jboss.undertow.deployment.default-server.default-host./auth:
> org.jboss.msc.service.StartException in service
> jboss.undertow.deployment.default-server.default-host./auth: Failed to
> start service
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_45]
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [rt.jar:1.7.0_45]
>     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.RuntimeException: Failed to construct public
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>     at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>     at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>     at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>     at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>     at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>     at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>     at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>     at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>     at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>     at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>     at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>     ... 3 more
> Caused by: javax.persistence.PersistenceException: Unable to build
> entity manager factory
>     at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>     at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>     at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>     at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>     at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>     at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>     at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>     at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>     at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>     at org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>     at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>     at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>     at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>     at org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>     at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>     at org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>     at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) [rt.jar:1.7.0_45]
>     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> [rt.jar:1.7.0_45]
>     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [rt.jar:1.7.0_45]
>     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> [rt.jar:1.7.0_45]
>     at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>     ... 15 more
> Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
> JNDI name [java:jboss/datasources/UnifiedPushDS]
>     at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>     at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>     at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>     at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>     at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>     at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>     at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>     at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>     at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>     at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>     at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>     at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>     at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>     at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>     at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>     at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>     at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>     ... 36 more
> Caused by: javax.naming.NameNotFoundException:
> datasources/UnifiedPushDS -- service
> jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>     at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>     at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>     at javax.naming.InitialContext.lookup(InitialContext.java:415)
> [rt.jar:1.7.0_45]
>     at javax.naming.InitialContext.lookup(InitialContext.java:415)
> [rt.jar:1.7.0_45]
>     at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>     ... 52 more
>
> 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
> (management-handler-thread - 1) JBAS014613: Operation ("deploy")
> failed - address: ([("deployment" => "auth-server.war")]) - failure
> description: {"JBAS014671: Failed services" =>
> {"jboss.undertow.deployment.default-server.default-host./auth" =>
> "org.jboss.msc.service.StartException in service
> jboss.undertow.deployment.default-server.default-host./auth: Failed to
> start service
>     Caused by: java.lang.RuntimeException: Failed to construct public
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>     Caused by: javax.persistence.PersistenceException: Unable to build
> entity manager factory
>     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
> lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>     Caused by: javax.naming.NameNotFoundException:
> datasources/UnifiedPushDS -- service
> jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
> 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
> 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
> with the following failure message:
> {"JBAS014671: Failed services" =>
> {"jboss.undertow.deployment.default-server.default-host./auth" =>
> "org.jboss.msc.service.StartException in service
> jboss.undertow.deployment.default-server.default-host./auth: Failed to
> start service
>     Caused by: java.lang.RuntimeException: Failed to construct public
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>     Caused by: javax.persistence.PersistenceException: Unable to build
> entity manager factory
>     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
> lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>     Caused by: javax.naming.NameNotFoundException:
> datasources/UnifiedPushDS -- service
> jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>
> Using java version ?1.8.0_25?
> ------------------------------
> JBoss AS 7.1
>
> I can not start JBoss AS 7.1 using Java 8
>
> [passos]: ~
> ? ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
> -b 0.0.0.0
> =========================================================================
>
>   JBoss Bootstrap Environment
>
>   JBOSS_HOME: /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>
>   JAVA: java
>
>   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
> -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
> -Dorg.jboss.resolver.warning=true
> -Dsun.rmi.dgc.client.gcInterval=3600000
> -Dsun.rmi.dgc.server.gcInterval=3600000
> -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> -Djboss.server.default.config=standalone.xml
>
> =========================================================================
>
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> MaxPermSize=256m; support was removed in 8.0
> 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
> 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
> "Brontes" starting
>
> Wildfly 8.1.0 Deploy
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> [git:pr/408]
> ? mvn wildfly:deploy -Pwildfly
>
> Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
> X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
> deploy against EAP, but I'm not sure that matters given the error
> looks to be JDK/path/version-based.
> [ERROR] Failed to execute goal
> org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
> (deploy) on project switchyard-validate-xml: Execution deploy of goal
> org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
> failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
> one of its dependencies could not be resolved: Could not find artifact
> sun.jdk:jconsole:jar:jdk at specified path
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
> -> [Help 1]
>
> I found the same problem in SwitchYard quickstart
> <https://issues.jboss.org/browse/SWITCHYARD-2315>
>
> ? Passos
> ?

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Tue Oct 21 04:12:03 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 10:12:03 +0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <20141021020208.GA15719@abstractj.org>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
Message-ID: <CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>

Hello passos,

regarding JBoss AS7.1 it's not really supported, especially after we added
a scheduler to 1.0.0.Final:
https://issues.jboss.org/browse/AS7-4694

Please use EAP 6.3.GA instead.

Also, I think they (EAP) do not support JDK8.

But yeah, on Wildfly Java8 is first-class citizens ;-)

greetings from Slovenia

On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning Passos, would you mind to try the following steps?
>
> - WildFly 8.1.0
>
> 1. remove any previous installation of WildFly to make sure that we're
> dealing with a fresh environment
> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
> 3. Start WildFly
> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
> 5. cp servers/auth-server/target/auth-server.war
> $JBOSS_HOME/standalone/deployments
> 6. cp servers/ups-wildfly/target/ag-push.war
> $JBOSS_HOME/standalone/deployments
>
>
> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
> fresh setup.
>
> I know manual deploy is not awesome, but help us to debug what's goign
> on.
>
> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
> this, thanks for testing.
>
>
>
> On 2014-10-20, Daniel Passos wrote:
> > Hey Guys,
> >
> > Today I?ve spend a lot of time (without success), trying test #408
> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
> using a
> > new JBoss AS 7.1/Wildfly 8.1.0 installations
> > Using Java version ?1.7.0_45?
> > ------------------------------
> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
> > --file=../databases/h2-database-config.cli
> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
> > --jndi-name=java:jboss/datasources/UnifiedPushDS
> >
> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
> > --user-name=sa --password=sa --use-ccm=true
> > #2 data-source enable --name=UnifiedPushDS
> > The batch executed successfully.
> >
> > Deployment
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? mvn jboss-as:deploy -Pas7
> >
> > Server Log
> >
> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
> > 1-8) MSC00001: Failed to start service
> > jboss.deployment.unit."ag-push.war".WeldService:
> > org.jboss.msc.service.StartException in service
> > jboss.deployment.unit."ag-push.war".WeldService:
> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
> > at injection point [[parameter 1] of [constructor] @Inject public
> >
> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> >     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > [rt.jar:1.7.0_45]
> >     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > [rt.jar:1.7.0_45]
> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
> > public
> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
> >     at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
> >     at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
> >     at
> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
> >     at
> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
> >     at
> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
> >     at
> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
> >     at
> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> >     ... 5 more
> >
> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
> > --file=../databases/h2-database-config.cli
> > The batch failed with the following error (you are remaining in the
> > batch editing mode to have a chance to correct the error):
> > {"JBAS014653: Composite operation failed and was rolled back. Steps
> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
> > failed: Service jboss.data-source-config.UnifiedPushDS is already
> > registered"}}
> >
> > Server Log
> >
> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
> > (MSC service thread 1-2) JBAS010400: Bound data source
> > [java:jboss/datasources/UnifiedPushDS]
> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
> > address: ([
> >     ("subsystem" => "datasources"),
> >     ("data-source" => "UnifiedPushDS")
> > ]): org.jboss.msc.service.DuplicateServiceException: Service
> > jboss.data-source-config.UnifiedPushDS is already registered
> >     at
> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
> >     at
> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
> >     at
> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at java.security.AccessController.doPrivileged(Native Method)
> > [rt.jar:1.7.0_45]
> >     at javax.security.auth.Subject.doAs(Subject.java:415)
> [rt.jar:1.7.0_45]
> >     at
> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
> >     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > [rt.jar:1.7.0_45]
> >     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > [rt.jar:1.7.0_45]
> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> >
> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
> > (MSC service thread 1-7) JBAS010409: Unbound data source
> > [java:jboss/datasources/UnifiedPushDS]
> >
> > Deployment
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? mvn wildfly:deploy -Pwildfly
> > .
> > .
> > .
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
> [10.217s]
> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
> [4.306s]
> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Total time: 15.561s
> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
> > [INFO] Final Memory: 35M/367M
> > [INFO]
> ------------------------------------------------------------------------
> >
> > Server Log
> >
> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
> > 1-4) MSC000001: Failed to start service
> > jboss.undertow.deployment.default-server.default-host./auth:
> > org.jboss.msc.service.StartException in service
> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
> > start service
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > [rt.jar:1.7.0_45]
> >     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > [rt.jar:1.7.0_45]
> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> > Caused by: java.lang.RuntimeException: Failed to construct public
> >
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
> >     at
> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
> >     at
> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
> >     at
> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
> >     at
> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
> >     at
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
> >     at
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
> >     at
> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
> >     at
> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
> >     at
> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
> >     at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
> >     at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     ... 3 more
> > Caused by: javax.persistence.PersistenceException: Unable to build
> > entity manager factory
> >     at
> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
> >     at
> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
> >     at
> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
> >     at
> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
> >     at
> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
> >     at
> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
> >     at
> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
> >     at
> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
> >     at
> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
> >     at
> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
> >     at
> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
> >     at
> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
> >     at
> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
> >     at
> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
> >     at
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
> >     at
> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
> >     at
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > Method) [rt.jar:1.7.0_45]
> >     at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> > [rt.jar:1.7.0_45]
> >     at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> > [rt.jar:1.7.0_45]
> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> > [rt.jar:1.7.0_45]
> >     at
> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
> >     ... 15 more
> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
> > JNDI name [java:jboss/datasources/UnifiedPushDS]
> >     at
> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
> >     at
> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
> >     at
> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
> >     at
> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
> >     at
> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
> >     at
> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
> >     at
> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
> >     at
> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> >     at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
> >     at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
> >     at
> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
> >     at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
> >     at
> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
> >     ... 36 more
> > Caused by: javax.naming.NameNotFoundException:
> > datasources/UnifiedPushDS -- service
> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
> >     at
> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
> >     at
> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
> > [rt.jar:1.7.0_45]
> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
> > [rt.jar:1.7.0_45]
> >     at
> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
> >     ... 52 more
> >
> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
> > failed - address: ([("deployment" => "auth-server.war")]) - failure
> > description: {"JBAS014671: Failed services" =>
> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
> > "org.jboss.msc.service.StartException in service
> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
> > start service
> >     Caused by: java.lang.RuntimeException: Failed to construct public
> >
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
> >     Caused by: javax.persistence.PersistenceException: Unable to build
> > entity manager factory
> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
> >     Caused by: javax.naming.NameNotFoundException:
> > datasources/UnifiedPushDS -- service
> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
> > with the following failure message:
> > {"JBAS014671: Failed services" =>
> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
> > "org.jboss.msc.service.StartException in service
> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
> > start service
> >     Caused by: java.lang.RuntimeException: Failed to construct public
> >
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
> >     Caused by: javax.persistence.PersistenceException: Unable to build
> > entity manager factory
> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
> >     Caused by: javax.naming.NameNotFoundException:
> > datasources/UnifiedPushDS -- service
> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
> >
> > Using java version ?1.8.0_25?
> > ------------------------------
> > JBoss AS 7.1
> >
> > I can not start JBoss AS 7.1 using Java 8
> >
> > [passos]: ~
> > ? ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
> > -b 0.0.0.0
> > =========================================================================
> >
> >   JBoss Bootstrap Environment
> >
> >   JBOSS_HOME:
> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
> >
> >   JAVA: java
> >
> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
> > -Dorg.jboss.resolver.warning=true
> > -Dsun.rmi.dgc.client.gcInterval=3600000
> > -Dsun.rmi.dgc.server.gcInterval=3600000
> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> > -Djboss.server.default.config=standalone.xml
> >
> > =========================================================================
> >
> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> > MaxPermSize=256m; support was removed in 8.0
> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
> > "Brontes" starting
> >
> > Wildfly 8.1.0 Deploy
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? mvn wildfly:deploy -Pwildfly
> >
> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
> > deploy against EAP, but I'm not sure that matters given the error
> > looks to be JDK/path/version-based.
> > [ERROR] Failed to execute goal
> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
> > one of its dependencies could not be resolved: Could not find artifact
> > sun.jdk:jconsole:jar:jdk at specified path
> >
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
> > -> [Help 1]
> >
> > I found the same problem in SwitchYard quickstart
> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
> >
> > ? Passos
> > ?
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev




-- 
Matthias Wessendorf

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

From daniel at passos.me  Tue Oct 21 07:14:58 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 21 Oct 2014 09:14:58 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <20141021020208.GA15719@abstractj.org>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
Message-ID: <CAKjsGbtNL7ac63DG7j-Wd5OgDOybuOGxDjvyEnTGHAdK=QZG-Q@mail.gmail.com>

On Tue, Oct 21, 2014 at 12:02 AM, Bruno Oliveira <bruno at abstractj.org>
wrote:

> Good morning Passos, would you mind to try the following steps?
>
> - WildFly 8.1.0
>
> 1. remove any previous installation of WildFly to make sure that we're
> dealing with a fresh environment
> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
> 3. Start WildFly
> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
> 5. cp servers/auth-server/target/auth-server.war
> $JBOSS_HOME/standalone/deployments
> 6. cp servers/ups-wildfly/target/ag-push.war
> $JBOSS_HOME/standalone/deployments
>
>
> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
> fresh setup.
>
> I know manual deploy is not awesome, but help us to debug what's goign
> on.
>

It works


> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
> this, thanks for testing.
>
>
>
> On 2014-10-20, Daniel Passos wrote:
> > Hey Guys,
> >
> > Today I?ve spend a lot of time (without success), trying test #408
> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
> using a
> > new JBoss AS 7.1/Wildfly 8.1.0 installations
> > Using Java version ?1.7.0_45?
> > ------------------------------
> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
> > --file=../databases/h2-database-config.cli
> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
> > --jndi-name=java:jboss/datasources/UnifiedPushDS
> >
> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
> > --user-name=sa --password=sa --use-ccm=true
> > #2 data-source enable --name=UnifiedPushDS
> > The batch executed successfully.
> >
> > Deployment
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? mvn jboss-as:deploy -Pas7
> >
> > Server Log
> >
> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
> > 1-8) MSC00001: Failed to start service
> > jboss.deployment.unit."ag-push.war".WeldService:
> > org.jboss.msc.service.StartException in service
> > jboss.deployment.unit."ag-push.war".WeldService:
> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
> > at injection point [[parameter 1] of [constructor] @Inject public
> >
> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> >     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > [rt.jar:1.7.0_45]
> >     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > [rt.jar:1.7.0_45]
> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
> > public
> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
> >     at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
> >     at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
> >     at
> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
> >     at
> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
> >     at
> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
> >     at
> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
> >     at
> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> >     ... 5 more
> >
> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
> > --file=../databases/h2-database-config.cli
> > The batch failed with the following error (you are remaining in the
> > batch editing mode to have a chance to correct the error):
> > {"JBAS014653: Composite operation failed and was rolled back. Steps
> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
> > failed: Service jboss.data-source-config.UnifiedPushDS is already
> > registered"}}
> >
> > Server Log
> >
> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
> > (MSC service thread 1-2) JBAS010400: Bound data source
> > [java:jboss/datasources/UnifiedPushDS]
> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
> > address: ([
> >     ("subsystem" => "datasources"),
> >     ("data-source" => "UnifiedPushDS")
> > ]): org.jboss.msc.service.DuplicateServiceException: Service
> > jboss.data-source-config.UnifiedPushDS is already registered
> >     at
> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
> >     at
> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
> >     at
> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at java.security.AccessController.doPrivileged(Native Method)
> > [rt.jar:1.7.0_45]
> >     at javax.security.auth.Subject.doAs(Subject.java:415)
> [rt.jar:1.7.0_45]
> >     at
> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
> >     at
> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
> >     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > [rt.jar:1.7.0_45]
> >     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > [rt.jar:1.7.0_45]
> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> >
> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
> > (MSC service thread 1-7) JBAS010409: Unbound data source
> > [java:jboss/datasources/UnifiedPushDS]
> >
> > Deployment
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? mvn wildfly:deploy -Pwildfly
> > .
> > .
> > .
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
> [10.217s]
> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
> [4.306s]
> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Total time: 15.561s
> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
> > [INFO] Final Memory: 35M/367M
> > [INFO]
> ------------------------------------------------------------------------
> >
> > Server Log
> >
> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
> > 1-4) MSC000001: Failed to start service
> > jboss.undertow.deployment.default-server.default-host./auth:
> > org.jboss.msc.service.StartException in service
> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
> > start service
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > [rt.jar:1.7.0_45]
> >     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > [rt.jar:1.7.0_45]
> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> > Caused by: java.lang.RuntimeException: Failed to construct public
> >
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
> >     at
> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
> >     at
> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
> >     at
> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
> >     at
> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
> >     at
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
> >     at
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
> >     at
> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
> >     at
> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
> >     at
> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
> >     at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
> >     at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> >     ... 3 more
> > Caused by: javax.persistence.PersistenceException: Unable to build
> > entity manager factory
> >     at
> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
> >     at
> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
> >     at
> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
> >     at
> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
> >     at
> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
> >     at
> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
> >     at
> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
> >     at
> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
> >     at
> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
> >     at
> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
> >     at
> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
> >     at
> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
> >     at
> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
> >     at
> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
> >     at
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
> >     at
> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
> >     at
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > Method) [rt.jar:1.7.0_45]
> >     at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> > [rt.jar:1.7.0_45]
> >     at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> > [rt.jar:1.7.0_45]
> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> > [rt.jar:1.7.0_45]
> >     at
> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
> >     ... 15 more
> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
> > JNDI name [java:jboss/datasources/UnifiedPushDS]
> >     at
> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
> >     at
> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
> >     at
> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
> >     at
> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
> >     at
> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
> >     at
> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
> >     at
> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
> >     at
> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
> >     at
> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> >     at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
> >     at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
> >     at
> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
> >     at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
> >     at
> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
> >     ... 36 more
> > Caused by: javax.naming.NameNotFoundException:
> > datasources/UnifiedPushDS -- service
> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
> >     at
> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
> >     at
> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
> > [rt.jar:1.7.0_45]
> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
> > [rt.jar:1.7.0_45]
> >     at
> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
> >     ... 52 more
> >
> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
> > failed - address: ([("deployment" => "auth-server.war")]) - failure
> > description: {"JBAS014671: Failed services" =>
> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
> > "org.jboss.msc.service.StartException in service
> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
> > start service
> >     Caused by: java.lang.RuntimeException: Failed to construct public
> >
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
> >     Caused by: javax.persistence.PersistenceException: Unable to build
> > entity manager factory
> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
> >     Caused by: javax.naming.NameNotFoundException:
> > datasources/UnifiedPushDS -- service
> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
> > with the following failure message:
> > {"JBAS014671: Failed services" =>
> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
> > "org.jboss.msc.service.StartException in service
> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
> > start service
> >     Caused by: java.lang.RuntimeException: Failed to construct public
> >
> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
> >     Caused by: javax.persistence.PersistenceException: Unable to build
> > entity manager factory
> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
> >     Caused by: javax.naming.NameNotFoundException:
> > datasources/UnifiedPushDS -- service
> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
> >
> > Using java version ?1.8.0_25?
> > ------------------------------
> > JBoss AS 7.1
> >
> > I can not start JBoss AS 7.1 using Java 8
> >
> > [passos]: ~
> > ? ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
> > -b 0.0.0.0
> > =========================================================================
> >
> >   JBoss Bootstrap Environment
> >
> >   JBOSS_HOME:
> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
> >
> >   JAVA: java
> >
> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
> > -Dorg.jboss.resolver.warning=true
> > -Dsun.rmi.dgc.client.gcInterval=3600000
> > -Dsun.rmi.dgc.server.gcInterval=3600000
> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> > -Djboss.server.default.config=standalone.xml
> >
> > =========================================================================
> >
> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> > MaxPermSize=256m; support was removed in 8.0
> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
> > "Brontes" starting
> >
> > Wildfly 8.1.0 Deploy
> >
> > [passos]:
> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
> > [git:pr/408]
> > ? mvn wildfly:deploy -Pwildfly
> >
> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
> > deploy against EAP, but I'm not sure that matters given the error
> > looks to be JDK/path/version-based.
> > [ERROR] Failed to execute goal
> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
> > one of its dependencies could not be resolved: Could not find artifact
> > sun.jdk:jconsole:jar:jdk at specified path
> >
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
> > -> [Help 1]
> >
> > I found the same problem in SwitchYard quickstart
> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
> >
> > ? Passos
> > ?
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/3e20947c/attachment-0001.html 

From daniel at passos.me  Tue Oct 21 07:20:35 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 21 Oct 2014 09:20:35 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
Message-ID: <CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>

On Tue, Oct 21, 2014 at 6:12 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello passos,
>
> regarding JBoss AS7.1 it's not really supported, especially after we added
> a scheduler to 1.0.0.Final:
> https://issues.jboss.org/browse/AS7-4694
>

So, we need update our READMEs/Docs ASAP

Please use EAP 6.3.GA instead.
>
> Also, I think they (EAP) do not support JDK8.
>
> But yeah, on Wildfly Java8 is first-class citizens ;-)
>
> greetings from Slovenia
>
> On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> Good morning Passos, would you mind to try the following steps?
>>
>> - WildFly 8.1.0
>>
>> 1. remove any previous installation of WildFly to make sure that we're
>> dealing with a fresh environment
>> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
>> 3. Start WildFly
>> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
>> 5. cp servers/auth-server/target/auth-server.war
>> $JBOSS_HOME/standalone/deployments
>> 6. cp servers/ups-wildfly/target/ag-push.war
>> $JBOSS_HOME/standalone/deployments
>>
>>
>> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
>> fresh setup.
>>
>> I know manual deploy is not awesome, but help us to debug what's goign
>> on.
>>
>> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
>> this, thanks for testing.
>>
>>
>>
>> On 2014-10-20, Daniel Passos wrote:
>> > Hey Guys,
>> >
>> > Today I?ve spend a lot of time (without success), trying test #408
>> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
>> using a
>> > new JBoss AS 7.1/Wildfly 8.1.0 installations
>> > Using Java version ?1.7.0_45?
>> > ------------------------------
>> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>> >
>> > [passos]:
>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>> > [git:pr/408]
>> > ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
>> > --file=../databases/h2-database-config.cli
>> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
>> > --jndi-name=java:jboss/datasources/UnifiedPushDS
>> >
>> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
>> > --user-name=sa --password=sa --use-ccm=true
>> > #2 data-source enable --name=UnifiedPushDS
>> > The batch executed successfully.
>> >
>> > Deployment
>> >
>> > [passos]:
>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>> > [git:pr/408]
>> > ? mvn jboss-as:deploy -Pas7
>> >
>> > Server Log
>> >
>> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
>> > 1-8) MSC00001: Failed to start service
>> > jboss.deployment.unit."ag-push.war".WeldService:
>> > org.jboss.msc.service.StartException in service
>> > jboss.deployment.unit."ag-push.war".WeldService:
>> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
>> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
>> > at injection point [[parameter 1] of [constructor] @Inject public
>> >
>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>> >     at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> > [rt.jar:1.7.0_45]
>> >     at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> > [rt.jar:1.7.0_45]
>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
>> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
>> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
>> > public
>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>> >     at
>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>> >     at
>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>> >     at
>> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>> >     at
>> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>> >     at
>> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>> >     at
>> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>> >     at
>> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>> >     ... 5 more
>> >
>> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>> >
>> > [passos]:
>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>> > [git:pr/408]
>> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
>> > --file=../databases/h2-database-config.cli
>> > The batch failed with the following error (you are remaining in the
>> > batch editing mode to have a chance to correct the error):
>> > {"JBAS014653: Composite operation failed and was rolled back. Steps
>> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
>> > failed: Service jboss.data-source-config.UnifiedPushDS is already
>> > registered"}}
>> >
>> > Server Log
>> >
>> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
>> > (MSC service thread 1-2) JBAS010400: Bound data source
>> > [java:jboss/datasources/UnifiedPushDS]
>> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
>> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
>> > address: ([
>> >     ("subsystem" => "datasources"),
>> >     ("data-source" => "UnifiedPushDS")
>> > ]): org.jboss.msc.service.DuplicateServiceException: Service
>> > jboss.data-source-config.UnifiedPushDS is already registered
>> >     at
>> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>> >     at
>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>> >     at
>> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at java.security.AccessController.doPrivileged(Native Method)
>> > [rt.jar:1.7.0_45]
>> >     at javax.security.auth.Subject.doAs(Subject.java:415)
>> [rt.jar:1.7.0_45]
>> >     at
>> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>> >     at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> > [rt.jar:1.7.0_45]
>> >     at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> > [rt.jar:1.7.0_45]
>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>> >
>> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
>> > (MSC service thread 1-7) JBAS010409: Unbound data source
>> > [java:jboss/datasources/UnifiedPushDS]
>> >
>> > Deployment
>> >
>> > [passos]:
>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>> > [git:pr/408]
>> > ? mvn wildfly:deploy -Pwildfly
>> > .
>> > .
>> > .
>> > [INFO]
>> ------------------------------------------------------------------------
>> > [INFO] Reactor Summary:
>> > [INFO]
>> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
>> [10.217s]
>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
>> [4.306s]
>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
>> > [INFO]
>> ------------------------------------------------------------------------
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> ------------------------------------------------------------------------
>> > [INFO] Total time: 15.561s
>> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
>> > [INFO] Final Memory: 35M/367M
>> > [INFO]
>> ------------------------------------------------------------------------
>> >
>> > Server Log
>> >
>> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
>> > 1-4) MSC000001: Failed to start service
>> > jboss.undertow.deployment.default-server.default-host./auth:
>> > org.jboss.msc.service.StartException in service
>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>> > start service
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> > [rt.jar:1.7.0_45]
>> >     at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> > [rt.jar:1.7.0_45]
>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>> > Caused by: java.lang.RuntimeException: Failed to construct public
>> >
>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>> >     at
>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>> >     at
>> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>> >     at
>> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>> >     at
>> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>> >     at
>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>> >     at
>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>> >     at
>> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>> >     at
>> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>> >     at
>> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>> >     at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>> >     at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>> >     ... 3 more
>> > Caused by: javax.persistence.PersistenceException: Unable to build
>> > entity manager factory
>> >     at
>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>> >     at
>> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>> >     at
>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>> >     at
>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>> >     at
>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>> >     at
>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>> >     at
>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>> >     at
>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>> >     at
>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>> >     at
>> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>> >     at
>> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>> >     at
>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>> >     at
>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>> >     at
>> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>> >     at
>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>> >     at
>> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>> >     at
>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> > Method) [rt.jar:1.7.0_45]
>> >     at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> > [rt.jar:1.7.0_45]
>> >     at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> > [rt.jar:1.7.0_45]
>> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>> > [rt.jar:1.7.0_45]
>> >     at
>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>> >     ... 15 more
>> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
>> > JNDI name [java:jboss/datasources/UnifiedPushDS]
>> >     at
>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>> >     at
>> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>> >     at
>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>> >     at
>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>> >     at
>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>> >     at
>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>> >     at
>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>> >     at
>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>> >     at
>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>> >     at
>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>> >     at
>> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>> >     at
>> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>> >     at
>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>> >     at
>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>> >     at
>> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>> >     at
>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>> >     at
>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>> >     ... 36 more
>> > Caused by: javax.naming.NameNotFoundException:
>> > datasources/UnifiedPushDS -- service
>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>> >     at
>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>> >     at
>> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>> > [rt.jar:1.7.0_45]
>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>> > [rt.jar:1.7.0_45]
>> >     at
>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>> >     ... 52 more
>> >
>> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
>> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
>> > failed - address: ([("deployment" => "auth-server.war")]) - failure
>> > description: {"JBAS014671: Failed services" =>
>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>> > "org.jboss.msc.service.StartException in service
>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>> > start service
>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>> >
>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>> > entity manager factory
>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>> >     Caused by: javax.naming.NameNotFoundException:
>> > datasources/UnifiedPushDS -- service
>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
>> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
>> > with the following failure message:
>> > {"JBAS014671: Failed services" =>
>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>> > "org.jboss.msc.service.StartException in service
>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>> > start service
>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>> >
>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>> > entity manager factory
>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>> >     Caused by: javax.naming.NameNotFoundException:
>> > datasources/UnifiedPushDS -- service
>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>> >
>> > Using java version ?1.8.0_25?
>> > ------------------------------
>> > JBoss AS 7.1
>> >
>> > I can not start JBoss AS 7.1 using Java 8
>> >
>> > [passos]: ~
>> > ? ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
>> > -b 0.0.0.0
>> >
>> =========================================================================
>> >
>> >   JBoss Bootstrap Environment
>> >
>> >   JBOSS_HOME:
>> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>> >
>> >   JAVA: java
>> >
>> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
>> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
>> > -Dorg.jboss.resolver.warning=true
>> > -Dsun.rmi.dgc.client.gcInterval=3600000
>> > -Dsun.rmi.dgc.server.gcInterval=3600000
>> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>> > -Djboss.server.default.config=standalone.xml
>> >
>> >
>> =========================================================================
>> >
>> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>> > MaxPermSize=256m; support was removed in 8.0
>> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
>> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
>> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
>> > "Brontes" starting
>> >
>> > Wildfly 8.1.0 Deploy
>> >
>> > [passos]:
>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>> > [git:pr/408]
>> > ? mvn wildfly:deploy -Pwildfly
>> >
>> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
>> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
>> > deploy against EAP, but I'm not sure that matters given the error
>> > looks to be JDK/path/version-based.
>> > [ERROR] Failed to execute goal
>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
>> > one of its dependencies could not be resolved: Could not find artifact
>> > sun.jdk:jconsole:jar:jdk at specified path
>> >
>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
>> > -> [Help 1]
>> >
>> > I found the same problem in SwitchYard quickstart
>> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
>> >
>> > ? Passos
>> > ?
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/f1cdd23f/attachment-0001.html 

From matzew at apache.org  Tue Oct 21 07:45:25 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 13:45:25 +0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
Message-ID: <CAAg5f2S8BrEGoaZXs5qHDEEXg4J2Qy3aq2K9KzXKhSphqbAR6Q@mail.gmail.com>

On Tuesday, October 21, 2014, Daniel Passos <daniel at passos.me> wrote:

> On Tue, Oct 21, 2014 at 6:12 AM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>> Hello passos,
>>
>> regarding JBoss AS7.1 it's not really supported, especially after we
>> added a scheduler to 1.0.0.Final:
>> https://issues.jboss.org/browse/AS7-4694
>>
>
> So, we need update our READMEs/Docs ASAP
>

ok, I will remove the AS7 parts tomorrow morning, or later at the airport;

How about only mentioning/promoting WildFly8.x on the README?

On our docs, I would like to "replace" JBossAS7 with EAP instructions, ok?


>
> Please use EAP 6.3.GA instead.
>>
>> Also, I think they (EAP) do not support JDK8.
>>
>> But yeah, on Wildfly Java8 is first-class citizens ;-)
>>
>> greetings from Slovenia
>>
>> On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org
>> <javascript:_e(%7B%7D,'cvml','bruno at abstractj.org');>> wrote:
>>
>>> Good morning Passos, would you mind to try the following steps?
>>>
>>> - WildFly 8.1.0
>>>
>>> 1. remove any previous installation of WildFly to make sure that we're
>>> dealing with a fresh environment
>>> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
>>> 3. Start WildFly
>>> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
>>> 5. cp servers/auth-server/target/auth-server.war
>>> $JBOSS_HOME/standalone/deployments
>>> 6. cp servers/ups-wildfly/target/ag-push.war
>>> $JBOSS_HOME/standalone/deployments
>>>
>>>
>>> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
>>> fresh setup.
>>>
>>> I know manual deploy is not awesome, but help us to debug what's goign
>>> on.
>>>
>>> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
>>> this, thanks for testing.
>>>
>>>
>>>
>>> On 2014-10-20, Daniel Passos wrote:
>>> > Hey Guys,
>>> >
>>> > Today I?ve spend a lot of time (without success), trying test #408
>>> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
>>> using a
>>> > new JBoss AS 7.1/Wildfly 8.1.0 installations
>>> > Using Java version ?1.7.0_45?
>>> > ------------------------------
>>> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
>>> > --file=../databases/h2-database-config.cli
>>> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
>>> > --jndi-name=java:jboss/datasources/UnifiedPushDS
>>> >
>>> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
>>> > --user-name=sa --password=sa --use-ccm=true
>>> > #2 data-source enable --name=UnifiedPushDS
>>> > The batch executed successfully.
>>> >
>>> > Deployment
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? mvn jboss-as:deploy -Pas7
>>> >
>>> > Server Log
>>> >
>>> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>> > 1-8) MSC00001: Failed to start service
>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>> > org.jboss.msc.service.StartException in service
>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
>>> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
>>> > at injection point [[parameter 1] of [constructor] @Inject public
>>> >
>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>> >     at
>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
>>> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
>>> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
>>> > public
>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>>> >     at
>>> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>>> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>>> >     at
>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>> >     ... 5 more
>>> >
>>> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
>>> > --file=../databases/h2-database-config.cli
>>> > The batch failed with the following error (you are remaining in the
>>> > batch editing mode to have a chance to correct the error):
>>> > {"JBAS014653: Composite operation failed and was rolled back. Steps
>>> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
>>> > failed: Service jboss.data-source-config.UnifiedPushDS is already
>>> > registered"}}
>>> >
>>> > Server Log
>>> >
>>> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
>>> > (MSC service thread 1-2) JBAS010400: Bound data source
>>> > [java:jboss/datasources/UnifiedPushDS]
>>> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
>>> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
>>> > address: ([
>>> >     ("subsystem" => "datasources"),
>>> >     ("data-source" => "UnifiedPushDS")
>>> > ]): org.jboss.msc.service.DuplicateServiceException: Service
>>> > jboss.data-source-config.UnifiedPushDS is already registered
>>> >     at
>>> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>>> >     at
>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at java.security.AccessController.doPrivileged(Native Method)
>>> > [rt.jar:1.7.0_45]
>>> >     at javax.security.auth.Subject.doAs(Subject.java:415)
>>> [rt.jar:1.7.0_45]
>>> >     at
>>> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>>> >
>>> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
>>> > (MSC service thread 1-7) JBAS010409: Unbound data source
>>> > [java:jboss/datasources/UnifiedPushDS]
>>> >
>>> > Deployment
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? mvn wildfly:deploy -Pwildfly
>>> > .
>>> > .
>>> > .
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> > [INFO] Reactor Summary:
>>> > [INFO]
>>> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
>>> [10.217s]
>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
>>> [4.306s]
>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> > [INFO] BUILD FAILURE
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> > [INFO] Total time: 15.561s
>>> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
>>> > [INFO] Final Memory: 35M/367M
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> >
>>> > Server Log
>>> >
>>> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>> > 1-4) MSC000001: Failed to start service
>>> > jboss.undertow.deployment.default-server.default-host./auth:
>>> > org.jboss.msc.service.StartException in service
>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>> > start service
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>> > Caused by: java.lang.RuntimeException: Failed to construct public
>>> >
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>> >     at
>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>>> >     at
>>> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>>> >     at
>>> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>>> >     at
>>> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>>> >     at
>>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>>> >     at
>>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>>> >     at
>>> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>>> >     at
>>> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>>> >     at
>>> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>>> >     at
>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>>> >     at
>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     ... 3 more
>>> > Caused by: javax.persistence.PersistenceException: Unable to build
>>> > entity manager factory
>>> >     at
>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>>> >     at
>>> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>>> >     at
>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>>> >     at
>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>>> >     at
>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>>> >     at
>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>> >     at
>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>>> >     at
>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>>> >     at
>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>> >     at
>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>>> >     at
>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>>> >     at
>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>>> >     at
>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>>> >     at
>>> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>>> >     at
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>>> >     at
>>> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>>> >     at
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>> > Method) [rt.jar:1.7.0_45]
>>> >     at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>>> >     ... 15 more
>>> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
>>> > JNDI name [java:jboss/datasources/UnifiedPushDS]
>>> >     at
>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>>> >     at
>>> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>>> >     at
>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>> >     at
>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>>> >     at
>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>>> >     at
>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>> >     at
>>> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>>> >     at
>>> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>>> >     at
>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>>> >     at
>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>>> >     at
>>> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>>> >     at
>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>>> >     at
>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>>> >     ... 36 more
>>> > Caused by: javax.naming.NameNotFoundException:
>>> > datasources/UnifiedPushDS -- service
>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>>> >     at
>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>> >     at
>>> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>> > [rt.jar:1.7.0_45]
>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>>> >     ... 52 more
>>> >
>>> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
>>> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
>>> > failed - address: ([("deployment" => "auth-server.war")]) - failure
>>> > description: {"JBAS014671: Failed services" =>
>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>> > "org.jboss.msc.service.StartException in service
>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>> > start service
>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>> >
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>> > entity manager factory
>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>> >     Caused by: javax.naming.NameNotFoundException:
>>> > datasources/UnifiedPushDS -- service
>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
>>> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
>>> > with the following failure message:
>>> > {"JBAS014671: Failed services" =>
>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>> > "org.jboss.msc.service.StartException in service
>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>> > start service
>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>> >
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>> > entity manager factory
>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>> >     Caused by: javax.naming.NameNotFoundException:
>>> > datasources/UnifiedPushDS -- service
>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>> >
>>> > Using java version ?1.8.0_25?
>>> > ------------------------------
>>> > JBoss AS 7.1
>>> >
>>> > I can not start JBoss AS 7.1 using Java 8
>>> >
>>> > [passos]: ~
>>> > ?
>>> ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
>>> > -b 0.0.0.0
>>> >
>>> =========================================================================
>>> >
>>> >   JBoss Bootstrap Environment
>>> >
>>> >   JBOSS_HOME:
>>> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>>> >
>>> >   JAVA: java
>>> >
>>> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
>>> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
>>> > -Dorg.jboss.resolver.warning=true
>>> > -Dsun.rmi.dgc.client.gcInterval=3600000
>>> > -Dsun.rmi.dgc.server.gcInterval=3600000
>>> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>>> > -Djboss.server.default.config=standalone.xml
>>> >
>>> >
>>> =========================================================================
>>> >
>>> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>> > MaxPermSize=256m; support was removed in 8.0
>>> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
>>> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
>>> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
>>> > "Brontes" starting
>>> >
>>> > Wildfly 8.1.0 Deploy
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? mvn wildfly:deploy -Pwildfly
>>> >
>>> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
>>> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
>>> > deploy against EAP, but I'm not sure that matters given the error
>>> > looks to be JDK/path/version-based.
>>> > [ERROR] Failed to execute goal
>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
>>> > one of its dependencies could not be resolved: Could not find artifact
>>> > sun.jdk:jconsole:jar:jdk at specified path
>>> >
>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
>>> > -> [Help 1]
>>> >
>>> > I found the same problem in SwitchYard quickstart
>>> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
>>> >
>>> > ? Passos
>>> > ?
>>>
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> --
>>>
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://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:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/a2a227a2/attachment-0001.html 

From daniel at passos.me  Tue Oct 21 07:46:53 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 21 Oct 2014 09:46:53 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
Message-ID: <CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>

As Matthias suggested, here is my test using a clean instance of JBoss EAP
6.2GA

I?ve got the same problem using Java ?1.7.0_45? and ?1.8.0_25?
Generate the UnifiedPush Database and Datasource

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? ~/Development/Java/Server/JBoss/jboss-eap-6.3/bin/jboss-cli.sh
--file=../databases/h2-database-config.cli
The batch executed successfully

Deploy

[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
? mvn jboss-as:deploy -Pas7
.
.
.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] UnifiedPush Auth Server ........................... SUCCESS [12.755s]
[INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE [4.050s]
[INFO] UnifiedPush Servers Parent ........................ SKIPPED
[INFO] ------------------------------------------------------------------------

Server Log

09:29:09,889 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-6) MSC000001: Failed to start service
jboss.deployment.unit."ag-push.war".WeldStartService:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."ag-push.war".WeldStartService: Failed to start
service
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936)
[jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
[@Default] at injection point [[parameter 1] of [constructor] @Inject
public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:315)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:147)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:386)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
    at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
[jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
[jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    ... 3 more

09:29:09,900 ERROR [org.jboss.as.server] (management-handler-thread -
1) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with
the following failure message:
{"JBAS014671: Failed services" =>
{"jboss.deployment.unit.\"ag-push.war\".WeldStartService" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"ag-push.war\".WeldStartService: Failed to
start service
    Caused by: org.jboss.weld.exceptions.DeploymentException:
WELD-001408 Unsatisfied dependencies for type [HttpServletRequest]
with qualifiers [@Default] at injection point [[parameter 1] of
[constructor] @Inject public
org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]"}}

?

On Tue, Oct 21, 2014 at 9:20 AM, Daniel Passos <daniel at passos.me> wrote:

> On Tue, Oct 21, 2014 at 6:12 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hello passos,
>>
>> regarding JBoss AS7.1 it's not really supported, especially after we
>> added a scheduler to 1.0.0.Final:
>> https://issues.jboss.org/browse/AS7-4694
>>
>
> So, we need update our READMEs/Docs ASAP
>
> Please use EAP 6.3.GA instead.
>>
>> Also, I think they (EAP) do not support JDK8.
>>
>> But yeah, on Wildfly Java8 is first-class citizens ;-)
>>
>> greetings from Slovenia
>>
>> On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org>
>> wrote:
>>
>>> Good morning Passos, would you mind to try the following steps?
>>>
>>> - WildFly 8.1.0
>>>
>>> 1. remove any previous installation of WildFly to make sure that we're
>>> dealing with a fresh environment
>>> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
>>> 3. Start WildFly
>>> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
>>> 5. cp servers/auth-server/target/auth-server.war
>>> $JBOSS_HOME/standalone/deployments
>>> 6. cp servers/ups-wildfly/target/ag-push.war
>>> $JBOSS_HOME/standalone/deployments
>>>
>>>
>>> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
>>> fresh setup.
>>>
>>> I know manual deploy is not awesome, but help us to debug what's goign
>>> on.
>>>
>>> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
>>> this, thanks for testing.
>>>
>>>
>>>
>>> On 2014-10-20, Daniel Passos wrote:
>>> > Hey Guys,
>>> >
>>> > Today I?ve spend a lot of time (without success), trying test #408
>>> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
>>> using a
>>> > new JBoss AS 7.1/Wildfly 8.1.0 installations
>>> > Using Java version ?1.7.0_45?
>>> > ------------------------------
>>> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
>>> > --file=../databases/h2-database-config.cli
>>> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
>>> > --jndi-name=java:jboss/datasources/UnifiedPushDS
>>> >
>>> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
>>> > --user-name=sa --password=sa --use-ccm=true
>>> > #2 data-source enable --name=UnifiedPushDS
>>> > The batch executed successfully.
>>> >
>>> > Deployment
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? mvn jboss-as:deploy -Pas7
>>> >
>>> > Server Log
>>> >
>>> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>> > 1-8) MSC00001: Failed to start service
>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>> > org.jboss.msc.service.StartException in service
>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
>>> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
>>> > at injection point [[parameter 1] of [constructor] @Inject public
>>> >
>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>> >     at
>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
>>> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
>>> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
>>> > public
>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>>> >     at
>>> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>>> >     at
>>> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>>> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>>> >     at
>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>> >     ... 5 more
>>> >
>>> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
>>> > --file=../databases/h2-database-config.cli
>>> > The batch failed with the following error (you are remaining in the
>>> > batch editing mode to have a chance to correct the error):
>>> > {"JBAS014653: Composite operation failed and was rolled back. Steps
>>> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
>>> > failed: Service jboss.data-source-config.UnifiedPushDS is already
>>> > registered"}}
>>> >
>>> > Server Log
>>> >
>>> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
>>> > (MSC service thread 1-2) JBAS010400: Bound data source
>>> > [java:jboss/datasources/UnifiedPushDS]
>>> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
>>> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
>>> > address: ([
>>> >     ("subsystem" => "datasources"),
>>> >     ("data-source" => "UnifiedPushDS")
>>> > ]): org.jboss.msc.service.DuplicateServiceException: Service
>>> > jboss.data-source-config.UnifiedPushDS is already registered
>>> >     at
>>> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>>> >     at
>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at java.security.AccessController.doPrivileged(Native Method)
>>> > [rt.jar:1.7.0_45]
>>> >     at javax.security.auth.Subject.doAs(Subject.java:415)
>>> [rt.jar:1.7.0_45]
>>> >     at
>>> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>>> >
>>> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
>>> > (MSC service thread 1-7) JBAS010409: Unbound data source
>>> > [java:jboss/datasources/UnifiedPushDS]
>>> >
>>> > Deployment
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? mvn wildfly:deploy -Pwildfly
>>> > .
>>> > .
>>> > .
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> > [INFO] Reactor Summary:
>>> > [INFO]
>>> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
>>> [10.217s]
>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
>>> [4.306s]
>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> > [INFO] BUILD FAILURE
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> > [INFO] Total time: 15.561s
>>> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
>>> > [INFO] Final Memory: 35M/367M
>>> > [INFO]
>>> ------------------------------------------------------------------------
>>> >
>>> > Server Log
>>> >
>>> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>> > 1-4) MSC000001: Failed to start service
>>> > jboss.undertow.deployment.default-server.default-host./auth:
>>> > org.jboss.msc.service.StartException in service
>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>> > start service
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>> > Caused by: java.lang.RuntimeException: Failed to construct public
>>> >
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>> >     at
>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>>> >     at
>>> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>>> >     at
>>> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>>> >     at
>>> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>>> >     at
>>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>>> >     at
>>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>>> >     at
>>> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>>> >     at
>>> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>>> >     at
>>> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>>> >     at
>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>>> >     at
>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     at
>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>> >     ... 3 more
>>> > Caused by: javax.persistence.PersistenceException: Unable to build
>>> > entity manager factory
>>> >     at
>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>>> >     at
>>> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>>> >     at
>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>>> >     at
>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>>> >     at
>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>>> >     at
>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>> >     at
>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>>> >     at
>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>>> >     at
>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>> >     at
>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>>> >     at
>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>>> >     at
>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>>> >     at
>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>>> >     at
>>> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>>> >     at
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>>> >     at
>>> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>>> >     at
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>> > Method) [rt.jar:1.7.0_45]
>>> >     at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> > [rt.jar:1.7.0_45]
>>> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>>> >     ... 15 more
>>> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
>>> > JNDI name [java:jboss/datasources/UnifiedPushDS]
>>> >     at
>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>>> >     at
>>> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>>> >     at
>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>> >     at
>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>>> >     at
>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>>> >     at
>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>> >     at
>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>> >     at
>>> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>>> >     at
>>> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>>> >     at
>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>>> >     at
>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>>> >     at
>>> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>>> >     at
>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>>> >     at
>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>>> >     ... 36 more
>>> > Caused by: javax.naming.NameNotFoundException:
>>> > datasources/UnifiedPushDS -- service
>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>>> >     at
>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>> >     at
>>> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>> > [rt.jar:1.7.0_45]
>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>> > [rt.jar:1.7.0_45]
>>> >     at
>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>>> >     ... 52 more
>>> >
>>> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
>>> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
>>> > failed - address: ([("deployment" => "auth-server.war")]) - failure
>>> > description: {"JBAS014671: Failed services" =>
>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>> > "org.jboss.msc.service.StartException in service
>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>> > start service
>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>> >
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>> > entity manager factory
>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>> >     Caused by: javax.naming.NameNotFoundException:
>>> > datasources/UnifiedPushDS -- service
>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
>>> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
>>> > with the following failure message:
>>> > {"JBAS014671: Failed services" =>
>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>> > "org.jboss.msc.service.StartException in service
>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>> > start service
>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>> >
>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>> > entity manager factory
>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>> >     Caused by: javax.naming.NameNotFoundException:
>>> > datasources/UnifiedPushDS -- service
>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>> >
>>> > Using java version ?1.8.0_25?
>>> > ------------------------------
>>> > JBoss AS 7.1
>>> >
>>> > I can not start JBoss AS 7.1 using Java 8
>>> >
>>> > [passos]: ~
>>> > ?
>>> ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
>>> > -b 0.0.0.0
>>> >
>>> =========================================================================
>>> >
>>> >   JBoss Bootstrap Environment
>>> >
>>> >   JBOSS_HOME:
>>> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>>> >
>>> >   JAVA: java
>>> >
>>> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
>>> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
>>> > -Dorg.jboss.resolver.warning=true
>>> > -Dsun.rmi.dgc.client.gcInterval=3600000
>>> > -Dsun.rmi.dgc.server.gcInterval=3600000
>>> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>>> > -Djboss.server.default.config=standalone.xml
>>> >
>>> >
>>> =========================================================================
>>> >
>>> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>> > MaxPermSize=256m; support was removed in 8.0
>>> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
>>> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
>>> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
>>> > "Brontes" starting
>>> >
>>> > Wildfly 8.1.0 Deploy
>>> >
>>> > [passos]:
>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>> > [git:pr/408]
>>> > ? mvn wildfly:deploy -Pwildfly
>>> >
>>> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
>>> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
>>> > deploy against EAP, but I'm not sure that matters given the error
>>> > looks to be JDK/path/version-based.
>>> > [ERROR] Failed to execute goal
>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
>>> > one of its dependencies could not be resolved: Could not find artifact
>>> > sun.jdk:jconsole:jar:jdk at specified path
>>> >
>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
>>> > -> [Help 1]
>>> >
>>> > I found the same problem in SwitchYard quickstart
>>> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
>>> >
>>> > ? Passos
>>> > ?
>>>
>>> > _______________________________________________
>>> > aerogear-dev mailing list
>>> > aerogear-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> --
>>>
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/77ad3661/attachment-0001.html 

From daniel at passos.me  Tue Oct 21 07:47:46 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 21 Oct 2014 09:47:46 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
Message-ID: <CAKjsGbvoYqXuQ0-7AZTBXTNQ5dDcaKbKAoTZ4577YgLGtkZkDw@mail.gmail.com>

Also I?m getting this when I try compile the project using Java 8. Maybe is
a good idea add Java 8 on travis build.

[ERROR] The given File link:
/Users/passos/Development/Projects/AeroGear/aerogear-unifiedpush-server/jaxrs/../target/site/apidocs
is not a dir.
[ERROR] Error fetching link:
/Users/passos/Development/Projects/AeroGear/aerogear-unifiedpush-server/jaxrs/../target/site/apidocs/package-list.
Ignored it.
[INFO]
Loading source files for package org.jboss.aerogear.unifiedpush.rest...
Loading source files for package
org.jboss.aerogear.unifiedpush.rest.annotations...
Loading source files for package
org.jboss.aerogear.unifiedpush.rest.registry.installations...
Loading source files for package org.jboss.aerogear.unifiedpush.rest.sender...
Constructing Javadoc information...
1 error
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] AeroGear UnifiedPush Server ....................... SUCCESS [1.981s]
[INFO] UnifiedPush Model Layer ........................... SUCCESS [0.052s]
[INFO] UnifiedPush Server Model API ...................... SUCCESS [3.359s]
[INFO] UnifiedPush Server Model JPA implementation ....... SUCCESS [16.161s]
[INFO] UnifiedPush Service Layer ......................... SUCCESS [21.848s]
[INFO] UnifiedPush Push Notification Networks ............ SUCCESS [3.745s]
[INFO] UnifiedPush RESTful Endpoint ...................... FAILURE [2.425s]
[INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED
[INFO] UnifiedPush Dependencies Parent ................... SKIPPED
[INFO] UnifiedPush Server Dependencies Server ............ SKIPPED
[INFO] UnifiedPush Auth Server ........................... SKIPPED
[INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED
[INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED
[INFO] UnifiedPush Servers Parent ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 50.770s
[INFO] Finished at: Tue Oct 21 09:35:48 BRST 2014
[INFO] Final Memory: 88M/716M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc
(jax-rs-docs) on project unifiedpush-jaxrs: An error has occurred in
JavaDocs report generation:
[ERROR] Exit code: 1 - javadoc: error - In doclet class
com.lunatech.doclets.jax.jaxrs.JAXRSDoclet,  method start has thrown
an exception java.lang.reflect.InvocationTargetException
[ERROR] java.lang.NullPointerException
[ERROR] at com.lunatech.doclets.jax.jaxrs.JAXRSDoclet.<init>(JAXRSDoclet.java:84)
[ERROR] at com.lunatech.doclets.jax.jaxrs.JAXRSDoclet.start(JAXRSDoclet.java:78)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:483)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:310)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:189)
[ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:366)
[ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:219)
[ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:205)
[ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:64)
[ERROR] at com.sun.tools.javadoc.Main.main(Main.java:54)
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/javadoc
@options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/passos/Development/Projects/AeroGear/aerogear-unifiedpush-server/jaxrs/target/site/apidocs'
dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :unifiedpush-jaxrs

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/1718528b/attachment.html 

From scm.blanc at gmail.com  Tue Oct 21 07:48:50 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Tue, 21 Oct 2014 13:48:50 +0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAAg5f2S8BrEGoaZXs5qHDEEXg4J2Qy3aq2K9KzXKhSphqbAR6Q@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAAg5f2S8BrEGoaZXs5qHDEEXg4J2Qy3aq2K9KzXKhSphqbAR6Q@mail.gmail.com>
Message-ID: <A46E0911-4CF5-4215-90F1-565CA25C4074@gmail.com>



Envoy? de mon iPhone

> Le 21 oct. 2014 ? 13:45, Matthias Wessendorf <matzew at apache.org> a ?crit :
> 
> 
> 
>> On Tuesday, October 21, 2014, Daniel Passos <daniel at passos.me> wrote:
>>> On Tue, Oct 21, 2014 at 6:12 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>>> Hello passos,
>>> 
>>> regarding JBoss AS7.1 it's not really supported, especially after we added a scheduler to 1.0.0.Final:
>>> https://issues.jboss.org/browse/AS7-4694
>>  
>> So, we need update our READMEs/Docs ASAP
> 
> ok, I will remove the AS7 parts tomorrow morning, or later at the airport;
> 
> How about only mentioning/promoting WildFly8.x on the README?
+1
> 
> On our docs, I would like to "replace" JBossAS7 with EAP instructions, ok?
Yes, make sense 
>  
>> 
>>> Please use EAP 6.3.GA instead.
>>> 
>>> Also, I think they (EAP) do not support JDK8.
>>> 
>>> But yeah, on Wildfly Java8 is first-class citizens ;-)
>>> 
>>> greetings from Slovenia 
>>> 
>>>> On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
>>>> Good morning Passos, would you mind to try the following steps?
>>>> 
>>>> - WildFly 8.1.0
>>>> 
>>>> 1. remove any previous installation of WildFly to make sure that we're
>>>> dealing with a fresh environment
>>>> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
>>>> 3. Start WildFly
>>>> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
>>>> 5. cp servers/auth-server/target/auth-server.war $JBOSS_HOME/standalone/deployments
>>>> 6. cp servers/ups-wildfly/target/ag-push.war $JBOSS_HOME/standalone/deployments
>>>> 
>>>> 
>>>> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
>>>> fresh setup.
>>>> 
>>>> I know manual deploy is not awesome, but help us to debug what's goign
>>>> on.
>>>> 
>>>> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
>>>> this, thanks for testing.
>>>> 
>>>> 
>>>> 
>>>> On 2014-10-20, Daniel Passos wrote:
>>>> > Hey Guys,
>>>> >
>>>> > Today I?ve spend a lot of time (without success), trying test #408
>>>> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408> using a
>>>> > new JBoss AS 7.1/Wildfly 8.1.0 installations
>>>> > Using Java version ?1.7.0_45?
>>>> > ------------------------------
>>>> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>>>> >
>>>> > [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
>>>> > --file=../databases/h2-database-config.cli
>>>> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
>>>> > --jndi-name=java:jboss/datasources/UnifiedPushDS
>>>> > --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
>>>> > --user-name=sa --password=sa --use-ccm=true
>>>> > #2 data-source enable --name=UnifiedPushDS
>>>> > The batch executed successfully.
>>>> >
>>>> > Deployment
>>>> >
>>>> > [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn jboss-as:deploy -Pas7
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>>> > 1-8) MSC00001: Failed to start service
>>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>>> > org.jboss.msc.service.StartException in service
>>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>>> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
>>>> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
>>>> > at injection point [[parameter 1] of [constructor] @Inject public
>>>> > org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>>> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>> >     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>> >     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
>>>> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
>>>> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
>>>> > public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>>> >     at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>>>> >     at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>>>> >     at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>>>> >     at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>>>> >     at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>>>> >     at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>>>> >     at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>>>> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>>>> >     at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>> >     ... 5 more
>>>> >
>>>> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>>>> >
>>>> > [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
>>>> > --file=../databases/h2-database-config.cli
>>>> > The batch failed with the following error (you are remaining in the
>>>> > batch editing mode to have a chance to correct the error):
>>>> > {"JBAS014653: Composite operation failed and was rolled back. Steps
>>>> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
>>>> > failed: Service jboss.data-source-config.UnifiedPushDS is already
>>>> > registered"}}
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
>>>> > (MSC service thread 1-2) JBAS010400: Bound data source
>>>> > [java:jboss/datasources/UnifiedPushDS]
>>>> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
>>>> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
>>>> > address: ([
>>>> >     ("subsystem" => "datasources"),
>>>> >     ("data-source" => "UnifiedPushDS")
>>>> > ]): org.jboss.msc.service.DuplicateServiceException: Service
>>>> > jboss.data-source-config.UnifiedPushDS is already registered
>>>> >     at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>>>> >     at org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>>>> >     at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at java.security.AccessController.doPrivileged(Native Method)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_45]
>>>> >     at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
>>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
>>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>>> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>>>> >
>>>> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
>>>> > (MSC service thread 1-7) JBAS010409: Unbound data source
>>>> > [java:jboss/datasources/UnifiedPushDS]
>>>> >
>>>> > Deployment
>>>> >
>>>> > [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn wildfly:deploy -Pwildfly
>>>> > .
>>>> > .
>>>> > .
>>>> > [INFO] ------------------------------------------------------------------------
>>>> > [INFO] Reactor Summary:
>>>> > [INFO]
>>>> > [INFO] UnifiedPush Auth Server ........................... SUCCESS [10.217s]
>>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE [4.306s]
>>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
>>>> > [INFO] ------------------------------------------------------------------------
>>>> > [INFO] BUILD FAILURE
>>>> > [INFO] ------------------------------------------------------------------------
>>>> > [INFO] Total time: 15.561s
>>>> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
>>>> > [INFO] Final Memory: 35M/367M
>>>> > [INFO] ------------------------------------------------------------------------
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>>> > 1-4) MSC000001: Failed to start service
>>>> > jboss.undertow.deployment.default-server.default-host./auth:
>>>> > org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> > Caused by: java.lang.RuntimeException: Failed to construct public
>>>> > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>>>> >     at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>>>> >     at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>>>> >     at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>>>> >     at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>>>> >     at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>>>> >     at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>>>> >     at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>>>> >     at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>>>> >     at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>>>> >     at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>>>> >     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     ... 3 more
>>>> > Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>>>> >     at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>>>> >     at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>>>> >     at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>>>> >     at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>>>> >     at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>>> >     at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>>>> >     at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>>>> >     at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>>> >     at org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>>>> >     at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>>>> >     at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>>>> >     at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>>>> >     at org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>>>> >     at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>>>> >     at org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>>>> >     at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>>>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>> > Method) [rt.jar:1.7.0_45]
>>>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>>>> >     ... 15 more
>>>> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
>>>> > JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>>>> >     at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>>>> >     at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>>> >     at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>>> >     at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>>> >     at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>>>> >     at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>>>> >     at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>>> >     at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>>> >     at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>>> >     at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>>>> >     at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>>>> >     at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>>>> >     at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>>>> >     at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>>>> >     at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>>>> >     at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>>>> >     ... 36 more
>>>> > Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>>>> >     at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>>> >     at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>>>> >     at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>>>> >     ... 52 more
>>>> >
>>>> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
>>>> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
>>>> > failed - address: ([("deployment" => "auth-server.war")]) - failure
>>>> > description: {"JBAS014671: Failed services" =>
>>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>>> > "org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>>> > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>>> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
>>>> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
>>>> > with the following failure message:
>>>> > {"JBAS014671: Failed services" =>
>>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>>> > "org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>>> > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>>> >
>>>> > Using java version ?1.8.0_25?
>>>> > ------------------------------
>>>> > JBoss AS 7.1
>>>> >
>>>> > I can not start JBoss AS 7.1 using Java 8
>>>> >
>>>> > [passos]: ~
>>>> > ? ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
>>>> > -b 0.0.0.0
>>>> > =========================================================================
>>>> >
>>>> >   JBoss Bootstrap Environment
>>>> >
>>>> >   JBOSS_HOME: /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>>>> >
>>>> >   JAVA: java
>>>> >
>>>> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
>>>> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
>>>> > -Dorg.jboss.resolver.warning=true
>>>> > -Dsun.rmi.dgc.client.gcInterval=3600000
>>>> > -Dsun.rmi.dgc.server.gcInterval=3600000
>>>> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>>>> > -Djboss.server.default.config=standalone.xml
>>>> >
>>>> > =========================================================================
>>>> >
>>>> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>>> > MaxPermSize=256m; support was removed in 8.0
>>>> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
>>>> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
>>>> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
>>>> > "Brontes" starting
>>>> >
>>>> > Wildfly 8.1.0 Deploy
>>>> >
>>>> > [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn wildfly:deploy -Pwildfly
>>>> >
>>>> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
>>>> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
>>>> > deploy against EAP, but I'm not sure that matters given the error
>>>> > looks to be JDK/path/version-based.
>>>> > [ERROR] Failed to execute goal
>>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>>> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
>>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>>> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
>>>> > one of its dependencies could not be resolved: Could not find artifact
>>>> > sun.jdk:jconsole:jar:jdk at specified path
>>>> > /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
>>>> > -> [Help 1]
>>>> >
>>>> > I found the same problem in SwitchYard quickstart
>>>> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
>>>> >
>>>> > ? Passos
>>>> > ?
>>>> 
>>>> > _______________________________________________
>>>> > aerogear-dev mailing list
>>>> > aerogear-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> --
>>>> 
>>>> abstractj
>>>> PGP: 0x84DC9914
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> -- 
> 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/20141021/2efd46b4/attachment-0001.html 

From daniel at passos.me  Tue Oct 21 07:48:43 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 21 Oct 2014 09:48:43 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAAg5f2S8BrEGoaZXs5qHDEEXg4J2Qy3aq2K9KzXKhSphqbAR6Q@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAAg5f2S8BrEGoaZXs5qHDEEXg4J2Qy3aq2K9KzXKhSphqbAR6Q@mail.gmail.com>
Message-ID: <CAKjsGbuXyKzEWX-eqgCZBGF0AHMnMji9_+KUWvsWgknqjZv2Zw@mail.gmail.com>

On Tue, Oct 21, 2014 at 9:45 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Tuesday, October 21, 2014, Daniel Passos <daniel at passos.me> wrote:
>
>> On Tue, Oct 21, 2014 at 6:12 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hello passos,
>>>
>>> regarding JBoss AS7.1 it's not really supported, especially after we
>>> added a scheduler to 1.0.0.Final:
>>> https://issues.jboss.org/browse/AS7-4694
>>>
>>
>> So, we need update our READMEs/Docs ASAP
>>
>
> ok, I will remove the AS7 parts tomorrow morning, or later at the airport;
>
> How about only mentioning/promoting WildFly8.x on the README?
>

Sounds good to me


> On our docs, I would like to "replace" JBossAS7 with EAP instructions, ok?
>

#agreed


> Please use EAP 6.3.GA instead.
>>>
>>> Also, I think they (EAP) do not support JDK8.
>>>
>>> But yeah, on Wildfly Java8 is first-class citizens ;-)
>>>
>>> greetings from Slovenia
>>>
>>> On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org>
>>> wrote:
>>>
>>>> Good morning Passos, would you mind to try the following steps?
>>>>
>>>> - WildFly 8.1.0
>>>>
>>>> 1. remove any previous installation of WildFly to make sure that we're
>>>> dealing with a fresh environment
>>>> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
>>>> 3. Start WildFly
>>>> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
>>>> 5. cp servers/auth-server/target/auth-server.war
>>>> $JBOSS_HOME/standalone/deployments
>>>> 6. cp servers/ups-wildfly/target/ag-push.war
>>>> $JBOSS_HOME/standalone/deployments
>>>>
>>>>
>>>> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
>>>> fresh setup.
>>>>
>>>> I know manual deploy is not awesome, but help us to debug what's goign
>>>> on.
>>>>
>>>> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
>>>> this, thanks for testing.
>>>>
>>>>
>>>>
>>>> On 2014-10-20, Daniel Passos wrote:
>>>> > Hey Guys,
>>>> >
>>>> > Today I?ve spend a lot of time (without success), trying test #408
>>>> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
>>>> using a
>>>> > new JBoss AS 7.1/Wildfly 8.1.0 installations
>>>> > Using Java version ?1.7.0_45?
>>>> > ------------------------------
>>>> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ?
>>>> ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
>>>> > --file=../databases/h2-database-config.cli
>>>> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
>>>> > --jndi-name=java:jboss/datasources/UnifiedPushDS
>>>> >
>>>> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
>>>> > --user-name=sa --password=sa --use-ccm=true
>>>> > #2 data-source enable --name=UnifiedPushDS
>>>> > The batch executed successfully.
>>>> >
>>>> > Deployment
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn jboss-as:deploy -Pas7
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>>> > 1-8) MSC00001: Failed to start service
>>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>>> > org.jboss.msc.service.StartException in service
>>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>>> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
>>>> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
>>>> > at injection point [[parameter 1] of [constructor] @Inject public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>>> >     at
>>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
>>>> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
>>>> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
>>>> > public
>>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>>>> >     at
>>>> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>>>> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>>>> >     at
>>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>> >     ... 5 more
>>>> >
>>>> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
>>>> > --file=../databases/h2-database-config.cli
>>>> > The batch failed with the following error (you are remaining in the
>>>> > batch editing mode to have a chance to correct the error):
>>>> > {"JBAS014653: Composite operation failed and was rolled back. Steps
>>>> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
>>>> > failed: Service jboss.data-source-config.UnifiedPushDS is already
>>>> > registered"}}
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
>>>> > (MSC service thread 1-2) JBAS010400: Bound data source
>>>> > [java:jboss/datasources/UnifiedPushDS]
>>>> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
>>>> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
>>>> > address: ([
>>>> >     ("subsystem" => "datasources"),
>>>> >     ("data-source" => "UnifiedPushDS")
>>>> > ]): org.jboss.msc.service.DuplicateServiceException: Service
>>>> > jboss.data-source-config.UnifiedPushDS is already registered
>>>> >     at
>>>> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>>>> >     at
>>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at java.security.AccessController.doPrivileged(Native Method)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at javax.security.auth.Subject.doAs(Subject.java:415)
>>>> [rt.jar:1.7.0_45]
>>>> >     at
>>>> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
>>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
>>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>>> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>>>> >
>>>> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
>>>> > (MSC service thread 1-7) JBAS010409: Unbound data source
>>>> > [java:jboss/datasources/UnifiedPushDS]
>>>> >
>>>> > Deployment
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn wildfly:deploy -Pwildfly
>>>> > .
>>>> > .
>>>> > .
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> > [INFO] Reactor Summary:
>>>> > [INFO]
>>>> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
>>>> [10.217s]
>>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
>>>> [4.306s]
>>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> > [INFO] BUILD FAILURE
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> > [INFO] Total time: 15.561s
>>>> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
>>>> > [INFO] Final Memory: 35M/367M
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>>> > 1-4) MSC000001: Failed to start service
>>>> > jboss.undertow.deployment.default-server.default-host./auth:
>>>> > org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> > Caused by: java.lang.RuntimeException: Failed to construct public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     at
>>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>>>> >     at
>>>> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>>>> >     at
>>>> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>>>> >     at
>>>> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>>>> >     at
>>>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>>>> >     at
>>>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>>>> >     at
>>>> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>>>> >     at
>>>> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>>>> >     at
>>>> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>>>> >     at
>>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>>>> >     at
>>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     ... 3 more
>>>> > Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     at
>>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>>>> >     at
>>>> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>>>> >     at
>>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>>>> >     at
>>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>>>> >     at
>>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>>>> >     at
>>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>>> >     at
>>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>>>> >     at
>>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>>>> >     at
>>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>>> >     at
>>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>>>> >     at
>>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>>>> >     at
>>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>>>> >     at
>>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>>>> >     at
>>>> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>>>> >     at
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>>>> >     at
>>>> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>>>> >     at
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>>>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>> > Method) [rt.jar:1.7.0_45]
>>>> >     at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>>>> >     ... 15 more
>>>> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
>>>> > JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     at
>>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>>>> >     at
>>>> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>>>> >     at
>>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>>> >     at
>>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>>>> >     at
>>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>>>> >     at
>>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>>> >     at
>>>> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>>>> >     at
>>>> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>>>> >     at
>>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>>>> >     at
>>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>>>> >     at
>>>> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>>>> >     at
>>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>>>> >     at
>>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>>>> >     ... 36 more
>>>> > Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>>>> >     at
>>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>>>> >     at
>>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>>>> >     at
>>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>>> >     at
>>>> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>>>> >     at
>>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>>>> >     ... 52 more
>>>> >
>>>> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
>>>> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
>>>> > failed - address: ([("deployment" => "auth-server.war")]) - failure
>>>> > description: {"JBAS014671: Failed services" =>
>>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>>> > "org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>>> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
>>>> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
>>>> > with the following failure message:
>>>> > {"JBAS014671: Failed services" =>
>>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>>> > "org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>>> >
>>>> > Using java version ?1.8.0_25?
>>>> > ------------------------------
>>>> > JBoss AS 7.1
>>>> >
>>>> > I can not start JBoss AS 7.1 using Java 8
>>>> >
>>>> > [passos]: ~
>>>> > ?
>>>> ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
>>>> > -b 0.0.0.0
>>>> >
>>>> =========================================================================
>>>> >
>>>> >   JBoss Bootstrap Environment
>>>> >
>>>> >   JBOSS_HOME:
>>>> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>>>> >
>>>> >   JAVA: java
>>>> >
>>>> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
>>>> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
>>>> > -Dorg.jboss.resolver.warning=true
>>>> > -Dsun.rmi.dgc.client.gcInterval=3600000
>>>> > -Dsun.rmi.dgc.server.gcInterval=3600000
>>>> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>>>> > -Djboss.server.default.config=standalone.xml
>>>> >
>>>> >
>>>> =========================================================================
>>>> >
>>>> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>>> > MaxPermSize=256m; support was removed in 8.0
>>>> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
>>>> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
>>>> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
>>>> > "Brontes" starting
>>>> >
>>>> > Wildfly 8.1.0 Deploy
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn wildfly:deploy -Pwildfly
>>>> >
>>>> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
>>>> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
>>>> > deploy against EAP, but I'm not sure that matters given the error
>>>> > looks to be JDK/path/version-based.
>>>> > [ERROR] Failed to execute goal
>>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>>> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
>>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>>> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
>>>> > one of its dependencies could not be resolved: Could not find artifact
>>>> > sun.jdk:jconsole:jar:jdk at specified path
>>>> >
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
>>>> > -> [Help 1]
>>>> >
>>>> > I found the same problem in SwitchYard quickstart
>>>> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
>>>> >
>>>> > ? Passos
>>>> > ?
>>>>
>>>> > _______________________________________________
>>>> > aerogear-dev mailing list
>>>> > aerogear-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> --
>>>>
>>>> abstractj
>>>> PGP: 0x84DC9914
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>
> --
> 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/20141021/5c59c6a8/attachment-0001.html 

From matzew at apache.org  Tue Oct 21 07:57:13 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 13:57:13 +0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbvoYqXuQ0-7AZTBXTNQ5dDcaKbKAoTZ4577YgLGtkZkDw@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
	<CAKjsGbvoYqXuQ0-7AZTBXTNQ5dDcaKbKAoTZ4577YgLGtkZkDw@mail.gmail.com>
Message-ID: <CAAg5f2SiBuD2duAycKzUBK18j3EE98B_V+OZy9qUe8zToEowmw@mail.gmail.com>

yes, there are some issues with the docklet generator.

I think qmx recently looked into JDK8;



On Tuesday, October 21, 2014, Daniel Passos <daniel at passos.me> wrote:

> Also I?m getting this when I try compile the project using Java 8. Maybe
> is a good idea add Java 8 on travis build.
>
> [ERROR] The given File link: /Users/passos/Development/Projects/AeroGear/aerogear-unifiedpush-server/jaxrs/../target/site/apidocs is not a dir.
> [ERROR] Error fetching link: /Users/passos/Development/Projects/AeroGear/aerogear-unifiedpush-server/jaxrs/../target/site/apidocs/package-list. Ignored it.
> [INFO]
> Loading source files for package org.jboss.aerogear.unifiedpush.rest...
> Loading source files for package org.jboss.aerogear.unifiedpush.rest.annotations...
> Loading source files for package org.jboss.aerogear.unifiedpush.rest.registry.installations...
> Loading source files for package org.jboss.aerogear.unifiedpush.rest.sender...
> Constructing Javadoc information...
> 1 error
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [1.981s]
> [INFO] UnifiedPush Model Layer ........................... SUCCESS [0.052s]
> [INFO] UnifiedPush Server Model API ...................... SUCCESS [3.359s]
> [INFO] UnifiedPush Server Model JPA implementation ....... SUCCESS [16.161s]
> [INFO] UnifiedPush Service Layer ......................... SUCCESS [21.848s]
> [INFO] UnifiedPush Push Notification Networks ............ SUCCESS [3.745s]
> [INFO] UnifiedPush RESTful Endpoint ...................... FAILURE [2.425s]
> [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED
> [INFO] UnifiedPush Dependencies Parent ................... SKIPPED
> [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED
> [INFO] UnifiedPush Auth Server ........................... SKIPPED
> [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED
> [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED
> [INFO] UnifiedPush Servers Parent ........................ SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 50.770s
> [INFO] Finished at: Tue Oct 21 09:35:48 BRST 2014
> [INFO] Final Memory: 88M/716M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc (jax-rs-docs) on project unifiedpush-jaxrs: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - javadoc: error - In doclet class com.lunatech.doclets.jax.jaxrs.JAXRSDoclet,  method start has thrown an exception java.lang.reflect.InvocationTargetException
> [ERROR] java.lang.NullPointerException
> [ERROR] at com.lunatech.doclets.jax.jaxrs.JAXRSDoclet.<init>(JAXRSDoclet.java:84)
> [ERROR] at com.lunatech.doclets.jax.jaxrs.JAXRSDoclet.start(JAXRSDoclet.java:78)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:483)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:310)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:189)
> [ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:366)
> [ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:219)
> [ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:205)
> [ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:64)
> [ERROR] at com.sun.tools.javadoc.Main.main(Main.java:54)
> [ERROR]
> [ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/javadoc @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/Users/passos/Development/Projects/AeroGear/aerogear-unifiedpush-server/jaxrs/target/site/apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :unifiedpush-jaxrs
>
> ?
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/3a1dcfd9/attachment.html 

From matzew at apache.org  Tue Oct 21 07:59:13 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 13:59:13 +0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
Message-ID: <CAAg5f2RBYPTZSVG7ttOwCjLh5ZFNV_qMZd4fTkqgMkK54DjceA@mail.gmail.com>

hrm, not sure whats up w/ the deployment plugin

one question; you did mvn install before deployment?

On Tuesday, October 21, 2014, Daniel Passos <daniel at passos.me> wrote:

> As Matthias suggested, here is my test using a clean instance of JBoss EAP
> 6.2GA
>
> I?ve got the same problem using Java ?1.7.0_45? and ?1.8.0_25?
> Generate the UnifiedPush Database and Datasource
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers [git:pr/408]
> ? ~/Development/Java/Server/JBoss/jboss-eap-6.3/bin/jboss-cli.sh --file=../databases/h2-database-config.cli
> The batch executed successfully
>
> Deploy
>
> [passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers [git:pr/408]
> ? mvn jboss-as:deploy -Pas7
> .
> .
> .
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] UnifiedPush Auth Server ........................... SUCCESS [12.755s]
> [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE [4.050s]
> [INFO] UnifiedPush Servers Parent ........................ SKIPPED
> [INFO] ------------------------------------------------------------------------
>
> Server Log
>
> 09:29:09,889 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."ag-push.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."ag-push.war".WeldStartService: Failed to start service
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
>     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [HttpServletRequest] with qualifiers [@Default] at injection point [[parameter 1] of [constructor] @Inject public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>     at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:315)
>     at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
>     at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:147)
>     at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
>     at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:386)
>     at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371)
>     at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
>     at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64)
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
>     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
>     ... 3 more
>
> 09:29:09,900 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ag-push.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ag-push.war\".WeldStartService: Failed to start service
>     Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [HttpServletRequest] with qualifiers [@Default] at injection point [[parameter 1] of [constructor] @Inject public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]"}}
>
> ?
>
> On Tue, Oct 21, 2014 at 9:20 AM, Daniel Passos <daniel at passos.me
> <javascript:_e(%7B%7D,'cvml','daniel at passos.me');>> wrote:
>
>> On Tue, Oct 21, 2014 at 6:12 AM, Matthias Wessendorf <matzew at apache.org
>> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>>
>>> Hello passos,
>>>
>>> regarding JBoss AS7.1 it's not really supported, especially after we
>>> added a scheduler to 1.0.0.Final:
>>> https://issues.jboss.org/browse/AS7-4694
>>>
>>
>> So, we need update our READMEs/Docs ASAP
>>
>> Please use EAP 6.3.GA instead.
>>>
>>> Also, I think they (EAP) do not support JDK8.
>>>
>>> But yeah, on Wildfly Java8 is first-class citizens ;-)
>>>
>>> greetings from Slovenia
>>>
>>> On Tue, Oct 21, 2014 at 4:02 AM, Bruno Oliveira <bruno at abstractj.org
>>> <javascript:_e(%7B%7D,'cvml','bruno at abstractj.org');>> wrote:
>>>
>>>> Good morning Passos, would you mind to try the following steps?
>>>>
>>>> - WildFly 8.1.0
>>>>
>>>> 1. remove any previous installation of WildFly to make sure that we're
>>>> dealing with a fresh environment
>>>> 2. mvn clean install -DskipTests=true -Dcheckstyle.skip=true
>>>> 3. Start WildFly
>>>> 4. cp databases/unifiedpush-h2-ds.xml $JBOSS_HOME/standalone/deployments
>>>> 5. cp servers/auth-server/target/auth-server.war
>>>> $JBOSS_HOME/standalone/deployments
>>>> 6. cp servers/ups-wildfly/target/ag-push.war
>>>> $JBOSS_HOME/standalone/deployments
>>>>
>>>>
>>>> Note: Here I did a rm -rf ~/.m2/repository/org/jboss/aerogear for a
>>>> fresh setup.
>>>>
>>>> I know manual deploy is not awesome, but help us to debug what's goign
>>>> on.
>>>>
>>>> On JBoss AS 7.1.1 I was able to reproduce your issue and will look at
>>>> this, thanks for testing.
>>>>
>>>>
>>>>
>>>> On 2014-10-20, Daniel Passos wrote:
>>>> > Hey Guys,
>>>> >
>>>> > Today I?ve spend a lot of time (without success), trying test #408
>>>> > <https://github.com/aerogear/aerogear-unifiedpush-server/pull/408>
>>>> using a
>>>> > new JBoss AS 7.1/Wildfly 8.1.0 installations
>>>> > Using Java version ?1.7.0_45?
>>>> > ------------------------------
>>>> > JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ?
>>>> ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
>>>> > --file=../databases/h2-database-config.cli
>>>> > #1 data-source add --name=UnifiedPushDS --driver-name=h2
>>>> > --jndi-name=java:jboss/datasources/UnifiedPushDS
>>>> >
>>>> --connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
>>>> > --user-name=sa --password=sa --use-ccm=true
>>>> > #2 data-source enable --name=UnifiedPushDS
>>>> > The batch executed successfully.
>>>> >
>>>> > Deployment
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn jboss-as:deploy -Pas7
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>>> > 1-8) MSC00001: Failed to start service
>>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>>> > org.jboss.msc.service.StartException in service
>>>> > jboss.deployment.unit."ag-push.war".WeldService:
>>>> > org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
>>>> > dependencies for type [HttpServletRequest] with qualifiers [@Default]
>>>> > at injection point [[parameter 1] of [constructor] @Inject public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>>> >     at
>>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>>>> > [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
>>>> > Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
>>>> > [@Default] at injection point [[parameter 1] of [constructor] @Inject
>>>> > public
>>>> org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
>>>> >     at
>>>> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
>>>> >     at
>>>> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
>>>> >     at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
>>>> >     at
>>>> org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
>>>> >     ... 5 more
>>>> >
>>>> > Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
>>>> > --file=../databases/h2-database-config.cli
>>>> > The batch failed with the following error (you are remaining in the
>>>> > batch editing mode to have a chance to correct the error):
>>>> > {"JBAS014653: Composite operation failed and was rolled back. Steps
>>>> > that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
>>>> > failed: Service jboss.data-source-config.UnifiedPushDS is already
>>>> > registered"}}
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:49:48,359 INFO  [org.jboss.as.connector.subsystems.datasources]
>>>> > (MSC service thread 1-2) JBAS010400: Bound data source
>>>> > [java:jboss/datasources/UnifiedPushDS]
>>>> > 19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
>>>> > (management-handler-thread - 1) JBAS014612: Operation ("add") failed -
>>>> > address: ([
>>>> >     ("subsystem" => "datasources"),
>>>> >     ("data-source" => "UnifiedPushDS")
>>>> > ]): org.jboss.msc.service.DuplicateServiceException: Service
>>>> > jboss.data-source-config.UnifiedPushDS is already registered
>>>> >     at
>>>> org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
>>>> >     at
>>>> org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at java.security.AccessController.doPrivileged(Native Method)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at javax.security.auth.Subject.doAs(Subject.java:415)
>>>> [rt.jar:1.7.0_45]
>>>> >     at
>>>> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
>>>> > [wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
>>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
>>>> > [wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> >     at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>>> > [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>>>> >
>>>> > 19:49:48,376 INFO  [org.jboss.as.connector.subsystems.datasources]
>>>> > (MSC service thread 1-7) JBAS010409: Unbound data source
>>>> > [java:jboss/datasources/UnifiedPushDS]
>>>> >
>>>> > Deployment
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn wildfly:deploy -Pwildfly
>>>> > .
>>>> > .
>>>> > .
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> > [INFO] Reactor Summary:
>>>> > [INFO]
>>>> > [INFO] UnifiedPush Auth Server ........................... SUCCESS
>>>> [10.217s]
>>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE
>>>> [4.306s]
>>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> > [INFO] BUILD FAILURE
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> > [INFO] Total time: 15.561s
>>>> > [INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
>>>> > [INFO] Final Memory: 35M/367M
>>>> > [INFO]
>>>> ------------------------------------------------------------------------
>>>> >
>>>> > Server Log
>>>> >
>>>> > 19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
>>>> > 1-4) MSC000001: Failed to start service
>>>> > jboss.undertow.deployment.default-server.default-host./auth:
>>>> > org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>>> > Caused by: java.lang.RuntimeException: Failed to construct public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     at
>>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
>>>> >     at
>>>> org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
>>>> >     at
>>>> org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
>>>> >     at
>>>> org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
>>>> >     at
>>>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
>>>> >     at
>>>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
>>>> >     at
>>>> io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
>>>> >     at
>>>> io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
>>>> >     at
>>>> io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
>>>> >     at
>>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
>>>> >     at
>>>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     at
>>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>>>> > [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>>> >     ... 3 more
>>>> > Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     at
>>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
>>>> >     at
>>>> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
>>>> >     at
>>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
>>>> >     at
>>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
>>>> >     at
>>>> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
>>>> >     at
>>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>>> >     at
>>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
>>>> >     at
>>>> org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
>>>> >     at
>>>> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
>>>> >     at
>>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
>>>> >     at
>>>> org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
>>>> >     at
>>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
>>>> >     at
>>>> org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
>>>> >     at
>>>> org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
>>>> >     at
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
>>>> >     at
>>>> org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
>>>> >     at
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
>>>> >     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>> > Method) [rt.jar:1.7.0_45]
>>>> >     at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>>>> >     ... 15 more
>>>> > Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
>>>> > JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     at
>>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
>>>> >     at
>>>> org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
>>>> >     at
>>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>>> >     at
>>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
>>>> >     at
>>>> org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
>>>> >     at
>>>> org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
>>>> >     at
>>>> org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
>>>> >     at
>>>> org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
>>>> >     at
>>>> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
>>>> >     at
>>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
>>>> >     at
>>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
>>>> >     at
>>>> org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
>>>> >     at
>>>> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
>>>> >     at
>>>> org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
>>>> >     ... 36 more
>>>> > Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS
>>>> >     at
>>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
>>>> >     at
>>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
>>>> >     at
>>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>>> >     at
>>>> org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
>>>> >     at
>>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at javax.naming.InitialContext.lookup(InitialContext.java:415)
>>>> > [rt.jar:1.7.0_45]
>>>> >     at
>>>> org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
>>>> >     ... 52 more
>>>> >
>>>> > 19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
>>>> > (management-handler-thread - 1) JBAS014613: Operation ("deploy")
>>>> > failed - address: ([("deployment" => "auth-server.war")]) - failure
>>>> > description: {"JBAS014671: Failed services" =>
>>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>>> > "org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>>> > 19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
>>>> > 1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
>>>> > with the following failure message:
>>>> > {"JBAS014671: Failed services" =>
>>>> > {"jboss.undertow.deployment.default-server.default-host./auth" =>
>>>> > "org.jboss.msc.service.StartException in service
>>>> > jboss.undertow.deployment.default-server.default-host./auth: Failed to
>>>> > start service
>>>> >     Caused by: java.lang.RuntimeException: Failed to construct public
>>>> >
>>>> org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
>>>> >     Caused by: javax.persistence.PersistenceException: Unable to build
>>>> > entity manager factory
>>>> >     Caused by: org.hibernate.engine.jndi.JndiException: Unable to
>>>> > lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
>>>> >     Caused by: javax.naming.NameNotFoundException:
>>>> > datasources/UnifiedPushDS -- service
>>>> > jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
>>>> >
>>>> > Using java version ?1.8.0_25?
>>>> > ------------------------------
>>>> > JBoss AS 7.1
>>>> >
>>>> > I can not start JBoss AS 7.1 using Java 8
>>>> >
>>>> > [passos]: ~
>>>> > ?
>>>> ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
>>>> > -b 0.0.0.0
>>>> >
>>>> =========================================================================
>>>> >
>>>> >   JBoss Bootstrap Environment
>>>> >
>>>> >   JBOSS_HOME:
>>>> /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
>>>> >
>>>> >   JAVA: java
>>>> >
>>>> >   JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation
>>>> > -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
>>>> > -Dorg.jboss.resolver.warning=true
>>>> > -Dsun.rmi.dgc.client.gcInterval=3600000
>>>> > -Dsun.rmi.dgc.server.gcInterval=3600000
>>>> > -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>>>> > -Djboss.server.default.config=standalone.xml
>>>> >
>>>> >
>>>> =========================================================================
>>>> >
>>>> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>>> > MaxPermSize=256m; support was removed in 8.0
>>>> > 19:42:02,527 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
>>>> > 19:42:02,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
>>>> > 19:42:02,947 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
>>>> > "Brontes" starting
>>>> >
>>>> > Wildfly 8.1.0 Deploy
>>>> >
>>>> > [passos]:
>>>> ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
>>>> > [git:pr/408]
>>>> > ? mvn wildfly:deploy -Pwildfly
>>>> >
>>>> > Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
>>>> > X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
>>>> > deploy against EAP, but I'm not sure that matters given the error
>>>> > looks to be JDK/path/version-based.
>>>> > [ERROR] Failed to execute goal
>>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>>> > (deploy) on project switchyard-validate-xml: Execution deploy of goal
>>>> > org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
>>>> > failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
>>>> > one of its dependencies could not be resolved: Could not find artifact
>>>> > sun.jdk:jconsole:jar:jdk at specified path
>>>> >
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
>>>> > -> [Help 1]
>>>> >
>>>> > I found the same problem in SwitchYard quickstart
>>>> > <https://issues.jboss.org/browse/SWITCHYARD-2315>
>>>> >
>>>> > ? Passos
>>>> > ?
>>>>
>>>> > _______________________________________________
>>>> > aerogear-dev mailing list
>>>> > aerogear-dev at lists.jboss.org
>>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> --
>>>>
>>>> abstractj
>>>> PGP: 0x84DC9914
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://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:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/5f6c9644/attachment-0001.html 

From daniel at passos.me  Tue Oct 21 08:12:34 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 21 Oct 2014 10:12:34 -0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAAg5f2RBYPTZSVG7ttOwCjLh5ZFNV_qMZd4fTkqgMkK54DjceA@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
	<CAAg5f2RBYPTZSVG7ttOwCjLh5ZFNV_qMZd4fTkqgMkK54DjceA@mail.gmail.com>
Message-ID: <CAKjsGbsx7XMXSXpxLcdSwA13udAM+W=uYKFON8DhCHY9stEtzQ@mail.gmail.com>

On Tue, Oct 21, 2014 at 9:59 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

hrm, not sure whats up w/ the deployment plugin
>
> one question; you did mvn install before deployment?
>
mvn clean install
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/7ab78ba4/attachment.html 

From io.christod at gmail.com  Tue Oct 21 09:01:59 2014
From: io.christod at gmail.com (JChrist)
Date: Tue, 21 Oct 2014 06:01:59 -0700 (PDT)
Subject: [aerogear-dev] Upgrade from 0.10.2
Message-ID: <1413896519586-9545.post@n5.nabble.com>

Hello everyone.
I am currently using the Aerogear Unified Push Server v 0.10.2 and have
already gathered a number of installations on one application variant (an
iOS app).
I was thinking about upgrading to the latest version (the v1.0.x series) and
I would greatly appreciate if you could point out an upgrade plan (if such
exists), so as to not lose the existing installations.

Kind regards



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From cvasilak at gmail.com  Tue Oct 21 10:16:11 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 21 Oct 2014 17:16:11 +0300
Subject: [aerogear-dev] iOS meeting to prepare 2.1 release
In-Reply-To: <83AC41B1-3276-47CC-A179-945B180C75B0@gmail.com>
References: <83AC41B1-3276-47CC-A179-945B180C75B0@gmail.com>
Message-ID: <E5A38F7C-9888-4E2A-AD34-1FB1A1C72A88@gmail.com>

fyi,

meeting minutes

<jbott>	 Ending meeting. Generating minutes. Be patient :)
<jbott>	 Meeting ended Tue Oct 21 14:14:10 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-10-21-14.00.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-21-14.00.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-21-14.00.log.html

On Oct 20, 2014, at 11:40 AM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello iOS world!
> 
> Our next iOS meeting we will focus on organizing 2.1 release.
> Be warmed it could be a long list of JIRAs in it. For now here is a skeleton of meeting agenda (to be completed):
> http://oksoclap.com/p/planning_ios_2.1
> 
> Let?s meet Tuesday 21st October 4pm (CEST - UTC + 2hours) on IRC #aerogear
> See you all there.
> 
> ++
> Corinne
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From matzew at apache.org  Tue Oct 21 10:40:00 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 16:40:00 +0200
Subject: [aerogear-dev] Upgrade from 0.10.2
In-Reply-To: <1413896519586-9545.post@n5.nabble.com>
References: <1413896519586-9545.post@n5.nabble.com>
Message-ID: <CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>

hello jchrist!

looks like you need a way to export the installations. perhaps you need to
do it by hand.

any reasons for not updating to 1.0.1?
that has import ;) so the above "select * from installations" result could
be used to populate the json import file

-Matthias

On Tuesday, October 21, 2014, JChrist <io.christod at gmail.com> wrote:

> Hello everyone.
> I am currently using the Aerogear Unified Push Server v 0.10.2 and have
> already gathered a number of installations on one application variant (an
> iOS app).
> I was thinking about upgrading to the latest version (the v1.0.x series)
> and
> I would greatly appreciate if you could point out an upgrade plan (if such
> exists), so as to not lose the existing installations.
>
> Kind regards
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.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/20141021/e7fcd788/attachment.html 

From matzew at apache.org  Tue Oct 21 10:49:09 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 16:49:09 +0200
Subject: [aerogear-dev] Upgrade from 0.10.2
In-Reply-To: <CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>
References: <1413896519586-9545.post@n5.nabble.com>
	<CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>
Message-ID: <CAAg5f2RDv-HK5hsOCDOT1B_PHGrLkP2RUeM6mD3ZiJj0uZQVXw@mail.gmail.com>

i think we need to import the variant as well, because of device
registrations!

On Tuesday, October 21, 2014, Matthias Wessendorf <matzew at apache.org> wrote:

> hello jchrist!
>
> looks like you need a way to export the installations. perhaps you need to
> do it by hand.
>
> any reasons for not updating to 1.0.1?
> that has import ;) so the above "select * from installations" result could
> be used to populate the json import file
>
> -Matthias
>
> On Tuesday, October 21, 2014, JChrist <io.christod at gmail.com
> <javascript:_e(%7B%7D,'cvml','io.christod at gmail.com');>> wrote:
>
>> Hello everyone.
>> I am currently using the Aerogear Unified Push Server v 0.10.2 and have
>> already gathered a number of installations on one application variant (an
>> iOS app).
>> I was thinking about upgrading to the latest version (the v1.0.x series)
>> and
>> I would greatly appreciate if you could point out an upgrade plan (if such
>> exists), so as to not lose the existing installations.
>>
>> Kind regards
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> --
> Sent from Gmail Mobile
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/541e8b36/attachment.html 

From io.christod at gmail.com  Tue Oct 21 10:52:54 2014
From: io.christod at gmail.com (Ioannis Christodoulou)
Date: Tue, 21 Oct 2014 17:52:54 +0300
Subject: [aerogear-dev] Upgrade from 0.10.2
In-Reply-To: <CAAg5f2RDv-HK5hsOCDOT1B_PHGrLkP2RUeM6mD3ZiJj0uZQVXw@mail.gmail.com>
References: <1413896519586-9545.post@n5.nabble.com>
	<CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>
	<CAAg5f2RDv-HK5hsOCDOT1B_PHGrLkP2RUeM6mD3ZiJj0uZQVXw@mail.gmail.com>
Message-ID: <CAJbmAJEa9ibQ39+z9KbJDruX51uPUMEUHo+Za2Eko4ytSGbe8Q@mail.gmail.com>

Hello matthias, thanks for the fast response.
Just to make sure I completely follow you, the steps would be:
* export the iOS variant and the installations (to csv perhaps?)
* replace the UPS war(s).
* truncate the db
* import the previously exported variant and installations

is that right?

Kind regards,
Ioannis Christodoulou

????????? ????,
   ??????? ????????????

On Tue, Oct 21, 2014 at 5:49 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> i think we need to import the variant as well, because of device
> registrations!
>
>
> On Tuesday, October 21, 2014, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> hello jchrist!
>>
>> looks like you need a way to export the installations. perhaps you need
>> to do it by hand.
>>
>> any reasons for not updating to 1.0.1?
>> that has import ;) so the above "select * from installations" result
>> could be used to populate the json import file
>>
>> -Matthias
>>
>> On Tuesday, October 21, 2014, JChrist <io.christod at gmail.com> wrote:
>>
>>> Hello everyone.
>>> I am currently using the Aerogear Unified Push Server v 0.10.2 and have
>>> already gathered a number of installations on one application variant (an
>>> iOS app).
>>> I was thinking about upgrading to the latest version (the v1.0.x series)
>>> and
>>> I would greatly appreciate if you could point out an upgrade plan (if
>>> such
>>> exists), so as to not lose the existing installations.
>>>
>>> Kind regards
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>
>
> --
> 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/20141021/3aa419be/attachment.html 

From matzew at apache.org  Tue Oct 21 11:39:12 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 17:39:12 +0200
Subject: [aerogear-dev] Upgrade from 0.10.2
In-Reply-To: <CAJbmAJEa9ibQ39+z9KbJDruX51uPUMEUHo+Za2Eko4ytSGbe8Q@mail.gmail.com>
References: <1413896519586-9545.post@n5.nabble.com>
	<CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>
	<CAAg5f2RDv-HK5hsOCDOT1B_PHGrLkP2RUeM6mD3ZiJj0uZQVXw@mail.gmail.com>
	<CAJbmAJEa9ibQ39+z9KbJDruX51uPUMEUHo+Za2Eko4ytSGbe8Q@mail.gmail.com>
Message-ID: <CAAg5f2ReDiDV15BJPWwEO4QyPt3RMDSXjzc2Lz0h1PiBDjah=w@mail.gmail.com>

hi Ioannis!

yes! only issue is: no variant import atm(i will open a jira).
you would need to "edit" the variantId/secret in the new database :-)

On Tuesday, October 21, 2014, Ioannis Christodoulou <io.christod at gmail.com>
wrote:

> Hello matthias, thanks for the fast response.
> Just to make sure I completely follow you, the steps would be:
> * export the iOS variant and the installations (to csv perhaps?)
> * replace the UPS war(s).
> * truncate the db
> * import the previously exported variant and installations
>
> is that right?
>
> Kind regards,
> Ioannis Christodoulou
>
> ????????? ????,
>    ??????? ????????????
>
> On Tue, Oct 21, 2014 at 5:49 PM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>> i think we need to import the variant as well, because of device
>> registrations!
>>
>>
>> On Tuesday, October 21, 2014, Matthias Wessendorf <matzew at apache.org
>> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>>
>>> hello jchrist!
>>>
>>> looks like you need a way to export the installations. perhaps you need
>>> to do it by hand.
>>>
>>> any reasons for not updating to 1.0.1?
>>> that has import ;) so the above "select * from installations" result
>>> could be used to populate the json import file
>>>
>>> -Matthias
>>>
>>> On Tuesday, October 21, 2014, JChrist <io.christod at gmail.com> wrote:
>>>
>>>> Hello everyone.
>>>> I am currently using the Aerogear Unified Push Server v 0.10.2 and have
>>>> already gathered a number of installations on one application variant
>>>> (an
>>>> iOS app).
>>>> I was thinking about upgrading to the latest version (the v1.0.x
>>>> series) and
>>>> I would greatly appreciate if you could point out an upgrade plan (if
>>>> such
>>>> exists), so as to not lose the existing installations.
>>>>
>>>> Kind regards
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/0232dc26/attachment-0001.html 

From io.christod at gmail.com  Tue Oct 21 11:41:58 2014
From: io.christod at gmail.com (Ioannis Christodoulou)
Date: Tue, 21 Oct 2014 18:41:58 +0300
Subject: [aerogear-dev] Upgrade from 0.10.2
In-Reply-To: <CAAg5f2ReDiDV15BJPWwEO4QyPt3RMDSXjzc2Lz0h1PiBDjah=w@mail.gmail.com>
References: <1413896519586-9545.post@n5.nabble.com>
	<CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>
	<CAAg5f2RDv-HK5hsOCDOT1B_PHGrLkP2RUeM6mD3ZiJj0uZQVXw@mail.gmail.com>
	<CAJbmAJEa9ibQ39+z9KbJDruX51uPUMEUHo+Za2Eko4ytSGbe8Q@mail.gmail.com>
	<CAAg5f2ReDiDV15BJPWwEO4QyPt3RMDSXjzc2Lz0h1PiBDjah=w@mail.gmail.com>
Message-ID: <CAJbmAJG5yFfTMM6Pj3iQbeR6xk6Kq+gQYKvjc2vfWn1bqGnJng@mail.gmail.com>

amazing,
thanks a lot matthias!

Kind regards,
Ioannis Christodoulou

On Tue, Oct 21, 2014 at 6:39 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> hi Ioannis!
>
> yes! only issue is: no variant import atm(i will open a jira).
> you would need to "edit" the variantId/secret in the new database :-)
>
>
> On Tuesday, October 21, 2014, Ioannis Christodoulou <io.christod at gmail.com>
> wrote:
>
>> Hello matthias, thanks for the fast response.
>> Just to make sure I completely follow you, the steps would be:
>> * export the iOS variant and the installations (to csv perhaps?)
>> * replace the UPS war(s).
>> * truncate the db
>> * import the previously exported variant and installations
>>
>> is that right?
>>
>> Kind regards,
>> Ioannis Christodoulou
>>
>> ????????? ????,
>>    ??????? ????????????
>>
>> On Tue, Oct 21, 2014 at 5:49 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> i think we need to import the variant as well, because of device
>>> registrations!
>>>
>>>
>>> On Tuesday, October 21, 2014, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> hello jchrist!
>>>>
>>>> looks like you need a way to export the installations. perhaps you need
>>>> to do it by hand.
>>>>
>>>> any reasons for not updating to 1.0.1?
>>>> that has import ;) so the above "select * from installations" result
>>>> could be used to populate the json import file
>>>>
>>>> -Matthias
>>>>
>>>> On Tuesday, October 21, 2014, JChrist <io.christod at gmail.com> wrote:
>>>>
>>>>> Hello everyone.
>>>>> I am currently using the Aerogear Unified Push Server v 0.10.2 and have
>>>>> already gathered a number of installations on one application variant
>>>>> (an
>>>>> iOS app).
>>>>> I was thinking about upgrading to the latest version (the v1.0.x
>>>>> series) and
>>>>> I would greatly appreciate if you could point out an upgrade plan (if
>>>>> such
>>>>> exists), so as to not lose the existing installations.
>>>>>
>>>>> Kind regards
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>
> --
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/b572a1c6/attachment.html 

From matzew at apache.org  Tue Oct 21 12:12:58 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 18:12:58 +0200
Subject: [aerogear-dev] Problems to setup UPS
In-Reply-To: <CAKjsGbsx7XMXSXpxLcdSwA13udAM+W=uYKFON8DhCHY9stEtzQ@mail.gmail.com>
References: <CAKjsGbvzMSdPX0H+V=X3NAS_3HqG-+f2VPGq6Xbkv-sGNqZjkw@mail.gmail.com>
	<20141021020208.GA15719@abstractj.org>
	<CAAg5f2Tdhg2Pf8jAz82oZxSsrk_XOKi=2oSMME1+NBf5sbB11Q@mail.gmail.com>
	<CAKjsGbtTNj2VwNBgGhe4BYQrveiHSV5nbR-R0+E9z0gZr1Rk2w@mail.gmail.com>
	<CAKjsGbvrhf41Myb9UjyQgXpUkmJTzObpQDgT_6cuW5f0EV_z8w@mail.gmail.com>
	<CAAg5f2RBYPTZSVG7ttOwCjLh5ZFNV_qMZd4fTkqgMkK54DjceA@mail.gmail.com>
	<CAKjsGbsx7XMXSXpxLcdSwA13udAM+W=uYKFON8DhCHY9stEtzQ@mail.gmail.com>
Message-ID: <CAAg5f2Q32UjnLXVT6pE8buJTxgROEny_HV+gMBkLH_UqveO0Yg@mail.gmail.com>

hrm, weird. not sure but it could be that the plugin has some issue, will
give it a try tomorrow!


On Tue, Oct 21, 2014 at 2:12 PM, Daniel Passos <daniel at passos.me> wrote:

> On Tue, Oct 21, 2014 at 9:59 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> hrm, not sure whats up w/ the deployment plugin
>>
>> one question; you did mvn install before deployment?
>>
> mvn clean install
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141021/b7e5188f/attachment.html 

From matzew at apache.org  Tue Oct 21 14:35:42 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 21 Oct 2014 20:35:42 +0200
Subject: [aerogear-dev] Upgrade from 0.10.2
In-Reply-To: <CAJbmAJG5yFfTMM6Pj3iQbeR6xk6Kq+gQYKvjc2vfWn1bqGnJng@mail.gmail.com>
References: <1413896519586-9545.post@n5.nabble.com>
	<CAAg5f2R_trkAS8p8gGW9b4W-sdMdZcaPakHMgGJCCohmc72NdA@mail.gmail.com>
	<CAAg5f2RDv-HK5hsOCDOT1B_PHGrLkP2RUeM6mD3ZiJj0uZQVXw@mail.gmail.com>
	<CAJbmAJEa9ibQ39+z9KbJDruX51uPUMEUHo+Za2Eko4ytSGbe8Q@mail.gmail.com>
	<CAAg5f2ReDiDV15BJPWwEO4QyPt3RMDSXjzc2Lz0h1PiBDjah=w@mail.gmail.com>
	<CAJbmAJG5yFfTMM6Pj3iQbeR6xk6Kq+gQYKvjc2vfWn1bqGnJng@mail.gmail.com>
Message-ID: <CAAg5f2RuDRX9=G+3hyEs8in3y+Nb+J+AK9FE300SCwuXf4FNNg@mail.gmail.com>

let us know how it goes!

cheers,
matthias

On Tuesday, October 21, 2014, Ioannis Christodoulou <io.christod at gmail.com>
wrote:

> amazing,
> thanks a lot matthias!
>
> Kind regards,
> Ioannis Christodoulou
>
> On Tue, Oct 21, 2014 at 6:39 PM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>> hi Ioannis!
>>
>> yes! only issue is: no variant import atm(i will open a jira).
>> you would need to "edit" the variantId/secret in the new database :-)
>>
>>
>> On Tuesday, October 21, 2014, Ioannis Christodoulou <
>> io.christod at gmail.com
>> <javascript:_e(%7B%7D,'cvml','io.christod at gmail.com');>> wrote:
>>
>>> Hello matthias, thanks for the fast response.
>>> Just to make sure I completely follow you, the steps would be:
>>> * export the iOS variant and the installations (to csv perhaps?)
>>> * replace the UPS war(s).
>>> * truncate the db
>>> * import the previously exported variant and installations
>>>
>>> is that right?
>>>
>>> Kind regards,
>>> Ioannis Christodoulou
>>>
>>> ????????? ????,
>>>    ??????? ????????????
>>>
>>> On Tue, Oct 21, 2014 at 5:49 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> i think we need to import the variant as well, because of device
>>>> registrations!
>>>>
>>>>
>>>> On Tuesday, October 21, 2014, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>> hello jchrist!
>>>>>
>>>>> looks like you need a way to export the installations. perhaps you
>>>>> need to do it by hand.
>>>>>
>>>>> any reasons for not updating to 1.0.1?
>>>>> that has import ;) so the above "select * from installations" result
>>>>> could be used to populate the json import file
>>>>>
>>>>> -Matthias
>>>>>
>>>>> On Tuesday, October 21, 2014, JChrist <io.christod at gmail.com> wrote:
>>>>>
>>>>>> Hello everyone.
>>>>>> I am currently using the Aerogear Unified Push Server v 0.10.2 and
>>>>>> have
>>>>>> already gathered a number of installations on one application variant
>>>>>> (an
>>>>>> iOS app).
>>>>>> I was thinking about upgrading to the latest version (the v1.0.x
>>>>>> series) and
>>>>>> I would greatly appreciate if you could point out an upgrade plan (if
>>>>>> such
>>>>>> exists), so as to not lose the existing installations.
>>>>>>
>>>>>> Kind regards
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
>>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>>
>>>>
>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141021/2ca74c02/attachment.html 

From rajnukala at yahoo.com  Tue Oct 21 23:34:25 2014
From: rajnukala at yahoo.com (chansdad)
Date: Tue, 21 Oct 2014 20:34:25 -0700 (PDT)
Subject: [aerogear-dev] notification alert and app launched displays the
	alert
Message-ID: <1413948865382-9554.post@n5.nabble.com>

Hello 

I am testing aerogear for a project of mine . Able to send alerts . 

Here are couple of questions 
1. Can I send alerts based on a deviceId?
2. alerts is visible in the notifications panel in android . when i select
the alert , it takes me to the app . and when the app is active displays the
alert dialog on top of the app . can i disable this? when the app is not
active , alert is not displayed on the app screen.
3. Can i customize the alert as it displays on the screen.
4. Does aerogear support rich media notifications to be displayed on
homescreen. If not is there a plan to add this feature?

Thanks and to be honest , aerogear makes it super simple to send out
notifications .I still need to figure out if i can  send messages by
deviceId as that is my key requirement.

Regards




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/notification-alert-and-app-launched-displays-the-alert-tp9554.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Wed Oct 22 02:43:48 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 08:43:48 +0200
Subject: [aerogear-dev] [UPS] A thought: On MASTER only support WildFly?
Message-ID: <CAAg5f2Q555Pi6dWQDP_-xc=Zc9wAsvZLRJDeabNdbD2g+J6asA@mail.gmail.com>

Hello,

as said in the other email thread earlier this week ([1]) there is a bug in
the last JBoss AS 7.1 release (see [2]), that basically means the server
works properly only on EAP6.x and WildFly.

Because of that, I am wondering about removing the -as7 module (see [3]),
on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
usage reasons.

What do you guys think?

-Matthias

[1] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
[2] https://issues.jboss.org/browse/AS7-4694
[3]
https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7


-- 
Matthias Wessendorf

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

From matzew at apache.org  Wed Oct 22 02:44:52 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 08:44:52 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
	MASTER only support WildFly?)
Message-ID: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>

While at it :), as a follow-up thought on that, I am wondering if, on
MASTER, we should look into making it Java8?

-Matthias

On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello,
>
> as said in the other email thread earlier this week ([1]) there is a bug
> in the last JBoss AS 7.1 release (see [2]), that basically means the server
> works properly only on EAP6.x and WildFly.
>
> Because of that, I am wondering about removing the -as7 module (see [3]),
> on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
> usage reasons.
>
> What do you guys think?
>
> -Matthias
>
> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> [2] https://issues.jboss.org/browse/AS7-4694
> [3]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
>
>
> --
> 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/20141022/86f7d858/attachment.html 

From kpiwko at redhat.com  Wed Oct 22 04:33:52 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 22 Oct 2014 10:33:52 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
Message-ID: <1413966832.6296.27.camel@kpiwko-x220>

If master is WF only, that should work. 

If you guys keep EAP there, you'd need to target 1.6 and also not to use
1.8 for the runtime, see https://access.redhat.com/articles/111663 for
EAP supported configurations.

Karel

On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
> While at it :), as a follow-up thought on that, I am wondering if, on
> MASTER, we should look into making it Java8?
> 
> -Matthias
> 
> On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
> 
> > Hello,
> >
> > as said in the other email thread earlier this week ([1]) there is a bug
> > in the last JBoss AS 7.1 release (see [2]), that basically means the server
> > works properly only on EAP6.x and WildFly.
> >
> > Because of that, I am wondering about removing the -as7 module (see [3]),
> > on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
> > usage reasons.
> >
> > What do you guys think?
> >
> > -Matthias
> >
> > [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > [2] https://issues.jboss.org/browse/AS7-4694
> > [3]
> > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From matzew at apache.org  Wed Oct 22 04:35:58 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 10:35:58 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <1413966832.6296.27.camel@kpiwko-x220>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
Message-ID: <CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>

On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> If master is WF only, that should work.
>

yes, see original email :-)


>
> If you guys keep EAP there, you'd need to target 1.6 and also not to use
> 1.8 for the runtime, see https://access.redhat.com/articles/111663 for
> EAP supported configurations.
>
> Karel
>
> On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
> > While at it :), as a follow-up thought on that, I am wondering if, on
> > MASTER, we should look into making it Java8?
> >
> > -Matthias
> >
> > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> > > Hello,
> > >
> > > as said in the other email thread earlier this week ([1]) there is a
> bug
> > > in the last JBoss AS 7.1 release (see [2]), that basically means the
> server
> > > works properly only on EAP6.x and WildFly.
> > >
> > > Because of that, I am wondering about removing the -as7 module (see
> [3]),
> > > on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for
> EAP
> > > usage reasons.
> > >
> > > What do you guys think?
> > >
> > > -Matthias
> > >
> > > [1]
> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > > [2] https://issues.jboss.org/browse/AS7-4694
> > > [3]
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > >
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141022/44e9a6d4/attachment.html 

From kpiwko at redhat.com  Wed Oct 22 04:40:57 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 22 Oct 2014 10:40:57 +0200
Subject: [aerogear-dev] [UPS] A thought: On MASTER only support WildFly?
In-Reply-To: <CAAg5f2Q555Pi6dWQDP_-xc=Zc9wAsvZLRJDeabNdbD2g+J6asA@mail.gmail.com>
References: <CAAg5f2Q555Pi6dWQDP_-xc=Zc9wAsvZLRJDeabNdbD2g+J6asA@mail.gmail.com>
Message-ID: <1413967257.6296.29.camel@kpiwko-x220>

On Wed, 2014-10-22 at 08:43 +0200, Matthias Wessendorf wrote:
> Hello,
> 
> as said in the other email thread earlier this week ([1]) there is a bug in
> the last JBoss AS 7.1 release (see [2]), that basically means the server
> works properly only on EAP6.x and WildFly.
> 
> Because of that, I am wondering about removing the -as7 module (see [3]),
> on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
> usage reasons.

Sounds reasonable to me if there is an easy way how to backport from -wf
in 1.1.x (or 2.0.x) to -as7 in 1.0.x in case there is issue that
potentially affect both wars. Which should be pretty easy looking at
architecture of UPS ;-).

> 
> What do you guys think?
> 
> -Matthias
> 
> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> [2] https://issues.jboss.org/browse/AS7-4694
> [3]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> 
> 
> _______________________________________________
> 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 Oct 22 04:57:37 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Wed, 22 Oct 2014 10:57:37 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
Message-ID: <CAFJm-3Fo8Y5-Z8fdLTuZXiNQu4yowLcBxkPKePLYC5vhTWXz9w@mail.gmail.com>

+1 Sounds reasonable

On 22 October 2014 10:35, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
> On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> If master is WF only, that should work.
>>
>
> yes, see original email :-)
>
>
>>
>> If you guys keep EAP there, you'd need to target 1.6 and also not to use
>> 1.8 for the runtime, see https://access.redhat.com/articles/111663 for
>> EAP supported configurations.
>>
>> Karel
>>
>> On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
>> > While at it :), as a follow-up thought on that, I am wondering if, on
>> > MASTER, we should look into making it Java8?
>> >
>> > -Matthias
>> >
>> > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <matzew at apache.org
>> >
>> > wrote:
>> >
>> > > Hello,
>> > >
>> > > as said in the other email thread earlier this week ([1]) there is a
>> bug
>> > > in the last JBoss AS 7.1 release (see [2]), that basically means the
>> server
>> > > works properly only on EAP6.x and WildFly.
>> > >
>> > > Because of that, I am wondering about removing the -as7 module (see
>> [3]),
>> > > on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for
>> EAP
>> > > usage reasons.
>> > >
>> > > What do you guys think?
>> > >
>> > > -Matthias
>> > >
>> > > [1]
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
>> > > [2] https://issues.jboss.org/browse/AS7-4694
>> > > [3]
>> > >
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
>> > >
>> > >
>> > > --
>> > > Matthias Wessendorf
>> > >
>> > > blog: http://matthiaswessendorf.wordpress.com/
>> > > sessions: http://www.slideshare.net/mwessendorf
>> > > twitter: http://twitter.com/mwessendorf
>> > >
>> >
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20141022/b54a324e/attachment-0001.html 

From matzew at apache.org  Wed Oct 22 05:06:50 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 11:06:50 +0200
Subject: [aerogear-dev] [UPS] A thought: On MASTER only support WildFly?
In-Reply-To: <1413967257.6296.29.camel@kpiwko-x220>
References: <CAAg5f2Q555Pi6dWQDP_-xc=Zc9wAsvZLRJDeabNdbD2g+J6asA@mail.gmail.com>
	<1413967257.6296.29.camel@kpiwko-x220>
Message-ID: <CAAg5f2TzHSyEqWp6unzmQxrAJ0Bb-67ZFVXG2nhk9WzBWbg_CA@mail.gmail.com>

Hi Karel!

On Wed, Oct 22, 2014 at 10:40 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> On Wed, 2014-10-22 at 08:43 +0200, Matthias Wessendorf wrote:
> > Hello,
> >
> > as said in the other email thread earlier this week ([1]) there is a bug
> in
> > the last JBoss AS 7.1 release (see [2]), that basically means the server
> > works properly only on EAP6.x and WildFly.
> >
> > Because of that, I am wondering about removing the -as7 module (see [3]),
> > on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
> > usage reasons.
>
> Sounds reasonable to me if there is an easy way how to backport from -wf
> in 1.1.x (or 2.0.x) to -as7 in 1.0.x in case there is issue that
> potentially affect both wars.


Overall idea here is to get MASTER (currently labled as '1.1.x') rely on
latest greatest, including JDK8 (see other email)
However, for our 1.0.x branch there will be a few more releases that are
also targeting EAP 6.x, until the end of the year + maybe a few fixes early
next year



> Which should be pretty easy looking at
> architecture of UPS ;-).
>

IMO main diff. is really the actual KC adapter, since they hook into two
completely different web-servers.

-Matthias


> >
> > What do you guys think?
> >
> > -Matthias
> >
> > [1]
> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > [2] https://issues.jboss.org/browse/AS7-4694
> > [3]
> >
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141022/55a4e18a/attachment.html 

From kpiwko at redhat.com  Wed Oct 22 06:21:05 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 22 Oct 2014 12:21:05 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
Message-ID: <1413973265.6296.35.camel@kpiwko-x220>

Just a clarification, you mean making it *also* Java8 compatible, not
exclusively Java8, right?

On Wed, 2014-10-22 at 10:35 +0200, Matthias Wessendorf wrote:
> On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:
> 
> > If master is WF only, that should work.
> >
> 
> yes, see original email :-)
> 
> 
> >
> > If you guys keep EAP there, you'd need to target 1.6 and also not to use
> > 1.8 for the runtime, see https://access.redhat.com/articles/111663 for
> > EAP supported configurations.
> >
> > Karel
> >
> > On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
> > > While at it :), as a follow-up thought on that, I am wondering if, on
> > > MASTER, we should look into making it Java8?
> > >
> > > -Matthias
> > >
> > > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <matzew at apache.org>
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > as said in the other email thread earlier this week ([1]) there is a
> > bug
> > > > in the last JBoss AS 7.1 release (see [2]), that basically means the
> > server
> > > > works properly only on EAP6.x and WildFly.
> > > >
> > > > Because of that, I am wondering about removing the -as7 module (see
> > [3]),
> > > > on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for
> > EAP
> > > > usage reasons.
> > > >
> > > > What do you guys think?
> > > >
> > > > -Matthias
> > > >
> > > > [1]
> > http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > > > [2] https://issues.jboss.org/browse/AS7-4694
> > > > [3]
> > > >
> > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.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 Oct 22 06:38:31 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 12:38:31 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <1413973265.6296.35.camel@kpiwko-x220>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
	<1413973265.6296.35.camel@kpiwko-x220>
Message-ID: <CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>

long term, on master, exclusively jsk8

On Wednesday, October 22, 2014, Karel Piwko <kpiwko at redhat.com> wrote:

> Just a clarification, you mean making it *also* Java8 compatible, not
> exclusively Java8, right?
>
> On Wed, 2014-10-22 at 10:35 +0200, Matthias Wessendorf wrote:
> > On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com
> <javascript:;>> wrote:
> >
> > > If master is WF only, that should work.
> > >
> >
> > yes, see original email :-)
> >
> >
> > >
> > > If you guys keep EAP there, you'd need to target 1.6 and also not to
> use
> > > 1.8 for the runtime, see https://access.redhat.com/articles/111663 for
> > > EAP supported configurations.
> > >
> > > Karel
> > >
> > > On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
> > > > While at it :), as a follow-up thought on that, I am wondering if, on
> > > > MASTER, we should look into making it Java8?
> > > >
> > > > -Matthias
> > > >
> > > > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <
> matzew at apache.org <javascript:;>>
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > as said in the other email thread earlier this week ([1]) there is
> a
> > > bug
> > > > > in the last JBoss AS 7.1 release (see [2]), that basically means
> the
> > > server
> > > > > works properly only on EAP6.x and WildFly.
> > > > >
> > > > > Because of that, I am wondering about removing the -as7 module (see
> > > [3]),
> > > > > on our MASTER branch. For the 1.0.x branch, I'd like to keep it,
> for
> > > EAP
> > > > > usage reasons.
> > > > >
> > > > > What do you guys think?
> > > > >
> > > > > -Matthias
> > > > >
> > > > > [1]
> > > http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > > > > [2] https://issues.jboss.org/browse/AS7-4694
> > > > > [3]
> > > > >
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://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
> > >
> >
> >
> >
> > _______________________________________________
> > 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/20141022/a5ff20c8/attachment.html 

From scm.blanc at gmail.com  Wed Oct 22 06:48:17 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 22 Oct 2014 12:48:17 +0200
Subject: [aerogear-dev] notification alert and app launched displays the
	alert
In-Reply-To: <1413948865382-9554.post@n5.nabble.com>
References: <1413948865382-9554.post@n5.nabble.com>
Message-ID: <CAD_dpu1m-YUd6q=sn1BkE+yJQPXnXY5SwkD=7E2mhmijoiWL9Q@mail.gmail.com>

Hi !
Thanks for trying out the UnifiedPush  Server.
See my answers inline

On Wed, Oct 22, 2014 at 5:34 AM, chansdad <rajnukala at yahoo.com> wrote:

> Hello
>
> I am testing aerogear for a project of mine . Able to send alerts .
>
> Here are couple of questions
> 1. Can I send alerts based on a deviceId?
>
No, but you can send alerts based on an "alias". You can pass an "alias"
when you registers your device.

> 2. alerts is visible in the notifications panel in android . when i select
> the alert , it takes me to the app . and when the app is active displays
> the
> alert dialog on top of the app . can i disable this? when the app is not
> active , alert is not displayed on the app screen.
> 3. Can i customize the alert as it displays on the screen.
> 4. Does aerogear support rich media notifications to be displayed on
> homescreen. If not is there a plan to add this feature?
>
I will let our Android experts answer these questions :)

>
> Thanks and to be honest , aerogear makes it super simple to send out
> notifications .I still need to figure out if i can  send messages by
> deviceId as that is my key requirement.
>

Thx, and regarding deviceId, does the trick with "alias" fix your
requirement ?


>
> Regards
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/notification-alert-and-app-launched-displays-the-alert-tp9554.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/20141022/c2ac108f/attachment.html 

From scm.blanc at gmail.com  Wed Oct 22 06:53:04 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 22 Oct 2014 12:53:04 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
Message-ID: <CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>

Hi !
Since the UPS has its PR now [1], any comment on my question here below ?
TLDR : Do we want to keep the same builder API (and just change the json
send to UPS) ?

Sebi

[1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/411

On Fri, Oct 10, 2014 at 9:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Here a first question :
> Do we want to change also how the Java Sender construct its message ?
> Now we have a "plain" builder pattern, do we want now
> message.criteria.alias("fdfd") ?
> I'm not sure
> Sebi
>
>
> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Hi,
>>
>> Since the API Version PR  [1] has been merged we can start the work on
>> AGPUSH-534 to change the format of the Push message. There has been some
>> discussions on this thread and this gist
>> https://gist.github.com/sebastienblanc/8897596
>> Just want to be sure everyone is okay or have remarks before starting
>> implementing this.
>>
>> Questions ?
>>
>> Sebi
>>
>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
>> [2] https://issues.jboss.org/browse/AGPUSH-534
>>
>> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>> here is the current format for comparison
>>>>>
>>>>> https://gist.github.com/lholmquist/8915817
>>>>>
>>>>> +1 to being more structured.
>>>>>
>>>>> one thing though,  in the current format, simplePush is not part of
>>>>> the message, but it's own thing
>>>>>
>>>> Yeah, that's why I put it in the config section in my first version but
>>>> Matzew suggested it was more part of the message payload
>>>>
>>>
>>>
>>> Nope to config; should stay its own, does not (IMO) make sense to
>>> include in tve message for richer platforms like Android/iOS
>>>
>>>
>>>>
>>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>> I was looking at our current Push Message Format[1] and I was wonderimg
>>>> if you should not add some more structure to it, decoupling config,
>>>> criterias and the message itself :
>>>>
>>>>
>>>> {
>>>>   "config" : {
>>>>
>>>>      "ttl" : 3600,
>>>>      "content-available" : true,
>>>>
>>>>
>>>>
>>>>
>>>>      "simple-push": "version=123"
>>>>
>>>>   },
>>>>   "criteria" : {
>>>>
>>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>>
>>>>
>>>>
>>>>
>>>>       "categories" : ["someCategory", "otherCategory"],
>>>>
>>>>
>>>>
>>>>
>>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>>
>>>>
>>>>
>>>>
>>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>>
>>>>
>>>>
>>>>
>>>>   }
>>>>   ,
>>>>   "message": {
>>>>     "alert":"HELLO!",
>>>>     "sound":"default",
>>>>     "badge":7,
>>>>
>>>>     "someKey":"some value",
>>>>
>>>>     "anotherCustomKey":"some other value"
>>>>
>>>>   },
>>>>   }
>>>>
>>>> wdyt ?
>>>>
>>>>
>>>> interesting idea - it looks better structured.
>>>>
>>>> Re
>>>>
>>>>
>>>>
>>>
>>> --
>>> 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/20141022/cae6340c/attachment-0001.html 

From daniel at passos.me  Wed Oct 22 06:56:59 2014
From: daniel at passos.me (Daniel Passos)
Date: Wed, 22 Oct 2014 08:56:59 -0200
Subject: [aerogear-dev] notification alert and app launched displays the
	alert
In-Reply-To: <1413948865382-9554.post@n5.nabble.com>
References: <1413948865382-9554.post@n5.nabble.com>
Message-ID: <CAKjsGbu+wqJonu_UHnQJFG_dU+dmO8=pzBLrNLj0KvZyL2RAKA@mail.gmail.com>

Hello,

Answers inline

On Wed, Oct 22, 2014 at 1:34 AM, chansdad <rajnukala at yahoo.com> wrote:

> Hello
>
> I am testing aerogear for a project of mine . Able to send alerts .
>
> Here are couple of questions
> 1. Can I send alerts based on a deviceId?
>

Yes and No. You can add an alias from this device on registration and send
a message to this alias.


> 2. alerts is visible in the notifications panel in android . when i select
> the alert , it takes me to the app . and when the app is active displays
> the
> alert dialog on top of the app . can i disable this? when the app is not
> active , alert is not displayed on the app screen.
> 3. Can i customize the alert as it displays on the screen.
> 4. Does aerogear support rich media notifications to be displayed on
> homescreen. If not is there a plan to add this feature?
>

So, talking about android land, is not an AeroGear responsibility display
the message received from UPS.

AeroGear provides a BroadcastReceiver[1] implementation. That automatically
handles/parse/whatever and dispatch it to one (or more) MessageHandler[2],

You (I mean developer) need create and declare MessageHandler. You can
declare a MessageHandler directly in AndroidManifest[3] or do it
programatically[4][5]

Your MessageHander is responsable by display the message (or do something
in background) using the best way to this

Hope this help you

[1]
https://github.com/aerogear/aerogear-android-push/blob/master/src/org/jboss/aerogear/android/unifiedpush/AeroGearGCMMessageReceiver.java
[2]
https://github.com/aerogear/aerogear-android-push/blob/master/src/org/jboss/aerogear/android/unifiedpush/MessageHandler.java
[3] <meta-data android:name="DEFAULT_MESSAGE_HANDLER_KEY"
android:value="[YOUR MessageHandler IMPLEMENTATION CLASS HERE]" />
[4]
https://github.com/aerogear/aerogear-push-helloworld/blob/master/android/src/org/jboss/aerogear/unifiedpush/helloworld/activities/MessagesActivity.java#L52-L59
[5]
https://github.com/aerogear/aerogear-push-helloworld/blob/master/android/src/org/jboss/aerogear/unifiedpush/helloworld/activities/MessagesActivity.java#L67-L72


> Thanks and to be honest , aerogear makes it super simple to send out
> notifications .I still need to figure out if i can  send messages by
> deviceId as that is my key requirement.
>

Glad to know that and thanks for trying out the UPS


> Regards
>

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

From matzew at apache.org  Wed Oct 22 06:58:25 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 12:58:25 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
	<1413973265.6296.35.camel@kpiwko-x220>
	<CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
Message-ID: <CAAg5f2R71HfTiKOyXddh1mWMocUF80if4Ep4OSWmid-Z4Mpdog@mail.gmail.com>

On Wed, Oct 22, 2014 at 12:38 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> long term, on master, exclusively jsk8


but :-) initial steps would be to make it also Java8 compatible. Once that
is there, we will see how to move on.
I think in the past qmx has expressed interested in looking at JDK8, as he
already looked into the doclet issue a bit

-M


>
>
> On Wednesday, October 22, 2014, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Just a clarification, you mean making it *also* Java8 compatible, not
>> exclusively Java8, right?
>>
>> On Wed, 2014-10-22 at 10:35 +0200, Matthias Wessendorf wrote:
>> > On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com>
>> wrote:
>> >
>> > > If master is WF only, that should work.
>> > >
>> >
>> > yes, see original email :-)
>> >
>> >
>> > >
>> > > If you guys keep EAP there, you'd need to target 1.6 and also not to
>> use
>> > > 1.8 for the runtime, see https://access.redhat.com/articles/111663
>> for
>> > > EAP supported configurations.
>> > >
>> > > Karel
>> > >
>> > > On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
>> > > > While at it :), as a follow-up thought on that, I am wondering if,
>> on
>> > > > MASTER, we should look into making it Java8?
>> > > >
>> > > > -Matthias
>> > > >
>> > > > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <
>> matzew at apache.org>
>> > > > wrote:
>> > > >
>> > > > > Hello,
>> > > > >
>> > > > > as said in the other email thread earlier this week ([1]) there
>> is a
>> > > bug
>> > > > > in the last JBoss AS 7.1 release (see [2]), that basically means
>> the
>> > > server
>> > > > > works properly only on EAP6.x and WildFly.
>> > > > >
>> > > > > Because of that, I am wondering about removing the -as7 module
>> (see
>> > > [3]),
>> > > > > on our MASTER branch. For the 1.0.x branch, I'd like to keep it,
>> for
>> > > EAP
>> > > > > usage reasons.
>> > > > >
>> > > > > What do you guys think?
>> > > > >
>> > > > > -Matthias
>> > > > >
>> > > > > [1]
>> > >
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
>> > > > > [2] https://issues.jboss.org/browse/AS7-4694
>> > > > > [3]
>> > > > >
>> > >
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Matthias Wessendorf
>> > > > >
>> > > > > blog: http://matthiaswessendorf.wordpress.com/
>> > > > > sessions: http://www.slideshare.net/mwessendorf
>> > > > > twitter: http://twitter.com/mwessendorf
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > _______________________________________________
>> > > > aerogear-dev mailing list
>> > > > aerogear-dev at lists.jboss.org
>> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> > >
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> >
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.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/20141022/bb007946/attachment.html 

From kpiwko at redhat.com  Wed Oct 22 07:05:04 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 22 Oct 2014 13:05:04 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <CAAg5f2R71HfTiKOyXddh1mWMocUF80if4Ep4OSWmid-Z4Mpdog@mail.gmail.com>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
	<1413973265.6296.35.camel@kpiwko-x220>
	<CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
	<CAAg5f2R71HfTiKOyXddh1mWMocUF80if4Ep4OSWmid-Z4Mpdog@mail.gmail.com>
Message-ID: <1413975904.6296.41.camel@kpiwko-x220>

On Wed, 2014-10-22 at 12:58 +0200, Matthias Wessendorf wrote:
> On Wed, Oct 22, 2014 at 12:38 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
> 
> > long term, on master, exclusively jsk8
> 
> 
> but :-) initial steps would be to make it also Java8 compatible. Once that
> is there, we will see how to move on.
> I think in the past qmx has expressed interested in looking at JDK8, as he
> already looked into the doclet issue a bit

Agree with initial steps. As for exclusively jdk8 - it would make more
sense to keep jdk7 if still supported by WF to me. So, if WF drops JDK7,
it's probably the right time to drop it as well in UPS but I don't see
any reason why to artificially limit users in runtime options. 

> 
> -M
> 
> 
> >
> >
> > On Wednesday, October 22, 2014, Karel Piwko <kpiwko at redhat.com> wrote:
> >
> >> Just a clarification, you mean making it *also* Java8 compatible, not
> >> exclusively Java8, right?
> >>
> >> On Wed, 2014-10-22 at 10:35 +0200, Matthias Wessendorf wrote:
> >> > On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com>
> >> wrote:
> >> >
> >> > > If master is WF only, that should work.
> >> > >
> >> >
> >> > yes, see original email :-)
> >> >
> >> >
> >> > >
> >> > > If you guys keep EAP there, you'd need to target 1.6 and also not to
> >> use
> >> > > 1.8 for the runtime, see https://access.redhat.com/articles/111663
> >> for
> >> > > EAP supported configurations.
> >> > >
> >> > > Karel
> >> > >
> >> > > On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
> >> > > > While at it :), as a follow-up thought on that, I am wondering if,
> >> on
> >> > > > MASTER, we should look into making it Java8?
> >> > > >
> >> > > > -Matthias
> >> > > >
> >> > > > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <
> >> matzew at apache.org>
> >> > > > wrote:
> >> > > >
> >> > > > > Hello,
> >> > > > >
> >> > > > > as said in the other email thread earlier this week ([1]) there
> >> is a
> >> > > bug
> >> > > > > in the last JBoss AS 7.1 release (see [2]), that basically means
> >> the
> >> > > server
> >> > > > > works properly only on EAP6.x and WildFly.
> >> > > > >
> >> > > > > Because of that, I am wondering about removing the -as7 module
> >> (see
> >> > > [3]),
> >> > > > > on our MASTER branch. For the 1.0.x branch, I'd like to keep it,
> >> for
> >> > > EAP
> >> > > > > usage reasons.
> >> > > > >
> >> > > > > What do you guys think?
> >> > > > >
> >> > > > > -Matthias
> >> > > > >
> >> > > > > [1]
> >> > >
> >> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> >> > > > > [2] https://issues.jboss.org/browse/AS7-4694
> >> > > > > [3]
> >> > > > >
> >> > >
> >> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Matthias Wessendorf
> >> > > > >
> >> > > > > blog: http://matthiaswessendorf.wordpress.com/
> >> > > > > sessions: http://www.slideshare.net/mwessendorf
> >> > > > > twitter: http://twitter.com/mwessendorf
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > _______________________________________________
> >> > > > aerogear-dev mailing list
> >> > > > aerogear-dev at lists.jboss.org
> >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> > >
> >> > >
> >> > > _______________________________________________
> >> > > aerogear-dev mailing list
> >> > > aerogear-dev at lists.jboss.org
> >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> > >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > aerogear-dev mailing list
> >> > aerogear-dev at lists.jboss.org
> >> > https://lists.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
> >
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From matzew at apache.org  Wed Oct 22 07:14:47 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 13:14:47 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <1413975904.6296.41.camel@kpiwko-x220>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
	<1413973265.6296.35.camel@kpiwko-x220>
	<CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
	<CAAg5f2R71HfTiKOyXddh1mWMocUF80if4Ep4OSWmid-Z4Mpdog@mail.gmail.com>
	<1413975904.6296.41.camel@kpiwko-x220>
Message-ID: <CAAg5f2Tmk=7G4MnO9Y3WsYjhJsZgU5MqZcLSjrhT8Ux5+Xme0A@mail.gmail.com>

On Wed, Oct 22, 2014 at 1:05 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> On Wed, 2014-10-22 at 12:58 +0200, Matthias Wessendorf wrote:
> > On Wed, Oct 22, 2014 at 12:38 PM, Matthias Wessendorf <matzew at apache.org
> >
> > wrote:
> >
> > > long term, on master, exclusively jsk8
> >
> >
> > but :-) initial steps would be to make it also Java8 compatible. Once
> that
> > is there, we will see how to move on.
> > I think in the past qmx has expressed interested in looking at JDK8, as
> he
> > already looked into the doclet issue a bit
>
> Agree with initial steps. As for exclusively jdk8 - it would make more
> sense to keep jdk7 if still supported by WF to me. So, if WF drops JDK7,
> it's probably the right time to drop it as well in UPS but I don't see
> any reason why to artificially limit users in runtime options.
>

yeah, let's see after the initial steps :)
there are some benefits in coding against Java8 ;-)


>
> >
> > -M
> >
> >
> > >
> > >
> > > On Wednesday, October 22, 2014, Karel Piwko <kpiwko at redhat.com> wrote:
> > >
> > >> Just a clarification, you mean making it *also* Java8 compatible, not
> > >> exclusively Java8, right?
> > >>
> > >> On Wed, 2014-10-22 at 10:35 +0200, Matthias Wessendorf wrote:
> > >> > On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko at redhat.com>
> > >> wrote:
> > >> >
> > >> > > If master is WF only, that should work.
> > >> > >
> > >> >
> > >> > yes, see original email :-)
> > >> >
> > >> >
> > >> > >
> > >> > > If you guys keep EAP there, you'd need to target 1.6 and also not
> to
> > >> use
> > >> > > 1.8 for the runtime, see
> https://access.redhat.com/articles/111663
> > >> for
> > >> > > EAP supported configurations.
> > >> > >
> > >> > > Karel
> > >> > >
> > >> > > On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
> > >> > > > While at it :), as a follow-up thought on that, I am wondering
> if,
> > >> on
> > >> > > > MASTER, we should look into making it Java8?
> > >> > > >
> > >> > > > -Matthias
> > >> > > >
> > >> > > > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <
> > >> matzew at apache.org>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Hello,
> > >> > > > >
> > >> > > > > as said in the other email thread earlier this week ([1])
> there
> > >> is a
> > >> > > bug
> > >> > > > > in the last JBoss AS 7.1 release (see [2]), that basically
> means
> > >> the
> > >> > > server
> > >> > > > > works properly only on EAP6.x and WildFly.
> > >> > > > >
> > >> > > > > Because of that, I am wondering about removing the -as7 module
> > >> (see
> > >> > > [3]),
> > >> > > > > on our MASTER branch. For the 1.0.x branch, I'd like to keep
> it,
> > >> for
> > >> > > EAP
> > >> > > > > usage reasons.
> > >> > > > >
> > >> > > > > What do you guys think?
> > >> > > > >
> > >> > > > > -Matthias
> > >> > > > >
> > >> > > > > [1]
> > >> > >
> > >>
> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > >> > > > > [2] https://issues.jboss.org/browse/AS7-4694
> > >> > > > > [3]
> > >> > > > >
> > >> > >
> > >>
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> > >> > > > >
> > >> > > > >
> > >> > > > > --
> > >> > > > > Matthias Wessendorf
> > >> > > > >
> > >> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > >> > > > > sessions: http://www.slideshare.net/mwessendorf
> > >> > > > > twitter: http://twitter.com/mwessendorf
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > _______________________________________________
> > >> > > > aerogear-dev mailing list
> > >> > > > aerogear-dev at lists.jboss.org
> > >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > >
> > >> > >
> > >> > > _______________________________________________
> > >> > > aerogear-dev mailing list
> > >> > > aerogear-dev at lists.jboss.org
> > >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > _______________________________________________
> > >> > aerogear-dev mailing list
> > >> > aerogear-dev at lists.jboss.org
> > >> > https://lists.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
> > >
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141022/1e7c32ce/attachment-0001.html 

From matzew at apache.org  Wed Oct 22 07:20:14 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 13:20:14 +0200
Subject: [aerogear-dev] notification alert and app launched displays the
	alert
In-Reply-To: <CAKjsGbu+wqJonu_UHnQJFG_dU+dmO8=pzBLrNLj0KvZyL2RAKA@mail.gmail.com>
References: <1413948865382-9554.post@n5.nabble.com>
	<CAKjsGbu+wqJonu_UHnQJFG_dU+dmO8=pzBLrNLj0KvZyL2RAKA@mail.gmail.com>
Message-ID: <CAAg5f2QXMMjs7Bq6gwAtHuGhU4yJ4Wv1uZQSm5X8DAczSTpN6Q@mail.gmail.com>

On Wed, Oct 22, 2014 at 12:56 PM, Daniel Passos <daniel at passos.me> wrote:

> Hello,
>
> Answers inline
>
> On Wed, Oct 22, 2014 at 1:34 AM, chansdad <rajnukala at yahoo.com> wrote:
>
>> Hello
>>
>> I am testing aerogear for a project of mine . Able to send alerts .
>>
>> Here are couple of questions
>> 1. Can I send alerts based on a deviceId?
>>
>
> Yes and No. You can add an alias from this device on registration and send
> a message to this alias.
>

Right! and, as a little 'work-around', you cold store the registrationID on
the alias value -  That way you can send to a specific device, leveraging
the 'alias' feature ;-)


>
>
>> 2. alerts is visible in the notifications panel in android . when i select
>> the alert , it takes me to the app . and when the app is active displays
>> the
>> alert dialog on top of the app . can i disable this? when the app is not
>> active , alert is not displayed on the app screen.
>> 3. Can i customize the alert as it displays on the screen.
>> 4. Does aerogear support rich media notifications to be displayed on
>> homescreen. If not is there a plan to add this feature?
>>
>
you mean, posting HTML5 and stuff? basically, as passos said, the content
is really up to your use-case.



>
> So, talking about android land, is not an AeroGear responsibility display
> the message received from UPS.
>
> AeroGear provides a BroadcastReceiver[1] implementation. That
> automatically handles/parse/whatever and dispatch it to one (or more)
> MessageHandler[2],
>
> You (I mean developer) need create and declare MessageHandler. You can
> declare a MessageHandler directly in AndroidManifest[3] or do it
> programatically[4][5]
>
> Your MessageHander is responsable by display the message (or do something
> in background) using the best way to this
>
> Hope this help you
>
> [1]
> https://github.com/aerogear/aerogear-android-push/blob/master/src/org/jboss/aerogear/android/unifiedpush/AeroGearGCMMessageReceiver.java
> [2]
> https://github.com/aerogear/aerogear-android-push/blob/master/src/org/jboss/aerogear/android/unifiedpush/MessageHandler.java
> [3] <meta-data android:name="DEFAULT_MESSAGE_HANDLER_KEY"
> android:value="[YOUR MessageHandler IMPLEMENTATION CLASS HERE]" />
> [4]
> https://github.com/aerogear/aerogear-push-helloworld/blob/master/android/src/org/jboss/aerogear/unifiedpush/helloworld/activities/MessagesActivity.java#L52-L59
> [5]
> https://github.com/aerogear/aerogear-push-helloworld/blob/master/android/src/org/jboss/aerogear/unifiedpush/helloworld/activities/MessagesActivity.java#L67-L72
>
>
>> Thanks and to be honest , aerogear makes it super simple to send out
>> notifications .I still need to figure out if i can  send messages by
>> deviceId as that is my key requirement.
>>
>
> Glad to know that and thanks for trying out the UPS
>

+1 yeah, gald to hear you like it so far :)


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



-- 
Matthias Wessendorf

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

From matzew at apache.org  Wed Oct 22 07:31:15 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 13:31:15 +0200
Subject: [aerogear-dev] General Android Updates
In-Reply-To: <54450592.8050602@redhat.com>
References: <54450592.8050602@redhat.com>
Message-ID: <CAAg5f2T=0zYTNwhrggadoaGxsrA1O3sQv-n4j_e0DgKQskak_Q@mail.gmail.com>

Great stuff!

thanks for the update!

On Mon, Oct 20, 2014 at 2:52 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
> Last week was a big week.
>
> * Merged last PR from out "Alpha" list
> * Android L released
> * Maven Android Plugin 4.0-rc.1 migration begun
>   * Deprecates apklib
>   * Introduces new project layout
> * Travis builds on  multiple JDKs now.
>
> We continued work on sync and started work on Shoot and Share.  This led
> to the discovery of some issues with the module system and Gradle. The
> aar builds produced by our current build system don't handle
> dependencies correctly. This problem doesn't seem to exist in the
> 4.0-rc.1 plugin.  Also the 4.0 project structure is compatible with the
> Gradle project structure which *SHOULD* make interacting with Android
> Studio better.
>
> This week we are tackling several big issues/tasks at once.
>
> * Updating all of the Travis builds to use multi-JDK
> * Updating all of the projects to MAP 4.0-rc.1
> * Updating all of the projects to API level 21.
>
>
> --
> 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/20141022/5094128d/attachment.html 

From qmx at qmx.me  Wed Oct 22 08:03:04 2014
From: qmx at qmx.me (Douglas Campos)
Date: Wed, 22 Oct 2014 10:03:04 -0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
	<1413973265.6296.35.camel@kpiwko-x220>
	<CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
Message-ID: <20141022120304.GH71845@darkstar.local>

On Wed, Oct 22, 2014 at 12:38:31PM +0200, Matthias Wessendorf wrote:
> long term, on master, exclusively jsk8
-1

There are no clear advantages for us on this, which effectively would
mean just putting a virtual restriction for our users.

making it work on jdk8 on the other hand is a high-value task, in my
roadmap :)

-- 
qmx

From matzew at apache.org  Wed Oct 22 08:09:09 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 14:09:09 +0200
Subject: [aerogear-dev] Java8 on master? (was: Re: [UPS] A thought: On
 MASTER only support WildFly?)
In-Reply-To: <20141022120304.GH71845@darkstar.local>
References: <CAAg5f2RKPoFtPnX3P7PMqDnMTdn5MMfhSpR1O5QVKW8-kCQfNw@mail.gmail.com>
	<1413966832.6296.27.camel@kpiwko-x220>
	<CAAg5f2QYDkEgJ_gMNXG6N5vJjuUdUL_scVZVUON-kTTk+3ZS3A@mail.gmail.com>
	<1413973265.6296.35.camel@kpiwko-x220>
	<CAAg5f2R5cg=HPn6qvHs+ANr-3dJrYzQ+=T4aPca2gHWNxjbZoQ@mail.gmail.com>
	<20141022120304.GH71845@darkstar.local>
Message-ID: <CAAg5f2RCrrzePf3hP-TnZy6wk18azjvpDc77mpvmAW7=uWaARQ@mail.gmail.com>

On Wed, Oct 22, 2014 at 2:03 PM, Douglas Campos <qmx at qmx.me> wrote:

> On Wed, Oct 22, 2014 at 12:38:31PM +0200, Matthias Wessendorf wrote:
> > long term, on master, exclusively jsk8
> -1
>
> There are no clear advantages for us on this, which effectively would
> mean just putting a virtual restriction for our users.
>

fair -> enough();


>
> making it work on jdk8 on the other hand is a high-value task, in my
> roadmap :)
>

cool! Ok, looks like we are getting started :)

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



-- 
Matthias Wessendorf

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

From matzew at apache.org  Wed Oct 22 08:26:07 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 14:26:07 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
	<CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>
Message-ID: <CAAg5f2TU0O1g3F843+Xe_+L8gcuZY+bQ1cvjTq76M3PEiQsqSQ@mail.gmail.com>

On Wed, Oct 22, 2014 at 12:53 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hi !
> Since the UPS has its PR now [1], any comment on my question here below ?
> TLDR : Do we want to keep the same builder API (and just change the json
> send to UPS) ?
>

oh, you mean the JAva-Sender API? Hrm.... I think, we can (or should?)
update it. makes sense to have a sender 1.1.x, on master :) while keeping
the "old" on 1.0.x branch


>
> Sebi
>
> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/411
>
> On Fri, Oct 10, 2014 at 9:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Here a first question :
>> Do we want to change also how the Java Sender construct its message ?
>> Now we have a "plain" builder pattern, do we want now
>> message.criteria.alias("fdfd") ?
>> I'm not sure
>> Sebi
>>
>>
>> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Since the API Version PR  [1] has been merged we can start the work on
>>> AGPUSH-534 to change the format of the Push message. There has been some
>>> discussions on this thread and this gist
>>> https://gist.github.com/sebastienblanc/8897596
>>> Just want to be sure everyone is okay or have remarks before starting
>>> implementing this.
>>>
>>> Questions ?
>>>
>>> Sebi
>>>
>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
>>> [2] https://issues.jboss.org/browse/AGPUSH-534
>>>
>>> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <lholmqui at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> here is the current format for comparison
>>>>>>
>>>>>> https://gist.github.com/lholmquist/8915817
>>>>>>
>>>>>> +1 to being more structured.
>>>>>>
>>>>>> one thing though,  in the current format, simplePush is not part of
>>>>>> the message, but it's own thing
>>>>>>
>>>>> Yeah, that's why I put it in the config section in my first version
>>>>> but Matzew suggested it was more part of the message payload
>>>>>
>>>>
>>>>
>>>> Nope to config; should stay its own, does not (IMO) make sense to
>>>> include in tve message for richer platforms like Android/iOS
>>>>
>>>>
>>>>>
>>>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <matzew at apache.org
>>>>> > wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>> I was looking at our current Push Message Format[1] and I was
>>>>> wonderimg if you should not add some more structure to it, decoupling
>>>>> config, criterias and the message itself :
>>>>>
>>>>>
>>>>> {
>>>>>   "config" : {
>>>>>
>>>>>      "ttl" : 3600,
>>>>>      "content-available" : true,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>      "simple-push": "version=123"
>>>>>
>>>>>   },
>>>>>   "criteria" : {
>>>>>
>>>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>       "categories" : ["someCategory", "otherCategory"],
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   }
>>>>>   ,
>>>>>   "message": {
>>>>>     "alert":"HELLO!",
>>>>>     "sound":"default",
>>>>>     "badge":7,
>>>>>
>>>>>     "someKey":"some value",
>>>>>
>>>>>     "anotherCustomKey":"some other value"
>>>>>
>>>>>   },
>>>>>   }
>>>>>
>>>>> wdyt ?
>>>>>
>>>>>
>>>>> interesting idea - it looks better structured.
>>>>>
>>>>> Re
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Wed Oct 22 08:28:18 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 22 Oct 2014 14:28:18 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAAg5f2TU0O1g3F843+Xe_+L8gcuZY+bQ1cvjTq76M3PEiQsqSQ@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
	<CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>
	<CAAg5f2TU0O1g3F843+Xe_+L8gcuZY+bQ1cvjTq76M3PEiQsqSQ@mail.gmail.com>
Message-ID: <CAD_dpu1rk6vUv8GwQfNP0XRthr5PKYf_6E0TLdfM7_RANG_qAw@mail.gmail.com>

Ok, so we should expose a more "rich" builder API ?


On Wed, Oct 22, 2014 at 2:26 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Oct 22, 2014 at 12:53 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Hi !
>> Since the UPS has its PR now [1], any comment on my question here below ?
>> TLDR : Do we want to keep the same builder API (and just change the json
>> send to UPS) ?
>>
>
> oh, you mean the JAva-Sender API? Hrm.... I think, we can (or should?)
> update it. makes sense to have a sender 1.1.x, on master :) while keeping
> the "old" on 1.0.x branch
>
>
>>
>> Sebi
>>
>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/411
>>
>> On Fri, Oct 10, 2014 at 9:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Here a first question :
>>> Do we want to change also how the Java Sender construct its message ?
>>> Now we have a "plain" builder pattern, do we want now
>>> message.criteria.alias("fdfd") ?
>>> I'm not sure
>>> Sebi
>>>
>>>
>>> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Since the API Version PR  [1] has been merged we can start the work on
>>>> AGPUSH-534 to change the format of the Push message. There has been some
>>>> discussions on this thread and this gist
>>>> https://gist.github.com/sebastienblanc/8897596
>>>> Just want to be sure everyone is okay or have remarks before starting
>>>> implementing this.
>>>>
>>>> Questions ?
>>>>
>>>> Sebi
>>>>
>>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
>>>> [2] https://issues.jboss.org/browse/AGPUSH-534
>>>>
>>>> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>>
>>>>>
>>>>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <lholmqui at redhat.com
>>>>>> > wrote:
>>>>>>
>>>>>>> here is the current format for comparison
>>>>>>>
>>>>>>> https://gist.github.com/lholmquist/8915817
>>>>>>>
>>>>>>> +1 to being more structured.
>>>>>>>
>>>>>>> one thing though,  in the current format, simplePush is not part of
>>>>>>> the message, but it's own thing
>>>>>>>
>>>>>> Yeah, that's why I put it in the config section in my first version
>>>>>> but Matzew suggested it was more part of the message payload
>>>>>>
>>>>>
>>>>>
>>>>> Nope to config; should stay its own, does not (IMO) make sense to
>>>>> include in tve message for richer platforms like Android/iOS
>>>>>
>>>>>
>>>>>>
>>>>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <scm.blanc at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I was looking at our current Push Message Format[1] and I was
>>>>>> wonderimg if you should not add some more structure to it, decoupling
>>>>>> config, criterias and the message itself :
>>>>>>
>>>>>>
>>>>>> {
>>>>>>   "config" : {
>>>>>>
>>>>>>      "ttl" : 3600,
>>>>>>      "content-available" : true,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>      "simple-push": "version=123"
>>>>>>
>>>>>>   },
>>>>>>   "criteria" : {
>>>>>>
>>>>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>       "categories" : ["someCategory", "otherCategory"],
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>   }
>>>>>>   ,
>>>>>>   "message": {
>>>>>>     "alert":"HELLO!",
>>>>>>     "sound":"default",
>>>>>>     "badge":7,
>>>>>>
>>>>>>     "someKey":"some value",
>>>>>>
>>>>>>     "anotherCustomKey":"some other value"
>>>>>>
>>>>>>   },
>>>>>>   }
>>>>>>
>>>>>> wdyt ?
>>>>>>
>>>>>>
>>>>>> interesting idea - it looks better structured.
>>>>>>
>>>>>> Re
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141022/430ea0b0/attachment.html 

From matzew at apache.org  Wed Oct 22 08:31:26 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 22 Oct 2014 14:31:26 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAD_dpu1rk6vUv8GwQfNP0XRthr5PKYf_6E0TLdfM7_RANG_qAw@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
	<CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>
	<CAAg5f2TU0O1g3F843+Xe_+L8gcuZY+bQ1cvjTq76M3PEiQsqSQ@mail.gmail.com>
	<CAD_dpu1rk6vUv8GwQfNP0XRthr5PKYf_6E0TLdfM7_RANG_qAw@mail.gmail.com>
Message-ID: <CAAg5f2Rrd_6QdCVEoFWdORtvnehnUtzboyV55+SB6K8UYqWhLw@mail.gmail.com>

On Wed, Oct 22, 2014 at 2:28 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Ok, so we should expose a more "rich" builder API ?
>

yeah, perhaps - I have no concrete feeling on the API at the moment.
I think it would be nice to revisit the Java-Sender for the 1.1.x UPS
version.

If something better comes out -> nice();



>
>
> On Wed, Oct 22, 2014 at 2:26 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Wed, Oct 22, 2014 at 12:53 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Hi !
>>> Since the UPS has its PR now [1], any comment on my question here below
>>> ? TLDR : Do we want to keep the same builder API (and just change the json
>>> send to UPS) ?
>>>
>>
>> oh, you mean the JAva-Sender API? Hrm.... I think, we can (or should?)
>> update it. makes sense to have a sender 1.1.x, on master :) while keeping
>> the "old" on 1.0.x branch
>>
>>
>>>
>>> Sebi
>>>
>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/411
>>>
>>> On Fri, Oct 10, 2014 at 9:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> Here a first question :
>>>> Do we want to change also how the Java Sender construct its message ?
>>>> Now we have a "plain" builder pattern, do we want now
>>>> message.criteria.alias("fdfd") ?
>>>> I'm not sure
>>>> Sebi
>>>>
>>>>
>>>> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Since the API Version PR  [1] has been merged we can start the work on
>>>>> AGPUSH-534 to change the format of the Push message. There has been some
>>>>> discussions on this thread and this gist
>>>>> https://gist.github.com/sebastienblanc/8897596
>>>>> Just want to be sure everyone is okay or have remarks before starting
>>>>> implementing this.
>>>>>
>>>>> Questions ?
>>>>>
>>>>> Sebi
>>>>>
>>>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
>>>>> [2] https://issues.jboss.org/browse/AGPUSH-534
>>>>>
>>>>> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <
>>>>>>> lholmqui at redhat.com> wrote:
>>>>>>>
>>>>>>>> here is the current format for comparison
>>>>>>>>
>>>>>>>> https://gist.github.com/lholmquist/8915817
>>>>>>>>
>>>>>>>> +1 to being more structured.
>>>>>>>>
>>>>>>>> one thing though,  in the current format, simplePush is not part of
>>>>>>>> the message, but it's own thing
>>>>>>>>
>>>>>>> Yeah, that's why I put it in the config section in my first version
>>>>>>> but Matzew suggested it was more part of the message payload
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Nope to config; should stay its own, does not (IMO) make sense to
>>>>>> include in tve message for richer platforms like Android/iOS
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <
>>>>>>> matzew at apache.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <
>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>> I was looking at our current Push Message Format[1] and I was
>>>>>>> wonderimg if you should not add some more structure to it, decoupling
>>>>>>> config, criterias and the message itself :
>>>>>>>
>>>>>>>
>>>>>>> {
>>>>>>>   "config" : {
>>>>>>>
>>>>>>>      "ttl" : 3600,
>>>>>>>      "content-available" : true,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>      "simple-push": "version=123"
>>>>>>>
>>>>>>>   },
>>>>>>>   "criteria" : {
>>>>>>>
>>>>>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>       "categories" : ["someCategory", "otherCategory"],
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>   }
>>>>>>>   ,
>>>>>>>   "message": {
>>>>>>>     "alert":"HELLO!",
>>>>>>>     "sound":"default",
>>>>>>>     "badge":7,
>>>>>>>
>>>>>>>     "someKey":"some value",
>>>>>>>
>>>>>>>     "anotherCustomKey":"some other value"
>>>>>>>
>>>>>>>   },
>>>>>>>   }
>>>>>>>
>>>>>>> wdyt ?
>>>>>>>
>>>>>>>
>>>>>>> interesting idea - it looks better structured.
>>>>>>>
>>>>>>> Re
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From scm.blanc at gmail.com  Wed Oct 22 08:38:09 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 22 Oct 2014 14:38:09 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAAg5f2Rrd_6QdCVEoFWdORtvnehnUtzboyV55+SB6K8UYqWhLw@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
	<CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>
	<CAAg5f2TU0O1g3F843+Xe_+L8gcuZY+bQ1cvjTq76M3PEiQsqSQ@mail.gmail.com>
	<CAD_dpu1rk6vUv8GwQfNP0XRthr5PKYf_6E0TLdfM7_RANG_qAw@mail.gmail.com>
	<CAAg5f2Rrd_6QdCVEoFWdORtvnehnUtzboyV55+SB6K8UYqWhLw@mail.gmail.com>
Message-ID: <CAD_dpu1W=b41uwU438tk8HRF8DDHcd9Ev38Y8ya-AMXO54QO6w@mail.gmail.com>

Ok let me propose an approach on a PR and then we can discuss that.


On Wed, Oct 22, 2014 at 2:31 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Oct 22, 2014 at 2:28 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Ok, so we should expose a more "rich" builder API ?
>>
>
> yeah, perhaps - I have no concrete feeling on the API at the moment.
> I think it would be nice to revisit the Java-Sender for the 1.1.x UPS
> version.
>
> If something better comes out -> nice();
>
>
>
>>
>>
>> On Wed, Oct 22, 2014 at 2:26 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Wed, Oct 22, 2014 at 12:53 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> Hi !
>>>> Since the UPS has its PR now [1], any comment on my question here below
>>>> ? TLDR : Do we want to keep the same builder API (and just change the json
>>>> send to UPS) ?
>>>>
>>>
>>> oh, you mean the JAva-Sender API? Hrm.... I think, we can (or should?)
>>> update it. makes sense to have a sender 1.1.x, on master :) while keeping
>>> the "old" on 1.0.x branch
>>>
>>>
>>>>
>>>> Sebi
>>>>
>>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/411
>>>>
>>>> On Fri, Oct 10, 2014 at 9:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> Here a first question :
>>>>> Do we want to change also how the Java Sender construct its message ?
>>>>> Now we have a "plain" builder pattern, do we want now
>>>>> message.criteria.alias("fdfd") ?
>>>>> I'm not sure
>>>>> Sebi
>>>>>
>>>>>
>>>>> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Since the API Version PR  [1] has been merged we can start the work
>>>>>> on AGPUSH-534 to change the format of the Push message. There has been some
>>>>>> discussions on this thread and this gist
>>>>>> https://gist.github.com/sebastienblanc/8897596
>>>>>> Just want to be sure everyone is okay or have remarks before starting
>>>>>> implementing this.
>>>>>>
>>>>>> Questions ?
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
>>>>>> [2] https://issues.jboss.org/browse/AGPUSH-534
>>>>>>
>>>>>> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <
>>>>>>>> lholmqui at redhat.com> wrote:
>>>>>>>>
>>>>>>>>> here is the current format for comparison
>>>>>>>>>
>>>>>>>>> https://gist.github.com/lholmquist/8915817
>>>>>>>>>
>>>>>>>>> +1 to being more structured.
>>>>>>>>>
>>>>>>>>> one thing though,  in the current format, simplePush is not part
>>>>>>>>> of the message, but it's own thing
>>>>>>>>>
>>>>>>>> Yeah, that's why I put it in the config section in my first version
>>>>>>>> but Matzew suggested it was more part of the message payload
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Nope to config; should stay its own, does not (IMO) make sense to
>>>>>>> include in tve message for richer platforms like Android/iOS
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <
>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <
>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>> I was looking at our current Push Message Format[1] and I was
>>>>>>>> wonderimg if you should not add some more structure to it, decoupling
>>>>>>>> config, criterias and the message itself :
>>>>>>>>
>>>>>>>>
>>>>>>>> {
>>>>>>>>   "config" : {
>>>>>>>>
>>>>>>>>      "ttl" : 3600,
>>>>>>>>      "content-available" : true,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>      "simple-push": "version=123"
>>>>>>>>
>>>>>>>>   },
>>>>>>>>   "criteria" : {
>>>>>>>>
>>>>>>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>       "categories" : ["someCategory", "otherCategory"],
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>   }
>>>>>>>>   ,
>>>>>>>>   "message": {
>>>>>>>>     "alert":"HELLO!",
>>>>>>>>     "sound":"default",
>>>>>>>>     "badge":7,
>>>>>>>>
>>>>>>>>     "someKey":"some value",
>>>>>>>>
>>>>>>>>     "anotherCustomKey":"some other value"
>>>>>>>>
>>>>>>>>   },
>>>>>>>>   }
>>>>>>>>
>>>>>>>> wdyt ?
>>>>>>>>
>>>>>>>>
>>>>>>>> interesting idea - it looks better structured.
>>>>>>>>
>>>>>>>> Re
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141022/9ecc0062/attachment.html 

From kpiwko at redhat.com  Wed Oct 22 12:13:04 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 22 Oct 2014 18:13:04 +0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
	cartridge
Message-ID: <1413994384.6296.51.camel@kpiwko-x220>

Hi All,

I'd like to know your opinion on following changes to UnifiedPush
Server. They are both focused on improving customization process for the
cartridge.

Just in short, current update process now:
1/ Clone official git repository of cartridge
2/ Extract wars and do the modifications or build ones
3/ Package wars
4/ Push cartridge to your own repository
5/ Create cartridge from your own repository

Whereas, I'm proposing:
1/ Create cartridge from official repository
2/ Clone git repository for gear created by Openshift (by default if rhc
is used)
3/ Modify some files there we expose for user modification
4/ Push back to make changes live

What particular configuration elements I'm interested to have
externalized?

1/ Ability to load keycloak.json from external location

=> This allows user to create cartridge and modify it prior the first
access. This allows users to configure it to be consumable by other
services automatically, e.g. they can add developer users, roles, etc.

2/ Externalize GCM/APNs locations
 
=> Now, URLs are hardcoded in GCM/APNs JARs. If they would be loaded
from external location (defaults can still be hardcoded), this allows
user to easily check business logic that queries data in UPS and not
sending any messages. Also allows to put proxy in between UPS and
APNs/GCMs.

Both these will significantly reduce QE overhead. However, I believe
they are valuable for other as well. 

Feedback and tomatoes (I prefer plum ones) are welcomed.

Thanks,

Karel


From rajnukala at yahoo.com  Wed Oct 22 12:47:17 2014
From: rajnukala at yahoo.com (Raj Nukala)
Date: Wed, 22 Oct 2014 09:47:17 -0700
Subject: [aerogear-dev] notification alert and app launched displays
	the	alert
In-Reply-To: <CAAg5f2QXMMjs7Bq6gwAtHuGhU4yJ4Wv1uZQSm5X8DAczSTpN6Q@mail.gmail.com>
References: <1413948865382-9554.post@n5.nabble.com>	<CAKjsGbu+wqJonu_UHnQJFG_dU+dmO8=pzBLrNLj0KvZyL2RAKA@mail.gmail.com>
	<CAAg5f2QXMMjs7Bq6gwAtHuGhU4yJ4Wv1uZQSm5X8DAczSTpN6Q@mail.gmail.com>
Message-ID: <1413996437.80802.YahooMailNeo@web122603.mail.ne1.yahoo.com>

Well , I am using the cordova plugin to send push notifications. Also when i say rich media message notification , I mean a rich message displayed on home screen / lock screen. 

How do i get the alias field to work for deviceId ?
Further more , when the app registers , does aero gear also capture the gps coordinates ?


Regards



On Wednesday, October 22, 2014 7:21 AM, Matthias Wessendorf <matzew at apache.org> wrote:
 






On Wed, Oct 22, 2014 at 12:56 PM, Daniel Passos <daniel at passos.me> wrote:

Hello,
>
>
>Answers inline
>
>
>On Wed, Oct 22, 2014 at 1:34 AM, chansdad <rajnukala at yahoo.com> wrote:
>
>Hello
>>
>>I am testing aerogear for a project of mine . Able to send alerts .
>>
>>Here are couple of questions
>>1. Can I send alerts based on a deviceId?
>>
>
>
>Yes and No. You can add an alias from this device on registration and send a message to this alias.

Right! and, as a little 'work-around', you cold store the registrationID on the alias value -  That way you can send to a specific device, leveraging the 'alias' feature ;-)
 
 
>2. alerts is visible in the notifications panel in android . when i select
>>the alert , it takes me to the app . and when the app is active displays the
>>alert dialog on top of the app . can i disable this? when the app is not
>>active , alert is not displayed on the app screen.
>>3. Can i customize the alert as it displays on the screen.
>>4. Does aerogear support rich media notifications to be displayed on
>>homescreen. If not is there a plan to add this feature?
>>

you mean, posting HTML5 and stuff? basically, as passos said, the content is really up to your use-case.

 

>
>So, talking about android land, is not an AeroGear responsibility display the message received from UPS. 
>
>
>AeroGear provides a BroadcastReceiver[1] implementation. That automatically handles/parse/whatever and dispatch it to one (or more) MessageHandler[2], 
>
>
>You (I mean developer) need create and declare MessageHandler. You can declare a MessageHandler directly in AndroidManifest[3] or do it programatically[4][5]  
>
>
>Your MessageHander is responsable by display the message (or do something in background) using the best way to this
>
>
>
>Hope this help you
>
>
>[1] https://github.com/aerogear/aerogear-android-push/blob/master/src/org/jboss/aerogear/android/unifiedpush/AeroGearGCMMessageReceiver.java
>[2] https://github.com/aerogear/aerogear-android-push/blob/master/src/org/jboss/aerogear/android/unifiedpush/MessageHandler.java
>[3] <meta-data android:name="DEFAULT_MESSAGE_HANDLER_KEY" android:value="[YOUR MessageHandler IMPLEMENTATION CLASS HERE]" />
>
>[4] https://github.com/aerogear/aerogear-push-helloworld/blob/master/android/src/org/jboss/aerogear/unifiedpush/helloworld/activities/MessagesActivity.java#L52-L59
>[5] https://github.com/aerogear/aerogear-push-helloworld/blob/master/android/src/org/jboss/aerogear/unifiedpush/helloworld/activities/MessagesActivity.java#L67-L72
> 
>Thanks and to be honest , aerogear makes it super simple to send out
>>notifications .I still need to figure out if i can  send messages by
>>deviceId as that is my key requirement.
>>
>
>
>Glad to know that and thanks for trying out the UPS

+1 yeah, gald to hear you like it so far :)
 
 
>Regards
>>
>
>
>-- Passos 
>_______________________________________________
>aerogear-dev mailing list
>aerogear-dev at lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/aerogear-dev
>


-- 
Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141022/e53a9e5a/attachment-0001.html 

From matzew at apache.org  Thu Oct 23 04:48:58 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 10:48:58 +0200
Subject: [aerogear-dev] SSLv3: UnifiedPush and Apple Push Notification
	service
Message-ID: <CAAg5f2TmFc=Ge-PZ=eGnMyi4iGoWG3UmymN1+3Fi3Mces76tdQ@mail.gmail.com>

Hi,

here is a push related announcement from Apple, regarding SSLv3 on APNs:
https://developer.apple.com/news/?id=10222014a

As said, it's already active on their "sandbox"/"development" servers.

And yes I am able to send messages to Apple (just tested now against an app
that is DEVELOPMENT only)

However, I had to reboot my server, last Friday, when I was sending a push
to a development application, since I got a

javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: No trusted certificate found

This was nicely present to me in the dashboard of the server :)

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/20141023/e04c9871/attachment.html 

From scm.blanc at gmail.com  Thu Oct 23 05:45:49 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 23 Oct 2014 11:45:49 +0200
Subject: [aerogear-dev] SSLv3: UnifiedPush and Apple Push Notification
	service
In-Reply-To: <CAAg5f2TmFc=Ge-PZ=eGnMyi4iGoWG3UmymN1+3Fi3Mces76tdQ@mail.gmail.com>
References: <CAAg5f2TmFc=Ge-PZ=eGnMyi4iGoWG3UmymN1+3Fi3Mces76tdQ@mail.gmail.com>
Message-ID: <CAD_dpu0BXKDwOWO=g1gpCYZ9ZGkXgjHDMX_RfCobHLFqH0x_5g@mail.gmail.com>

Cool !
The dashboard is also really useful for me when I do some testing .

On Thu, Oct 23, 2014 at 10:48 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> here is a push related announcement from Apple, regarding SSLv3 on APNs:
> https://developer.apple.com/news/?id=10222014a
>
> As said, it's already active on their "sandbox"/"development" servers.
>
> And yes I am able to send messages to Apple (just tested now against an
> app that is DEVELOPMENT only)
>
> However, I had to reboot my server, last Friday, when I was sending a push
> to a development application, since I got a
>
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: No trusted certificate found
>
> This was nicely present to me in the dashboard of the server :)
>
> 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/20141023/7fbec800/attachment.html 

From matzew at apache.org  Thu Oct 23 07:51:57 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 13:51:57 +0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
	cartridge
In-Reply-To: <1413994384.6296.51.camel@kpiwko-x220>
References: <1413994384.6296.51.camel@kpiwko-x220>
Message-ID: <CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>

On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> Hi All,
>
> I'd like to know your opinion on following changes to UnifiedPush
> Server. They are both focused on improving customization process for the
> cartridge.
>
> Just in short, current update process now:
> 1/ Clone official git repository of cartridge
> 2/ Extract wars and do the modifications or build ones
> 3/ Package wars
> 4/ Push cartridge to your own repository
> 5/ Create cartridge from your own repository
>
> Whereas, I'm proposing:
> 1/ Create cartridge from official repository
> 2/ Clone git repository for gear created by Openshift (by default if rhc
> is used)
> 3/ Modify some files there we expose for user modification
> 4/ Push back to make changes live
>
> What particular configuration elements I'm interested to have
> externalized?
>
> 1/ Ability to load keycloak.json from external location
>
> => This allows user to create cartridge and modify it prior the first
> access. This allows users to configure it to be consumable by other
> services automatically, e.g. they can add developer users, roles, etc.
>

hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
have an idea here



>
> 2/ Externalize GCM/APNs locations
>
> => Now, URLs are hardcoded in GCM/APNs JARs.


yes, they are considered stable APIs :)

We are not going to 'externalize' these URLs


> If they would be loaded
> from external location (defaults can still be hardcoded), this allows
> user to easily check business logic that queries data in UPS and not
> sending any messages. Also allows to put proxy in between UPS and
> APNs/GCMs.
>
> Both these will significantly reduce QE overhead. However, I believe
> they are valuable for other as well.
>
> Feedback and tomatoes (I prefer plum ones) are welcomed.
>
> Thanks,
>
> Karel
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 23 07:59:49 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 13:59:49 +0200
Subject: [aerogear-dev] roadmap - OAuth2 work
In-Reply-To: <8D9AC777-6D7C-4EBC-8B9A-3B4BADEC71A9@gmail.com>
References: <CAAg5f2SJf1fUW6H8r2oTsPLwhi7S1QrewugW=71sj0sCLZxc8A@mail.gmail.com>
	<20141016105822.GD93240@abstractj.org>
	<CAAg5f2Tp996+yfALGmC83WhG-C0sxEfoCb75boi8OL0NPknELA@mail.gmail.com>
	<20141016112133.GF93240@abstractj.org>
	<8D9AC777-6D7C-4EBC-8B9A-3B4BADEC71A9@gmail.com>
Message-ID: <CAAg5f2RDnd-E2=qEY5GvKk6iNkv8VbgQ7dFgZ4CTvMdNK_XTrg@mail.gmail.com>

On Thu, Oct 16, 2014 at 1:42 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> On iOS side aerogear-ios-oauth2 (and its dependent aerogear-ios-http) is
> ready.
> @edewit let?s sync next week on iOS plugin.
>

ok;

so, what's the plan regarding moving it out OAuth2 from "otp" here:
http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november

timeframe still OK ?



> ++
> Corinne
> On 16 Oct 2014, at 13:21, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Thank you
> >
> > On 2014-10-16, Matthias Wessendorf wrote:
> >> Perfect!
> >>
> >> just added an epic for OAuth2 on AGCORDOVA and linked it to AGSEC-180
> ([1]).
> >>
> >> [1] https://issues.jboss.org/browse/AGCORDOVA-35
> >>
> >>
> >> On Thu, Oct 16, 2014 at 12:58 PM, Bruno Oliveira <bruno at abstractj.org>
> >> wrote:
> >>
> >>> Hi Matthias, I'm reviewing ALL the bits related to OAuth2 into our
> >>> project, including Cordova, please see
> >>>
> >>>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Security-Meeting-minutes-td9339.html
> >>>
> >>> The Jira for tracking the work is:
> >>> https://issues.jboss.org/browse/AGSEC-180
> >>>
> >>> On 2014-10-16, Matthias Wessendorf wrote:
> >>>> Hello team!
> >>>>
> >>>> While the Android and iOS team working on OAuth2 libraries and demos,
> the
> >>>> next logical victim for a wider OAuth2 support would be our Apache
> >>> Cordova
> >>>> project!
> >>>>
> >>>> I see it's part of our Cordova roadmap ([1]), but I think it should
> not
> >>> be
> >>>> nested underneath OTP. Instead we should have an "AeroGear Cordova
> >>> OAuth2"
> >>>> repo/project, which ships an OAuth2 plugin, leveraging the native
> >>>> Android/iOS libraries. For the demo, to me, it sounds like it would be
> >>> good
> >>>> to have a Shoot-n-Share Cordova app (supporting Facebook, Google and
> >>>> Keycloak) as well.
> >>>>
> >>>> Not sure exactly on the timing for this, but I think once the Android
> and
> >>>> iOS teams agree their libraries are in a solid state*, it would be a
> good
> >>>> time to rethink the roadmap regarding OAuth2 and our Apache Cordova
> >>> project.
> >>>>
> >>>> Any thoughts?
> >>>>
> >>>> -Matthias
> >>>>
> >>>> * The Android team is currently working on an Android version of
> >>>> "Shoot-n-Share" to test the library and finding potential bugs.
> >>>>
> >>>>
> >>>> [1]
> >>>>
> >>>
> http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/#_otp_0_7_0_november
> >>>> [2]
> >>> http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009364.html
> >>>>
> >>>>
> >>>> --
> >>>> Matthias Wessendorf
> >>>>
> >>>> blog: http://matthiaswessendorf.wordpress.com/
> >>>> sessions: http://www.slideshare.net/mwessendorf
> >>>> twitter: http://twitter.com/mwessendorf
> >>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>> --
> >>>
> >>> abstractj
> >>> PGP: 0x84DC9914
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 23 08:06:31 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 14:06:31 +0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
	cartridge
In-Reply-To: <CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
References: <1413994384.6296.51.camel@kpiwko-x220>
	<CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
Message-ID: <CAAg5f2Qj9dGsOwmmEbzPs55gfMGmhrd7agqq_89sQELDCe3jgQ@mail.gmail.com>

On Thu, Oct 23, 2014 at 1:51 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Hi All,
>>
>> I'd like to know your opinion on following changes to UnifiedPush
>> Server. They are both focused on improving customization process for the
>> cartridge.
>>
>> Just in short, current update process now:
>> 1/ Clone official git repository of cartridge
>> 2/ Extract wars and do the modifications or build ones
>> 3/ Package wars
>> 4/ Push cartridge to your own repository
>> 5/ Create cartridge from your own repository
>>
>> Whereas, I'm proposing:
>> 1/ Create cartridge from official repository
>> 2/ Clone git repository for gear created by Openshift (by default if rhc
>> is used)
>> 3/ Modify some files there we expose for user modification
>> 4/ Push back to make changes live
>>
>> What particular configuration elements I'm interested to have
>> externalized?
>>
>> 1/ Ability to load keycloak.json from external location
>>
>> => This allows user to create cartridge and modify it prior the first
>> access. This allows users to configure it to be consumable by other
>> services automatically, e.g. they can add developer users, roles, etc.
>>
>
> hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
> have an idea here
>

we could have our real in a JSON file, so that it is easy/easier to import
it into an existing KC server, to run UPS against that


>
>
>
>>
>> 2/ Externalize GCM/APNs locations
>>
>> => Now, URLs are hardcoded in GCM/APNs JARs.
>
>
> yes, they are considered stable APIs :)
>
> We are not going to 'externalize' these URLs
>
>
>> If they would be loaded
>> from external location (defaults can still be hardcoded), this allows
>> user to easily check business logic that queries data in UPS and not
>> sending any messages. Also allows to put proxy in between UPS and
>> APNs/GCMs.
>>
>> Both these will significantly reduce QE overhead. However, I believe
>> they are valuable for other as well.
>>
>> Feedback and tomatoes (I prefer plum ones) are welcomed.
>>
>> Thanks,
>>
>> Karel
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

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

From edewit at redhat.com  Thu Oct 23 08:27:55 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 23 Oct 2014 14:27:55 +0200
Subject: [aerogear-dev] Cordova Push Plugin Release
Message-ID: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>

Hi,

We are going to release a new version of the cordova push plugin the new version 1.0.2 a new feature is support for external configuration. Now instead of using code you can store the variantId and secrets into a separate json file. With more platforms support coming this will not `pollute` your code anymore. Check out the 1.0.x branch to give it a spin.

Here are the release notes:
Bug
[AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
Feature Request
[AGCORDOVA-34] - externalise Push config
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141023/2eb2aafe/attachment.html 

From scm.blanc at gmail.com  Thu Oct 23 10:07:22 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 23 Oct 2014 16:07:22 +0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
	cartridge
In-Reply-To: <CAAg5f2Qj9dGsOwmmEbzPs55gfMGmhrd7agqq_89sQELDCe3jgQ@mail.gmail.com>
References: <1413994384.6296.51.camel@kpiwko-x220>
	<CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
	<CAAg5f2Qj9dGsOwmmEbzPs55gfMGmhrd7agqq_89sQELDCe3jgQ@mail.gmail.com>
Message-ID: <CAD_dpu1Haqdj38nYsGQ_ftArS3VaoNMMMyDHp5yWL-YisXyUYQ@mail.gmail.com>

If we go for this let's make sure we have default values.
A lot of people might create an OpenShift App just using the online
interface and not clone it locally (and thus not modify the config files)


On Thu, Oct 23, 2014 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Thu, Oct 23, 2014 at 1:51 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:
>>
>>> Hi All,
>>>
>>> I'd like to know your opinion on following changes to UnifiedPush
>>> Server. They are both focused on improving customization process for the
>>> cartridge.
>>>
>>> Just in short, current update process now:
>>> 1/ Clone official git repository of cartridge
>>> 2/ Extract wars and do the modifications or build ones
>>> 3/ Package wars
>>> 4/ Push cartridge to your own repository
>>> 5/ Create cartridge from your own repository
>>>
>>> Whereas, I'm proposing:
>>> 1/ Create cartridge from official repository
>>> 2/ Clone git repository for gear created by Openshift (by default if rhc
>>> is used)
>>> 3/ Modify some files there we expose for user modification
>>> 4/ Push back to make changes live
>>>
>>> What particular configuration elements I'm interested to have
>>> externalized?
>>>
>>> 1/ Ability to load keycloak.json from external location
>>>
>>> => This allows user to create cartridge and modify it prior the first
>>> access. This allows users to configure it to be consumable by other
>>> services automatically, e.g. they can add developer users, roles, etc.
>>>
>>
>> hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
>> have an idea here
>>
>
> we could have our real in a JSON file, so that it is easy/easier to import
> it into an existing KC server, to run UPS against that
>
>
>>
>>
>>
>>>
>>> 2/ Externalize GCM/APNs locations
>>>
>>> => Now, URLs are hardcoded in GCM/APNs JARs.
>>
>>
>> yes, they are considered stable APIs :)
>>
>> We are not going to 'externalize' these URLs
>>
>>
>>> If they would be loaded
>>> from external location (defaults can still be hardcoded), this allows
>>> user to easily check business logic that queries data in UPS and not
>>> sending any messages. Also allows to put proxy in between UPS and
>>> APNs/GCMs.
>>>
>>> Both these will significantly reduce QE overhead. However, I believe
>>> they are valuable for other as well.
>>>
>>> Feedback and tomatoes (I prefer plum ones) are welcomed.
>>>
>>> Thanks,
>>>
>>> Karel
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20141023/290364c5/attachment.html 

From matzew at apache.org  Thu Oct 23 10:11:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 16:11:24 +0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
	cartridge
In-Reply-To: <CAD_dpu1Haqdj38nYsGQ_ftArS3VaoNMMMyDHp5yWL-YisXyUYQ@mail.gmail.com>
References: <1413994384.6296.51.camel@kpiwko-x220>
	<CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
	<CAAg5f2Qj9dGsOwmmEbzPs55gfMGmhrd7agqq_89sQELDCe3jgQ@mail.gmail.com>
	<CAD_dpu1Haqdj38nYsGQ_ftArS3VaoNMMMyDHp5yWL-YisXyUYQ@mail.gmail.com>
Message-ID: <CAAg5f2TKV0VZzQhHpN7bupLwjq1Kndzi15=jLJ7v=LVZq7vG1g@mail.gmail.com>

yes, our cartridge will still function like that

I think what we can do for Karel, is have the realm.json file, for UPS so
he and team can  import it into running keycloak.

Our cartridge will stay as is, at least that's my (current) understanding

On Thu, Oct 23, 2014 at 4:07 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> If we go for this let's make sure we have default values.
> A lot of people might create an OpenShift App just using the online
> interface and not clone it locally (and thus not modify the config files)
>
>
> On Thu, Oct 23, 2014 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Thu, Oct 23, 2014 at 1:51 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I'd like to know your opinion on following changes to UnifiedPush
>>>> Server. They are both focused on improving customization process for the
>>>> cartridge.
>>>>
>>>> Just in short, current update process now:
>>>> 1/ Clone official git repository of cartridge
>>>> 2/ Extract wars and do the modifications or build ones
>>>> 3/ Package wars
>>>> 4/ Push cartridge to your own repository
>>>> 5/ Create cartridge from your own repository
>>>>
>>>> Whereas, I'm proposing:
>>>> 1/ Create cartridge from official repository
>>>> 2/ Clone git repository for gear created by Openshift (by default if rhc
>>>> is used)
>>>> 3/ Modify some files there we expose for user modification
>>>> 4/ Push back to make changes live
>>>>
>>>> What particular configuration elements I'm interested to have
>>>> externalized?
>>>>
>>>> 1/ Ability to load keycloak.json from external location
>>>>
>>>> => This allows user to create cartridge and modify it prior the first
>>>> access. This allows users to configure it to be consumable by other
>>>> services automatically, e.g. they can add developer users, roles, etc.
>>>>
>>>
>>> hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
>>> have an idea here
>>>
>>
>> we could have our real in a JSON file, so that it is easy/easier to
>> import it into an existing KC server, to run UPS against that
>>
>>
>>>
>>>
>>>
>>>>
>>>> 2/ Externalize GCM/APNs locations
>>>>
>>>> => Now, URLs are hardcoded in GCM/APNs JARs.
>>>
>>>
>>> yes, they are considered stable APIs :)
>>>
>>> We are not going to 'externalize' these URLs
>>>
>>>
>>>> If they would be loaded
>>>> from external location (defaults can still be hardcoded), this allows
>>>> user to easily check business logic that queries data in UPS and not
>>>> sending any messages. Also allows to put proxy in between UPS and
>>>> APNs/GCMs.
>>>>
>>>> Both these will significantly reduce QE overhead. However, I believe
>>>> they are valuable for other as well.
>>>>
>>>> Feedback and tomatoes (I prefer plum ones) are welcomed.
>>>>
>>>> Thanks,
>>>>
>>>> Karel
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141023/27199f5c/attachment-0001.html 

From scm.blanc at gmail.com  Thu Oct 23 10:13:42 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 23 Oct 2014 16:13:42 +0200
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>
References: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>
Message-ID: <CAD_dpu1Zu7WWS-=GRAa2_D9xAdiBD0zwij6BkH67Q7vu-sqJ8A@mail.gmail.com>

For the testers a pro tip :
https://github.com/aerogear/aerogear-push-helloworld uses now this external
config so it's the easiest way to test the new plugin release !


On Thu, Oct 23, 2014 at 2:27 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> We are going to release a new version of the cordova push plugin the new
> version 1.0.2 a new feature is support for external configuration. Now
> instead of using code you can store the variantId and secrets into a
> separate json file. With more platforms support coming this will not
> `pollute` your code anymore. Check out the 1.0.x branch to give it a spin.
>
> Here are the release notes:
> Bug
>
>    - [AGCORDOVA-36 <https://issues.jboss.org/browse/AGCORDOVA-36>] - Make
>    Push Plugin work again with Android < 4.4
>
> Feature Request
>
>    - [AGCORDOVA-34 <https://issues.jboss.org/browse/AGCORDOVA-34>] -
>    externalise Push config
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141023/69730a13/attachment.html 

From miguel21op at gmail.com  Thu Oct 23 11:07:11 2014
From: miguel21op at gmail.com (Miguel Lemos)
Date: Thu, 23 Oct 2014 16:07:11 +0100
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <CAD_dpu1Zu7WWS-=GRAa2_D9xAdiBD0zwij6BkH67Q7vu-sqJ8A@mail.gmail.com>
References: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>
	<CAD_dpu1Zu7WWS-=GRAa2_D9xAdiBD0zwij6BkH67Q7vu-sqJ8A@mail.gmail.com>
Message-ID: <CADPUygfW0PgRhRfCjknLcLx32JHLUAEwSja-7dsSFSkdAQVrdA@mail.gmail.com>

Thanks :-)
Em 23/10/2014 15:14, "Sebastien Blanc" <scm.blanc at gmail.com> escreveu:

> For the testers a pro tip :
> https://github.com/aerogear/aerogear-push-helloworld uses now this
> external config so it's the easiest way to test the new plugin release !
>
>
> On Thu, Oct 23, 2014 at 2:27 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> Hi,
>>
>> We are going to release a new version of the cordova push plugin the new
>> version 1.0.2 a new feature is support for external configuration. Now
>> instead of using code you can store the variantId and secrets into a
>> separate json file. With more platforms support coming this will not
>> `pollute` your code anymore. Check out the 1.0.x branch to give it a spin.
>>
>> Here are the release notes:
>> Bug
>>
>>    - [AGCORDOVA-36 <https://issues.jboss.org/browse/AGCORDOVA-36>] -
>>    Make Push Plugin work again with Android < 4.4
>>
>> Feature Request
>>
>>    - [AGCORDOVA-34 <https://issues.jboss.org/browse/AGCORDOVA-34>] -
>>    externalise Push config
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20141023/80e1b0b1/attachment.html 

From matzew at apache.org  Thu Oct 23 11:41:55 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 17:41:55 +0200
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <CAD_dpu1Zu7WWS-=GRAa2_D9xAdiBD0zwij6BkH67Q7vu-sqJ8A@mail.gmail.com>
References: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>
	<CAD_dpu1Zu7WWS-=GRAa2_D9xAdiBD0zwij6BkH67Q7vu-sqJ8A@mail.gmail.com>
Message-ID: <CAAg5f2S-p1a36Z4FaCrvkpOFde2pHVntLKzrbnbGvNs7dH4AGA@mail.gmail.com>

+1 tested the 1.0.x branch of the push-plugin with the 1.0.x branch of the
helloworld (using external configuration)

==> works as expected against my UPS 1.0.1 instance on Openshift

-M

On Thu, Oct 23, 2014 at 4:13 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> For the testers a pro tip :
> https://github.com/aerogear/aerogear-push-helloworld uses now this
> external config so it's the easiest way to test the new plugin release !
>
>
> On Thu, Oct 23, 2014 at 2:27 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> Hi,
>>
>> We are going to release a new version of the cordova push plugin the new
>> version 1.0.2 a new feature is support for external configuration. Now
>> instead of using code you can store the variantId and secrets into a
>> separate json file. With more platforms support coming this will not
>> `pollute` your code anymore. Check out the 1.0.x branch to give it a spin.
>>
>> Here are the release notes:
>> Bug
>>
>>    - [AGCORDOVA-36 <https://issues.jboss.org/browse/AGCORDOVA-36>] -
>>    Make Push Plugin work again with Android < 4.4
>>
>> Feature Request
>>
>>    - [AGCORDOVA-34 <https://issues.jboss.org/browse/AGCORDOVA-34>] -
>>    externalise Push config
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141023/7c5d61c6/attachment.html 

From matzew at apache.org  Thu Oct 23 12:03:51 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 18:03:51 +0200
Subject: [aerogear-dev] [UPS] Proposal to change the Push Message Format
In-Reply-To: <CAD_dpu1W=b41uwU438tk8HRF8DDHcd9Ev38Y8ya-AMXO54QO6w@mail.gmail.com>
References: <CAD_dpu1UmMicopDX9iH5ZKLufFnE3N7A5ZPjVjBQbSUviOm-SQ@mail.gmail.com>
	<CAAg5f2RjUhneG5o1_U3dZ-wWQWKgZj=jp74p_4cyBUn5ABjqcQ@mail.gmail.com>
	<CAD_dpu04jDzSWr-O2n7o=P36k-ti2yZFesk3zWONp8pwObZ6oQ@mail.gmail.com>
	<3AD4DCCE-F0D6-4870-9632-EA3B83720B0A@redhat.com>
	<CAD_dpu3hYW-YJBVXEX3Sk03YyPkGuWRhKHg5HND8UDMOhcoYcA@mail.gmail.com>
	<CAAg5f2RPZGxUkp46NTW-6O6BTsHgC4AxBKL3SCyWMbrG=Cj7=A@mail.gmail.com>
	<CAD_dpu05i7-csPNVAbjnQLpTiY7k-e6CLvPCcieTA5z_H5yOPg@mail.gmail.com>
	<CAD_dpu0cZChhvNjPxTDyDkMR39LaivJ4WHQz80K5k4_7ER8TOw@mail.gmail.com>
	<CAD_dpu3yt75yL9ekyv5TS1Fhxy+JuL1t5qZ4SwQpGb5Ecv=1oA@mail.gmail.com>
	<CAAg5f2TU0O1g3F843+Xe_+L8gcuZY+bQ1cvjTq76M3PEiQsqSQ@mail.gmail.com>
	<CAD_dpu1rk6vUv8GwQfNP0XRthr5PKYf_6E0TLdfM7_RANG_qAw@mail.gmail.com>
	<CAAg5f2Rrd_6QdCVEoFWdORtvnehnUtzboyV55+SB6K8UYqWhLw@mail.gmail.com>
	<CAD_dpu1W=b41uwU438tk8HRF8DDHcd9Ev38Y8ya-AMXO54QO6w@mail.gmail.com>
Message-ID: <CAAg5f2R718Du59eu1DBJru-4R44xb6cDo-qpZXgG9_Rmc-PBWg@mail.gmail.com>

>From looking at the original proposal in this thread:
https://gist.github.com/sebastienblanc/8897596

and the actual PR:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/411

it looks like there is a mismatch. that is fine :)

However, I can't find a thread where the current proposal from the PR has
been discussed;


On Wed, Oct 22, 2014 at 2:38 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Ok let me propose an approach on a PR and then we can discuss that.
>
>
> On Wed, Oct 22, 2014 at 2:31 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Wed, Oct 22, 2014 at 2:28 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Ok, so we should expose a more "rich" builder API ?
>>>
>>
>> yeah, perhaps - I have no concrete feeling on the API at the moment.
>> I think it would be nice to revisit the Java-Sender for the 1.1.x UPS
>> version.
>>
>> If something better comes out -> nice();
>>
>>
>>
>>>
>>>
>>> On Wed, Oct 22, 2014 at 2:26 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Oct 22, 2014 at 12:53 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi !
>>>>> Since the UPS has its PR now [1], any comment on my question here
>>>>> below ? TLDR : Do we want to keep the same builder API (and just change the
>>>>> json send to UPS) ?
>>>>>
>>>>
>>>> oh, you mean the JAva-Sender API? Hrm.... I think, we can (or should?)
>>>> update it. makes sense to have a sender 1.1.x, on master :) while keeping
>>>> the "old" on 1.0.x branch
>>>>
>>>>
>>>>>
>>>>> Sebi
>>>>>
>>>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/411
>>>>>
>>>>> On Fri, Oct 10, 2014 at 9:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Here a first question :
>>>>>> Do we want to change also how the Java Sender construct its message ?
>>>>>> Now we have a "plain" builder pattern, do we want now
>>>>>> message.criteria.alias("fdfd") ?
>>>>>> I'm not sure
>>>>>> Sebi
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 10, 2014 at 9:01 AM, Sebastien Blanc <scm.blanc at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Since the API Version PR  [1] has been merged we can start the work
>>>>>>> on AGPUSH-534 to change the format of the Push message. There has been some
>>>>>>> discussions on this thread and this gist
>>>>>>> https://gist.github.com/sebastienblanc/8897596
>>>>>>> Just want to be sure everyone is okay or have remarks before
>>>>>>> starting implementing this.
>>>>>>>
>>>>>>> Questions ?
>>>>>>>
>>>>>>> Sebi
>>>>>>>
>>>>>>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/394
>>>>>>> [2] https://issues.jboss.org/browse/AGPUSH-534
>>>>>>>
>>>>>>> On Mon, Feb 10, 2014 at 4:46 PM, Matthias Wessendorf <
>>>>>>> matzew at apache.org> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, February 10, 2014, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Feb 10, 2014 at 2:23 PM, Lucas Holmquist <
>>>>>>>>> lholmqui at redhat.com> wrote:
>>>>>>>>>
>>>>>>>>>> here is the current format for comparison
>>>>>>>>>>
>>>>>>>>>> https://gist.github.com/lholmquist/8915817
>>>>>>>>>>
>>>>>>>>>> +1 to being more structured.
>>>>>>>>>>
>>>>>>>>>> one thing though,  in the current format, simplePush is not part
>>>>>>>>>> of the message, but it's own thing
>>>>>>>>>>
>>>>>>>>> Yeah, that's why I put it in the config section in my first
>>>>>>>>> version but Matzew suggested it was more part of the message payload
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Nope to config; should stay its own, does not (IMO) make sense to
>>>>>>>> include in tve message for richer platforms like Android/iOS
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Feb 9, 2014, at 9:06 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Feb 9, 2014 at 2:14 PM, Matthias Wessendorf <
>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Feb 9, 2014 at 12:06 PM, Sebastien Blanc <
>>>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> I was looking at our current Push Message Format[1] and I was
>>>>>>>>> wonderimg if you should not add some more structure to it, decoupling
>>>>>>>>> config, criterias and the message itself :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> {
>>>>>>>>>   "config" : {
>>>>>>>>>
>>>>>>>>>      "ttl" : 3600,
>>>>>>>>>      "content-available" : true,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>      "simple-push": "version=123"
>>>>>>>>>
>>>>>>>>>   },
>>>>>>>>>   "criteria" : {
>>>>>>>>>
>>>>>>>>>       "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>       "categories" : ["someCategory", "otherCategory"],
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>       "deviceType" : ["iPad", "AndroidTablet"],
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>       "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737"]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>   }
>>>>>>>>>   ,
>>>>>>>>>   "message": {
>>>>>>>>>     "alert":"HELLO!",
>>>>>>>>>     "sound":"default",
>>>>>>>>>     "badge":7,
>>>>>>>>>
>>>>>>>>>     "someKey":"some value",
>>>>>>>>>
>>>>>>>>>     "anotherCustomKey":"some other value"
>>>>>>>>>
>>>>>>>>>   },
>>>>>>>>>   }
>>>>>>>>>
>>>>>>>>> wdyt ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> interesting idea - it looks better structured.
>>>>>>>>>
>>>>>>>>> Re
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141023/02ecab9c/attachment-0001.html 

From matzew at apache.org  Thu Oct 23 12:07:26 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 18:07:26 +0200
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
Message-ID: <CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>

found it :-)

On Thu, Aug 21, 2014 at 1:09 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> {
>        "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737" ....],
>        "alias" : ["user at account.com", "someone at aerogear.org", ....],
>        "categories" : ["someCategory", "otherCategory"],
>        "deviceType" : ["iPad", "AndroidTablet"],
>        "ttl" : 3600,
>        "message": {
>          "alert":"HELLO!",
>          "sound":"default",
>          "badge":7,
>          "content-available" : true,
>          "action-category" : "some_category",*         "simple-push": "version=123",*
>          *"data"* : {
>              "someKey":"some value",
>              "anotherCustomKey":"some other value"
>             }
>        }}
>
>
I think I do like 'data' better than 'payload' (from the PR)

-M




>
>
> WDYT?
>
> Cheers,
> Erik Jan
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 23 13:33:21 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 19:33:21 +0200
Subject: [aerogear-dev] OAuth2, OpenID connect and AeroGear
In-Reply-To: <20141009024921.GA70897@abstractj.org>
References: <20141009024921.GA70897@abstractj.org>
Message-ID: <CAAg5f2QZxC_G6pgNPtHTtjHJY4G5t-u9P=Q6+0nC7wiC0HuVvQ@mail.gmail.com>

On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> Today we had a meeting to discuss some of the priorities for security on
> AeroGear[1]. One of the items is OAuth2 support. Currently we have
> several great examples and implementations for GDrive, flows for
> Keycloak and etc.
>
> Although is a bit confuse for developers getting started from scratch.
> I would like to keep our libaries aligned, considering the limitations
> of each technology of course, as well consolidate each flow[2].
>

that is a nice matrix to reflect where our client libraries are!

Thanks! helpful!

-Matthias



>
> Also the team agreed that OpenID connect (with Facebook and Google) should
> be considered a low
> priority at the moment. That said I have some open questions:
>
> - Should we provide separated SDKs for OAuth2? Or let's put everything
> into *-auth and break into modules later?
>
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js. In the end, OAuth2 is just a protocol and
> should support other servers.
>
> - Should we provide examples for OpenID connect? Or abstractions?
>
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
>
>
> [1] -
>
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>
> [3] - https://issues.jboss.org/browse/AGSEC-180
>
> [4] - https://issues.jboss.org/browse/AGSEC-190
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From avibelli at redhat.com  Thu Oct 23 14:44:46 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Thu, 23 Oct 2014 11:44:46 -0700 (PDT)
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>
References: <652FBCB7-BE72-4425-BCEB-9C495AF8F1DB@redhat.com>
Message-ID: <1414089886943-9594.post@n5.nabble.com>

+1 
tested the push-helloworld branch 1.0.x with a downloaded version of
pushplugin branch 1.0.x. 
The external configuration works well, very nice feature.

Once released, I think we should point out the quickstarts README files that
in order to use the external configuration, at least version 1.0.2 of the
plugin is required (I did test the external configuration with an old
version of the plugin and I had JSON parsing errors, as expected)

Thanks!
Andrea


Erik Jan de Wit wrote
> Hi,
> 
> We are going to release a new version of the cordova push plugin the new
> version 1.0.2 a new feature is support for external configuration. Now
> instead of using code you can store the variantId and secrets into a
> separate json file. With more platforms support coming this will not
> `pollute` your code anymore. Check out the 1.0.x branch to give it a spin.
> 
> Here are the release notes:
> Bug
> [AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
> Feature Request
> [AGCORDOVA-34] - externalise Push config
> 
> _______________________________________________
> 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-Cordova-Push-Plugin-Release-tp9585p9594.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From lholmqui at redhat.com  Thu Oct 23 15:09:08 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 23 Oct 2014 15:09:08 -0400
Subject: [aerogear-dev] UPS - change wildfly plugin hostname
Message-ID: <6647BFE8-957B-4A56-BCBA-B5EE42987108@redhat.com>

So JS guy trying to do Java,  i tried to change the default hostname that the wildfly plugin deploys to on the UPS,

so from the UPS_REPO/servers/:  mvn wildfly:deploy -Pwildfly

i thought that i would just have to update this https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45>

and add a <hostname>some_new_ip</hostname>

but it seems that i actually need to update this one instead

https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166>


Is this a bug/feature, or am i totally doing it wrong, 

i thought i could do it from the command line by adding a -Dhostname=blah,  but nada


-Luke

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141023/6a4ec135/attachment.html 

From matzew at apache.org  Thu Oct 23 15:19:48 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 21:19:48 +0200
Subject: [aerogear-dev] UPS - change wildfly plugin hostname
In-Reply-To: <6647BFE8-957B-4A56-BCBA-B5EE42987108@redhat.com>
References: <6647BFE8-957B-4A56-BCBA-B5EE42987108@redhat.com>
Message-ID: <CAAg5f2QAzUZwEDcVoY7WG=Cz3CHZxjeN_uPSdCqnmXT0z9+87w@mail.gmail.com>

-Dwildfly.hostname=blah ?

On Thu, Oct 23, 2014 at 9:09 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

> So JS guy trying to do Java,  i tried to change the default hostname that
> the wildfly plugin deploys to on the UPS,
>
> so from the UPS_REPO/servers/:  mvn wildfly:deploy -Pwildfly
>
> i thought that i would just have to update this
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45
>
> and add a <hostname>some_new_ip</hostname>
>
> but it seems that i actually need to update this one instead
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166
>
>
> Is this a bug/feature, or am i totally doing it wrong,
>
> i thought i could do it from the command line by adding a -Dhostname=blah,
>  but nada
>
>
> -Luke
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 23 15:20:20 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 21:20:20 +0200
Subject: [aerogear-dev] UPS - change wildfly plugin hostname
In-Reply-To: <CAAg5f2QAzUZwEDcVoY7WG=Cz3CHZxjeN_uPSdCqnmXT0z9+87w@mail.gmail.com>
References: <6647BFE8-957B-4A56-BCBA-B5EE42987108@redhat.com>
	<CAAg5f2QAzUZwEDcVoY7WG=Cz3CHZxjeN_uPSdCqnmXT0z9+87w@mail.gmail.com>
Message-ID: <CAAg5f2Q0MpwgNATmvxwnHAuKjzEeE3eMS_9TFQQjAJ41Czg0fA@mail.gmail.com>

Hey Luke,

here is what I just looked at:
https://docs.jboss.org/wildfly/plugins/maven/latest/deploy-mojo.html#hostname



On Thu, Oct 23, 2014 at 9:19 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> -Dwildfly.hostname=blah ?
>
> On Thu, Oct 23, 2014 at 9:09 PM, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
>> So JS guy trying to do Java,  i tried to change the default hostname that
>> the wildfly plugin deploys to on the UPS,
>>
>> so from the UPS_REPO/servers/:  mvn wildfly:deploy -Pwildfly
>>
>> i thought that i would just have to update this
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45
>>
>> and add a <hostname>some_new_ip</hostname>
>>
>> but it seems that i actually need to update this one instead
>>
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166
>>
>>
>> Is this a bug/feature, or am i totally doing it wrong,
>>
>> i thought i could do it from the command line by adding a
>> -Dhostname=blah,  but nada
>>
>>
>> -Luke
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Thu Oct 23 15:34:41 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 23 Oct 2014 15:34:41 -0400
Subject: [aerogear-dev] UPS - change wildfly plugin hostname
In-Reply-To: <CAAg5f2Q0MpwgNATmvxwnHAuKjzEeE3eMS_9TFQQjAJ41Czg0fA@mail.gmail.com>
References: <6647BFE8-957B-4A56-BCBA-B5EE42987108@redhat.com>
	<CAAg5f2QAzUZwEDcVoY7WG=Cz3CHZxjeN_uPSdCqnmXT0z9+87w@mail.gmail.com>
	<CAAg5f2Q0MpwgNATmvxwnHAuKjzEeE3eMS_9TFQQjAJ41Czg0fA@mail.gmail.com>
Message-ID: <FB9F6583-52FA-4DD8-B49C-D042180DBF3C@redhat.com>

Oh, FFS,  it works now,


however,  is what is in master broken.

trying to deploy on a clean wildfly 8.1.0-final

and getting this:

https://gist.github.com/lholmquist/dbc7f35d121903f914ff#file-gistfile1-sh-L341 <https://gist.github.com/lholmquist/dbc7f35d121903f914ff#file-gistfile1-sh-L341>


> On Oct 23, 2014, at 3:20 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> Hey Luke,
> 
> here is what I just looked at:
> https://docs.jboss.org/wildfly/plugins/maven/latest/deploy-mojo.html#hostname <https://docs.jboss.org/wildfly/plugins/maven/latest/deploy-mojo.html#hostname>
> 
> 
> 
> On Thu, Oct 23, 2014 at 9:19 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> -Dwildfly.hostname=blah ? 
> 
> On Thu, Oct 23, 2014 at 9:09 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> So JS guy trying to do Java,  i tried to change the default hostname that the wildfly plugin deploys to on the UPS,
> 
> so from the UPS_REPO/servers/:  mvn wildfly:deploy -Pwildfly
> 
> i thought that i would just have to update this https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45>
> 
> and add a <hostname>some_new_ip</hostname>
> 
> but it seems that i actually need to update this one instead
> 
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166>
> 
> 
> Is this a bug/feature, or am i totally doing it wrong, 
> 
> i thought i could do it from the command line by adding a -Dhostname=blah,  but nada
> 
> 
> -Luke
> 
> 
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141023/e45a1d85/attachment.html 

From matzew at apache.org  Thu Oct 23 15:36:03 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Oct 2014 21:36:03 +0200
Subject: [aerogear-dev] UPS - change wildfly plugin hostname
In-Reply-To: <FB9F6583-52FA-4DD8-B49C-D042180DBF3C@redhat.com>
References: <6647BFE8-957B-4A56-BCBA-B5EE42987108@redhat.com>
	<CAAg5f2QAzUZwEDcVoY7WG=Cz3CHZxjeN_uPSdCqnmXT0z9+87w@mail.gmail.com>
	<CAAg5f2Q0MpwgNATmvxwnHAuKjzEeE3eMS_9TFQQjAJ41Czg0fA@mail.gmail.com>
	<FB9F6583-52FA-4DD8-B49C-D042180DBF3C@redhat.com>
Message-ID: <CAAg5f2QRQ7muBkq4sehdabYszDh0rEmJAXCsynYhgDayJjXgHA@mail.gmail.com>

Luke, yes - the migration is broken;

let me file a PR, now

On Thu, Oct 23, 2014 at 9:34 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

> Oh, FFS,  it works now,
>
>
> however,  is what is in master broken.
>
> trying to deploy on a clean wildfly 8.1.0-final
>
> and getting this:
>
>
> https://gist.github.com/lholmquist/dbc7f35d121903f914ff#file-gistfile1-sh-L341
>
>
> On Oct 23, 2014, at 3:20 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> Hey Luke,
>
> here is what I just looked at:
>
> https://docs.jboss.org/wildfly/plugins/maven/latest/deploy-mojo.html#hostname
>
>
>
> On Thu, Oct 23, 2014 at 9:19 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> -Dwildfly.hostname=blah ?
>>
>> On Thu, Oct 23, 2014 at 9:09 PM, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> So JS guy trying to do Java,  i tried to change the default hostname
>>> that the wildfly plugin deploys to on the UPS,
>>>
>>> so from the UPS_REPO/servers/:  mvn wildfly:deploy -Pwildfly
>>>
>>> i thought that i would just have to update this
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/pom.xml#L45
>>>
>>> and add a <hostname>some_new_ip</hostname>
>>>
>>> but it seems that i actually need to update this one instead
>>>
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L166
>>>
>>>
>>> Is this a bug/feature, or am i totally doing it wrong,
>>>
>>> i thought i could do it from the command line by adding a
>>> -Dhostname=blah,  but nada
>>>
>>>
>>> -Luke
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141023/f63a5b41/attachment.html 

From kpiwko at redhat.com  Fri Oct 24 07:45:46 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 24 Oct 2014 13:45:46 +0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
 cartridge
In-Reply-To: <CAAg5f2TKV0VZzQhHpN7bupLwjq1Kndzi15=jLJ7v=LVZq7vG1g@mail.gmail.com>
References: <1413994384.6296.51.camel@kpiwko-x220>
	<CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
	<CAAg5f2Qj9dGsOwmmEbzPs55gfMGmhrd7agqq_89sQELDCe3jgQ@mail.gmail.com>
	<CAD_dpu1Haqdj38nYsGQ_ftArS3VaoNMMMyDHp5yWL-YisXyUYQ@mail.gmail.com>
	<CAAg5f2TKV0VZzQhHpN7bupLwjq1Kndzi15=jLJ7v=LVZq7vG1g@mail.gmail.com>
Message-ID: <1414151146.6296.71.camel@kpiwko-x220>

Hello,

we had a discussion about technical details yesterday. Thanks Matthias
for surprising us by paying us a visit :-)

ad 1/ web.xml in openshift profile could change location of
keycloak.json and this file can be directly in cartridge, unlocked for
changes. Keycloak already supports loading that file from filesystem:

https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/ups-as7/src/main/resources/openshift/web.xml
https://github.com/keycloak/keycloak/blob/master/integration/as7-eap6/adapter/src/main/java/org/keycloak/adapters/as7/KeycloakAuthenticatorValve.java#L98-L112

I can prepare PR for that and cartridge if you will.

ad 2/ Tadeas has a Poc with deploying LittleProxy [1] as another WAR
deployment in the cartridge and using rhc set-env to set JAVA_EXT_OPTS
to let EAP use that proxy. It works great with GCMs but not yet with
APNs, which uses sockets instead of HTTP/S, these in particular [2]. We
are investigating this, if you have any tips how to proxy SOCKS for Java
with least effort possible, please let us know. Or maybe we could expose
APNS proxy setup somehow in UPS configuration?

https://github.com/notnoop/java-apns/blob/master/src/main/java/com/notnoop/apns/ApnsServiceBuilder.java#L367-L450

Karel

[1] https://github.com/adamfisk/LittleProxy
[2]
https://github.com/notnoop/java-apns/blob/master/src/main/java/com/notnoop/apns/internal/Utilities.java#L60-L70


On Thu, 2014-10-23 at 16:11 +0200, Matthias Wessendorf wrote:
> yes, our cartridge will still function like that
> 
> I think what we can do for Karel, is have the realm.json file, for UPS so
> he and team can  import it into running keycloak.
> 
> Our cartridge will stay as is, at least that's my (current) understanding
> 
> On Thu, Oct 23, 2014 at 4:07 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
> 
> > If we go for this let's make sure we have default values.
> > A lot of people might create an OpenShift App just using the online
> > interface and not clone it locally (and thus not modify the config files)
> >
> >
> > On Thu, Oct 23, 2014 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> >>
> >>
> >> On Thu, Oct 23, 2014 at 1:51 PM, Matthias Wessendorf <matzew at apache.org>
> >> wrote:
> >>
> >>>
> >>>
> >>> On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:
> >>>
> >>>> Hi All,
> >>>>
> >>>> I'd like to know your opinion on following changes to UnifiedPush
> >>>> Server. They are both focused on improving customization process for the
> >>>> cartridge.
> >>>>
> >>>> Just in short, current update process now:
> >>>> 1/ Clone official git repository of cartridge
> >>>> 2/ Extract wars and do the modifications or build ones
> >>>> 3/ Package wars
> >>>> 4/ Push cartridge to your own repository
> >>>> 5/ Create cartridge from your own repository
> >>>>
> >>>> Whereas, I'm proposing:
> >>>> 1/ Create cartridge from official repository
> >>>> 2/ Clone git repository for gear created by Openshift (by default if rhc
> >>>> is used)
> >>>> 3/ Modify some files there we expose for user modification
> >>>> 4/ Push back to make changes live
> >>>>
> >>>> What particular configuration elements I'm interested to have
> >>>> externalized?
> >>>>
> >>>> 1/ Ability to load keycloak.json from external location
> >>>>
> >>>> => This allows user to create cartridge and modify it prior the first
> >>>> access. This allows users to configure it to be consumable by other
> >>>> services automatically, e.g. they can add developer users, roles, etc.
> >>>>
> >>>
> >>> hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
> >>> have an idea here
> >>>
> >>
> >> we could have our real in a JSON file, so that it is easy/easier to
> >> import it into an existing KC server, to run UPS against that
> >>
> >>
> >>>
> >>>
> >>>
> >>>>
> >>>> 2/ Externalize GCM/APNs locations
> >>>>
> >>>> => Now, URLs are hardcoded in GCM/APNs JARs.
> >>>
> >>>
> >>> yes, they are considered stable APIs :)
> >>>
> >>> We are not going to 'externalize' these URLs
> >>>
> >>>
> >>>> If they would be loaded
> >>>> from external location (defaults can still be hardcoded), this allows
> >>>> user to easily check business logic that queries data in UPS and not
> >>>> sending any messages. Also allows to put proxy in between UPS and
> >>>> APNs/GCMs.
> >>>>
> >>>> Both these will significantly reduce QE overhead. However, I believe
> >>>> they are valuable for other as well.
> >>>>
> >>>> Feedback and tomatoes (I prefer plum ones) are welcomed.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Karel
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.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 lholmqui at redhat.com  Fri Oct 24 09:36:44 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 24 Oct 2014 09:36:44 -0400
Subject: [aerogear-dev] Safari Push notifications
Message-ID: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>

Hello,

So i?ve decided to take today and try and add Safari Push notifications into the UPS.  When i tried about a year ago, i was successful, but i had lots of duplicated code since it is very close to the iOS variant.
basically, the only real difference is that Safari notifications use the Production cert only.  The other slight difference is how you send the message to the APNs service

I wondering if now is the time to start changing the variant names,  so iOSVariant would become APNsVariant(or something like that).  

This would also change the endpoint at which we connect from ?ios' to ?apns?  .  Since this is sort of a breaking change, from a curl perspective,  does this need to wait until a Major release?

plus this might make the current db migration stuff that is in progress more complex too

I have no problems keeping it separate, and then in a later release merging things together

wdyt?

-Luke







From matzew at apache.org  Fri Oct 24 10:16:05 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 24 Oct 2014 16:16:05 +0200
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
Message-ID: <CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>

On Fri, Oct 24, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

> Hello,
>
> So i?ve decided to take today and try and add Safari Push notifications
> into the UPS.  When i tried about a year ago, i was successful, but i had
> lots of duplicated code since it is very close to the iOS variant.
> basically, the only real difference is that Safari notifications use the
> Production cert only.  The other slight difference is how you send the
> message to the APNs service
>
> I wondering if now is the time to start changing the variant names,  so
> iOSVariant would become APNsVariant(or something like that).
>

+1


>
> This would also change the endpoint at which we connect from ?ios' to
> ?apns?  .  Since this is sort of a breaking change, from a curl
> perspective,  does this need to wait until a Major release?
>

Let's have it for master (1.1.x series) only.
That said, since there may be a few mire 1.0.x releases, which also may
have effect to the 1.1.x code base (merges), I'd like to wait a bit with
the actual merge of "Safari push" to master.


>
> plus this might make the current db migration stuff that is in progress
> more complex too
>
> I have no problems keeping it separate, and then in a later release
> merging things together
>

ah, yeah - that's the best :) no need to "wait" on the work, let's keep
branch in sync w/ master, and merge in a few weeks... ok ?

-Matthias



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




-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Fri Oct 24 10:18:20 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 24 Oct 2014 10:18:20 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
Message-ID: <9CB4E632-546B-401D-954F-F6672ABAC9C9@redhat.com>


> On Oct 24, 2014, at 10:16 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Fri, Oct 24, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> Hello,
> 
> So i?ve decided to take today and try and add Safari Push notifications into the UPS.  When i tried about a year ago, i was successful, but i had lots of duplicated code since it is very close to the iOS variant.
> basically, the only real difference is that Safari notifications use the Production cert only.  The other slight difference is how you send the message to the APNs service
> 
> I wondering if now is the time to start changing the variant names,  so iOSVariant would become APNsVariant(or something like that).
> 
> +1
>  
> 
> This would also change the endpoint at which we connect from ?ios' to ?apns?  .  Since this is sort of a breaking change, from a curl perspective,  does this need to wait until a Major release?
> 
> Let's have it for master (1.1.x series) only.
> That said, since there may be a few mire 1.0.x releases, which also may have effect to the 1.1.x code base (merges), I'd like to wait a bit with the actual merge of "Safari push" to master.
>  
> 
> plus this might make the current db migration stuff that is in progress more complex too
> 
> I have no problems keeping it separate, and then in a later release merging things together
> 
> ah, yeah - that's the best :) no need to "wait" on the work, let's keep branch in sync w/ master, and merge in a few weeks... ok ?

sounds good

>  
> -Matthias
> 
> 
> 
> wdyt?
> 
> -Luke
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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>
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141024/de8d963e/attachment.html 

From lholmqui at redhat.com  Fri Oct 24 10:19:30 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 24 Oct 2014 10:19:30 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
Message-ID: <FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>


> On Oct 24, 2014, at 10:16 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Fri, Oct 24, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> Hello,
> 
> So i?ve decided to take today and try and add Safari Push notifications into the UPS.  When i tried about a year ago, i was successful, but i had lots of duplicated code since it is very close to the iOS variant.
> basically, the only real difference is that Safari notifications use the Production cert only.  The other slight difference is how you send the message to the APNs service
> 
> I wondering if now is the time to start changing the variant names,  so iOSVariant would become APNsVariant(or something like that).

this would also apply to Android and Chrome since now both use the same GCM,

> 
> +1
>  
> 
> This would also change the endpoint at which we connect from ?ios' to ?apns?  .  Since this is sort of a breaking change, from a curl perspective,  does this need to wait until a Major release?
> 
> Let's have it for master (1.1.x series) only.
> That said, since there may be a few mire 1.0.x releases, which also may have effect to the 1.1.x code base (merges), I'd like to wait a bit with the actual merge of "Safari push" to master.
>  
> 
> plus this might make the current db migration stuff that is in progress more complex too
> 
> I have no problems keeping it separate, and then in a later release merging things together
> 
> ah, yeah - that's the best :) no need to "wait" on the work, let's keep branch in sync w/ master, and merge in a few weeks... ok ?
>  
> -Matthias
> 
> 
> 
> wdyt?
> 
> -Luke
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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>
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141024/a1a136f9/attachment-0001.html 

From matzew at apache.org  Fri Oct 24 10:24:11 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 24 Oct 2014 16:24:11 +0200
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
Message-ID: <CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>

On Friday, October 24, 2014, Lucas Holmquist <lholmqui at redhat.com> wrote:

>
> On Oct 24, 2014, at 10:16 AM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>
>
> On Fri, Oct 24, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com
> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>
>> Hello,
>>
>> So i?ve decided to take today and try and add Safari Push notifications
>> into the UPS.  When i tried about a year ago, i was successful, but i had
>> lots of duplicated code since it is very close to the iOS variant.
>> basically, the only real difference is that Safari notifications use the
>> Production cert only.  The other slight difference is how you send the
>> message to the APNs service
>>
>> I wondering if now is the time to start changing the variant names,  so
>> iOSVariant would become APNsVariant(or something like that).
>>
>
> this would also apply to Android and Chrome since now both use the same
> GCM,
>

ah, right, almost forgot about that change :-)


>
>
> +1
>
>
>>
>> This would also change the endpoint at which we connect from ?ios' to
>> ?apns?  .  Since this is sort of a breaking change, from a curl
>> perspective,  does this need to wait until a Major release?
>>
>
> Let's have it for master (1.1.x series) only.
> That said, since there may be a few mire 1.0.x releases, which also may
> have effect to the 1.1.x code base (merges), I'd like to wait a bit with
> the actual merge of "Safari push" to master.
>
>
>>
>> plus this might make the current db migration stuff that is in progress
>> more complex too
>>
>> I have no problems keeping it separate, and then in a later release
>> merging things together
>>
>
> ah, yeah - that's the best :) no need to "wait" on the work, let's keep
> branch in sync w/ master, and merge in a few weeks... ok ?
>
> -Matthias
>
>
>
>> wdyt?
>>
>> -Luke
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://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:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141024/751c14b3/attachment.html 

From daniel.bevenius at gmail.com  Sun Oct 26 05:14:59 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Sun, 26 Oct 2014 10:14:59 +0100
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3F=1J0rnH2LsevdXjSOWyMkbSUypnd43N_Y51sb2+urOw@mail.gmail.com>

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

From bruno at abstractj.org  Mon Oct 27 02:04:29 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 27 Oct 2014 04:04:29 -0200
Subject: [aerogear-dev] AeroGear Security meeting
Message-ID: <20141027060428.GA72807@abstractj.org>

Good morning, this is the clap for the security meeting on Wednesday
(same time of our official meeting)

http://oksoclap.com/p/Awo2S1V89M

Feel free to update.

--

abstractj
PGP: 0x84DC9914

From scm.blanc at gmail.com  Mon Oct 27 04:59:47 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 27 Oct 2014 09:59:47 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
Message-ID: <CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>

On Thu, Oct 23, 2014 at 6:07 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> found it :-)
>
> On Thu, Aug 21, 2014 at 1:09 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> {
>>        "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737" ....],
>>        "alias" : ["user at account.com", "someone at aerogear.org", ....],
>>        "categories" : ["someCategory", "otherCategory"],
>>        "deviceType" : ["iPad", "AndroidTablet"],
>>        "ttl" : 3600,
>>        "message": {
>>          "alert":"HELLO!",
>>          "sound":"default",
>>          "badge":7,
>>          "content-available" : true,
>>          "action-category" : "some_category",*         "simple-push": "version=123",*
>>          *"data"* : {
>>              "someKey":"some value",
>>              "anotherCustomKey":"some other value"
>>             }
>>        }}
>>
>>
> I think I do like 'data' better than 'payload' (from the PR)
>
Sounds good to me or 'custom-data'


>
> -M
>
>
>
>
>>
>>
>> WDYT?
>>
>> Cheers,
>> Erik Jan
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141027/3ffe78a1/attachment.html 

From lholmqui at redhat.com  Mon Oct 27 09:15:18 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 27 Oct 2014 09:15:18 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
Message-ID: <0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>


So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>

but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 

I?m not sure the syntax for https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>
to add a second thing in.

From the looks of it,  it looks like only one class is supported.

*Disclaimer:  javascript dude doing java*


> On Oct 24, 2014, at 10:24 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Friday, October 24, 2014, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> On Oct 24, 2014, at 10:16 AM, Matthias Wessendorf <matzew at apache.org <>> wrote:
>> 
>> 
>> 
>> On Fri, Oct 24, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com <>> wrote:
>> Hello,
>> 
>> So i?ve decided to take today and try and add Safari Push notifications into the UPS.  When i tried about a year ago, i was successful, but i had lots of duplicated code since it is very close to the iOS variant.
>> basically, the only real difference is that Safari notifications use the Production cert only.  The other slight difference is how you send the message to the APNs service
>> 
>> I wondering if now is the time to start changing the variant names,  so iOSVariant would become APNsVariant(or something like that).
> 
> this would also apply to Android and Chrome since now both use the same GCM,
> 
> ah, right, almost forgot about that change :-)
>  
> 
>> 
>> +1
>>  
>> 
>> This would also change the endpoint at which we connect from ?ios' to ?apns?  .  Since this is sort of a breaking change, from a curl perspective,  does this need to wait until a Major release?
>> 
>> Let's have it for master (1.1.x series) only.
>> That said, since there may be a few mire 1.0.x releases, which also may have effect to the 1.1.x code base (merges), I'd like to wait a bit with the actual merge of "Safari push" to master.
>>  
>> 
>> plus this might make the current db migration stuff that is in progress more complex too
>> 
>> I have no problems keeping it separate, and then in a later release merging things together
>> 
>> ah, yeah - that's the best :) no need to "wait" on the work, let's keep branch in sync w/ master, and merge in a few weeks... ok ?
>>  
>> -Matthias
>> 
>> 
>> 
>> wdyt?
>> 
>> -Luke
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org <>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>_______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org <>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> 
> -- 
> Sent from Gmail Mobile
> _______________________________________________
> 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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141027/96ef5c16/attachment-0001.html 

From edewit at redhat.com  Mon Oct 27 09:20:49 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 27 Oct 2014 14:20:49 +0100
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
Message-ID: <FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>

On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com> wrote:

> 
> So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52
> 
> but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 

Right now a sender is configured to send notifications for one specific variant type, this mapping is configured on the top of the class:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40

so APNsPushNotificationSender will only be use for iOSVariant variants, so either we change the way this works or you create a new Sender ( that extends this one maybe )

Cheers,
	Erik Jan


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

From edewit at redhat.com  Mon Oct 27 09:21:10 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 27 Oct 2014 14:21:10 +0100
Subject: [aerogear-dev] Cordova Push Plugin Release
Message-ID: <71684F92-FC11-4227-A67D-40DDEB0D3C65@redhat.com>

Hi,

After successful testing we are happy to announce that version 1.0.2 of the push plugin has been released. With a new feature support for external configuration, instead of using code you can store the variantId and secrets into a separate json file.

Cheers,
	Erik Jan


Here are the release notes:
Bug
[AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
Feature Request
[AGCORDOVA-34] - externalise Push config

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141027/59a662c9/attachment.html 

From avibelli at redhat.com  Mon Oct 27 09:24:57 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Mon, 27 Oct 2014 06:24:57 -0700 (PDT)
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <71684F92-FC11-4227-A67D-40DDEB0D3C65@redhat.com>
References: <71684F92-FC11-4227-A67D-40DDEB0D3C65@redhat.com>
Message-ID: <1414416297372-9612.post@n5.nabble.com>

Thanks Erik and all the team, 
this is a real nice new feature!

Andrea


Erik Jan de Wit wrote
> Hi,
> 
> After successful testing we are happy to announce that version 1.0.2 of
> the push plugin has been released. With a new feature support for external
> configuration, instead of using code you can store the variantId and
> secrets into a separate json file.
> 
> Cheers,
> 	Erik Jan
> 
> 
> Here are the release notes:
> Bug
> [AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
> Feature Request
> [AGCORDOVA-34] - externalise Push config
> 
> 
> _______________________________________________
> 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-Cordova-Push-Plugin-Release-tp9610p9612.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From daniel.bevenius at gmail.com  Mon Oct 27 09:26:03 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 27 Oct 2014 14:26:03 +0100
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <1414416297372-9612.post@n5.nabble.com>
References: <71684F92-FC11-4227-A67D-40DDEB0D3C65@redhat.com>
	<1414416297372-9612.post@n5.nabble.com>
Message-ID: <CAFJm-3EK1xRGyc1nVdb1vKpq4b=dBJdMExyCNnFyk5hiHsrd5Q@mail.gmail.com>

Nice work guys!

On 27 October 2014 14:24, Andrea Vibelli <avibelli at redhat.com> wrote:

> Thanks Erik and all the team,
> this is a real nice new feature!
>
> Andrea
>
>
> Erik Jan de Wit wrote
> > Hi,
> >
> > After successful testing we are happy to announce that version 1.0.2 of
> > the push plugin has been released. With a new feature support for
> external
> > configuration, instead of using code you can store the variantId and
> > secrets into a separate json file.
> >
> > Cheers,
> >       Erik Jan
> >
> >
> > Here are the release notes:
> > Bug
> > [AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
> > Feature Request
> > [AGCORDOVA-34] - externalise Push config
> >
> >
> > _______________________________________________
> > 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-Cordova-Push-Plugin-Release-tp9610p9612.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/20141027/8658a1e9/attachment.html 

From lholmqui at redhat.com  Mon Oct 27 09:28:02 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 27 Oct 2014 09:28:02 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
Message-ID: <2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>


> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com> wrote:
> 
> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> 
>> So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>
>> 
>> but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 
> 
> Right now a sender is configured to send notifications for one specific variant type, this mapping is configured on the top of the class:
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40>
> 
> so APNsPushNotificationSender will only be use for iOSVariant variants, so either we change the way this works or you create a new Sender ( that extends this one maybe )

I think i?ll just create a new sender of now just to get something working since the SafariVariant and iOSVariant will be combined into an APNsVariant in the near future.



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

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

From lholmqui at redhat.com  Mon Oct 27 09:28:34 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 27 Oct 2014 09:28:34 -0400
Subject: [aerogear-dev] Cordova Push Plugin Release
In-Reply-To: <CAFJm-3EK1xRGyc1nVdb1vKpq4b=dBJdMExyCNnFyk5hiHsrd5Q@mail.gmail.com>
References: <71684F92-FC11-4227-A67D-40DDEB0D3C65@redhat.com>
	<1414416297372-9612.post@n5.nabble.com>
	<CAFJm-3EK1xRGyc1nVdb1vKpq4b=dBJdMExyCNnFyk5hiHsrd5Q@mail.gmail.com>
Message-ID: <83AA71AF-149E-4B97-A1AC-C65DE0BFF8FB@redhat.com>

Good Job

++ for external configs!!!!!1!

> On Oct 27, 2014, at 9:26 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
> 
> Nice work guys!
> 
> On 27 October 2014 14:24, Andrea Vibelli <avibelli at redhat.com <mailto:avibelli at redhat.com>> wrote:
> Thanks Erik and all the team,
> this is a real nice new feature!
> 
> Andrea
> 
> 
> Erik Jan de Wit wrote
> > Hi,
> >
> > After successful testing we are happy to announce that version 1.0.2 of
> > the push plugin has been released. With a new feature support for external
> > configuration, instead of using code you can store the variantId and
> > secrets into a separate json file.
> >
> > Cheers,
> >       Erik Jan
> >
> >
> > Here are the release notes:
> > Bug
> > [AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
> > Feature Request
> > [AGCORDOVA-34] - externalise Push config
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> 
> > aerogear-dev at .jboss
> 
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> 
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Cordova-Push-Plugin-Release-tp9610p9612.html <http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Cordova-Push-Plugin-Release-tp9610p9612.html>
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> 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>
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From matzew at apache.org  Mon Oct 27 09:42:22 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 27 Oct 2014 14:42:22 +0100
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
Message-ID: <CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>

On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

>
> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com> wrote:
>
> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com> wrote:
>
>
> So i?ve run into a bit of a problem, I?m trying to send notifications,
>  using
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52
>
> but i?m not sure how to also tell it to use the new SafarVariant.class
> that i?ve created.
>
>
> Right now a sender is configured to send notifications for one specific
> variant type, this mapping is configured on the top of the class:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40
>
> so APNsPushNotificationSender will only be use for iOSVariant variants,
> so either we change the way this works or you create a new Sender ( that
> extends this one maybe )
>
>
> I think i?ll just create a new sender of now just to get something working
> since the SafariVariant and iOSVariant will be combined into an APNsVariant
> in the near future.
>

sounds reasonable on getting this started

-M

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



-- 
Matthias Wessendorf

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

From cvasilak at gmail.com  Mon Oct 27 10:14:26 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 27 Oct 2014 16:14:26 +0200
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3F=1J0rnH2LsevdXjSOWyMkbSUypnd43N_Y51sb2+urOw@mail.gmail.com>
References: <CAFJm-3F=1J0rnH2LsevdXjSOWyMkbSUypnd43N_Y51sb2+urOw@mail.gmail.com>
Message-ID: <CD0C06E3-3060-4C1B-A38A-64BABB3F2BFA@gmail.com>

fyi,

meeting minutes:

<jbott>	 Meeting ended Mon Oct 27 14:12:38 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-10-27-14.00.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-27-14.00.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-27-14.00.log.html


On Oct 26, 2014, at 11:14 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

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

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

From qmx at qmx.me  Mon Oct 27 10:15:44 2014
From: qmx at qmx.me (Douglas Campos)
Date: Mon, 27 Oct 2014 12:15:44 -0200
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
Message-ID: <20141027141544.GA2256@darkstar.local>

'payload' is the term used for this kind of "in-message custom data"
since the early years of EIP tools (before camel was born)

Any strong reason to avoid it?

Also, as others pointed out, we have json keys with dashes, is this
really desired? because consistency :)


-- 
qmx

From matzew at apache.org  Mon Oct 27 10:19:49 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 27 Oct 2014 15:19:49 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <20141027141544.GA2256@darkstar.local>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
Message-ID: <CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>

On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:

> 'payload' is the term used for this kind of "in-message custom data"
> since the early years of EIP tools (before camel was born)
>

nested payload, inside of message, I am not sure



>
> Any strong reason to avoid it?
>
> Also, as others pointed out, we have json keys with dashes, is this
> really desired? because consistency :)
>

yeah, we have a few, to stay in sync a/ le apple (action-category and
content-available)




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



-- 
Matthias Wessendorf

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

From edewit at redhat.com  Mon Oct 27 10:30:51 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 27 Oct 2014 15:30:51 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
Message-ID: <C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>

> On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
> 'payload' is the term used for this kind of "in-message custom data"
> since the early years of EIP tools (before camel was born)
> 
> nested payload, inside of message, I am not sure
> 

Thinking a bit more about it, I don?t like data (it?s to generic everything is data) and I don?t like payload either (because everything is message payload) can?t we use something like ?customData? , ?userData?, `userKeys` or perhaps something that says a little bit more to what this is.

>  
> 
> Any strong reason to avoid it?

yeah, let?s keep the once that are there because the are consistent with apple
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141027/1ce9c532/attachment.html 

From matzew at apache.org  Mon Oct 27 10:54:56 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 27 Oct 2014 15:54:56 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
Message-ID: <CAAg5f2SFpa7mFaqggHh8tmRpAD-5o4PtHuEV-pYMRgn1Ufr+=Q@mail.gmail.com>

On Mon, Oct 27, 2014 at 3:30 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
>
>> 'payload' is the term used for this kind of "in-message custom data"
>> since the early years of EIP tools (before camel was born)
>>
>
> nested payload, inside of message, I am not sure
>
>
> Thinking a bit more about it, I don?t like data (it?s to generic
> everything is data) and I don?t like payload either (because everything is
> message payload)
>

I hear you! data is pretty generic


> can?t we use something like ?customData? , ?userData?, `userKeys` or
> perhaps something that says a little bit more to what this is.
>

Good suggestions, I do like user-data!

:)



>
>
>
>
>>
>> Any strong reason to avoid it?
>>
>
> yeah, let?s keep the once that are there because the are consistent with
> apple
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141027/40f7b843/attachment-0001.html 

From qmx at qmx.me  Mon Oct 27 12:50:28 2014
From: qmx at qmx.me (Douglas Campos)
Date: Mon, 27 Oct 2014 14:50:28 -0200
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
Message-ID: <20141027165028.GB2256@darkstar.local>

On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
> > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
> > 'payload' is the term used for this kind of "in-message custom data"
> > since the early years of EIP tools (before camel was born)
> > 
> > nested payload, inside of message, I am not sure
> > 
> 
> Thinking a bit more about it, I don?t like data (it?s to generic
> everything is data) and I don?t like payload either (because
> everything is message payload) can?t we use something like
> ?customData? , ?userData?, `userKeys` or perhaps something that says a
> little bit more to what this is.
+1 to userData, clearly communicates intent (if y'all dislike payload) :D

-- 
qmx

From matzew at apache.org  Mon Oct 27 14:36:45 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 27 Oct 2014 19:36:45 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <20141027165028.GB2256@darkstar.local>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
Message-ID: <CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>

On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me> wrote:

> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
> > > 'payload' is the term used for this kind of "in-message custom data"
> > > since the early years of EIP tools (before camel was born)
> > >
> > > nested payload, inside of message, I am not sure
> > >
> >
> > Thinking a bit more about it, I don?t like data (it?s to generic
> > everything is data) and I don?t like payload either (because
> > everything is message payload) can?t we use something like
> > ?customData? , ?userData?, `userKeys` or perhaps something that says a
> > little bit more to what this is.
> +1 to userData, clearly communicates intent (if y'all dislike payload) :D
>

how about user-data  ?
(due to consistency ?) :)




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



-- 
Matthias Wessendorf

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

From bruno at abstractj.org  Mon Oct 27 14:48:00 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 27 Oct 2014 16:48:00 -0200
Subject: [aerogear-dev] Docker images on AeroGear
Message-ID: <20141027184800.GA17333@abstractj.org>

Good morning,

As you may know few months ago we started to work on Docker images, with
the support of Marek Goldmann ? the main responsible for leading the efforts on
Docker (https://github.com/jboss-dockerfiles).

I asked Matthias to create a fork of
https://github.com/jboss-dockerfiles/aerogear, into this way the
team can make our images more mature, before send to the official repository.
Also, my files were moved from my personal repository to AeroGear's fork
(https://github.com/abstractj/docker/blob/master/aerogear/README.md)

The AeroGear organization was created on Docker Hub
https://registry.hub.docker.com/repos/aerogear/ to host our official
images, the build of the images were automated and Marek was added as one of the admins.

The reason for having images like: aerogear/unifiedpush-as7-dev instead of
jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
on Docker Hub.

If you have any questions, go ahead.

--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Mon Oct 27 17:24:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 27 Oct 2014 22:24:24 +0100
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <20141027184800.GA17333@abstractj.org>
References: <20141027184800.GA17333@abstractj.org>
Message-ID: <CAAg5f2QLrBASf_fS+GCm-ewN8MYYg4AZPJ0E73Rtfxb0DSB89Q@mail.gmail.com>

Hi Bruno!

this is great work!

-Matthias



On Mon, Oct 27, 2014 at 7:48 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> As you may know few months ago we started to work on Docker images, with
> the support of Marek Goldmann ? the main responsible for leading the
> efforts on
> Docker (https://github.com/jboss-dockerfiles).
>
> I asked Matthias to create a fork of
> https://github.com/jboss-dockerfiles/aerogear, into this way the
> team can make our images more mature, before send to the official
> repository.
> Also, my files were moved from my personal repository to AeroGear's fork
> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
>
> The AeroGear organization was created on Docker Hub
> https://registry.hub.docker.com/repos/aerogear/ to host our official
> images, the build of the images were automated and Marek was added as one
> of the admins.
>
> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
> on Docker Hub.
>
> If you have any questions, go ahead.
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev




-- 
Matthias Wessendorf

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

From daniel at passos.me  Mon Oct 27 20:30:07 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 27 Oct 2014 22:30:07 -0200
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
	<CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
Message-ID: <CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>

-1 to payload, +1 to user-data || userData

-- Passos

On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me> wrote:
>
>> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
>> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
>> > > 'payload' is the term used for this kind of "in-message custom data"
>> > > since the early years of EIP tools (before camel was born)
>> > >
>> > > nested payload, inside of message, I am not sure
>> > >
>> >
>> > Thinking a bit more about it, I don?t like data (it?s to generic
>> > everything is data) and I don?t like payload either (because
>> > everything is message payload) can?t we use something like
>> > ?customData? , ?userData?, `userKeys` or perhaps something that says a
>> > little bit more to what this is.
>> +1 to userData, clearly communicates intent (if y'all dislike payload) :D
>>
>
> how about user-data  ?
> (due to consistency ?) :)
>
>
>
>
>>
>> --
>> qmx
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141027/6403e6f2/attachment.html 

From daniel.bevenius at gmail.com  Tue Oct 28 02:36:24 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 28 Oct 2014 07:36:24 +0100
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <CAAg5f2QLrBASf_fS+GCm-ewN8MYYg4AZPJ0E73Rtfxb0DSB89Q@mail.gmail.com>
References: <20141027184800.GA17333@abstractj.org>
	<CAAg5f2QLrBASf_fS+GCm-ewN8MYYg4AZPJ0E73Rtfxb0DSB89Q@mail.gmail.com>
Message-ID: <CAFJm-3H84y=DOpQH5e8piWSxA69XiqVQLgLvr91nQep9C18Cyg@mail.gmail.com>

+1 Very nice!

On 27 October 2014 22:24, Matthias Wessendorf <matzew at apache.org> wrote:

> Hi Bruno!
>
> this is great work!
>
> -Matthias
>
>
>
> On Mon, Oct 27, 2014 at 7:48 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> Good morning,
>>
>> As you may know few months ago we started to work on Docker images, with
>> the support of Marek Goldmann ? the main responsible for leading the
>> efforts on
>> Docker (https://github.com/jboss-dockerfiles).
>>
>> I asked Matthias to create a fork of
>> https://github.com/jboss-dockerfiles/aerogear, into this way the
>> team can make our images more mature, before send to the official
>> repository.
>> Also, my files were moved from my personal repository to AeroGear's fork
>> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
>>
>> The AeroGear organization was created on Docker Hub
>> https://registry.hub.docker.com/repos/aerogear/ to host our official
>> images, the build of the images were automated and Marek was added as one
>> of the admins.
>>
>> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
>> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
>> on Docker Hub.
>>
>> If you have any questions, go ahead.
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/3784c2b8/attachment-0001.html 

From cvasilak at gmail.com  Tue Oct 28 03:11:54 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 28 Oct 2014 09:11:54 +0200
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
	<CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
	<CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>
Message-ID: <66956EEB-6CD7-4C26-8863-7214F8B1D594@gmail.com>

+1 for user-data

-
Christos


On Oct 28, 2014, at 2:30 AM, Daniel Passos <daniel at passos.me> wrote:

> -1 to payload, +1 to user-data || userData
> 
> -- Passos
> 
> On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me> wrote:
> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
> > > 'payload' is the term used for this kind of "in-message custom data"
> > > since the early years of EIP tools (before camel was born)
> > >
> > > nested payload, inside of message, I am not sure
> > >
> >
> > Thinking a bit more about it, I don?t like data (it?s to generic
> > everything is data) and I don?t like payload either (because
> > everything is message payload) can?t we use something like
> > ?customData? , ?userData?, `userKeys` or perhaps something that says a
> > little bit more to what this is.
> +1 to userData, clearly communicates intent (if y'all dislike payload) :D
> 
> how about user-data  ? 
> (due to consistency ?) :)
> 
> 
>  
> 
> --
> qmx
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141028/93342684/attachment.html 

From cvasilak at gmail.com  Tue Oct 28 03:15:06 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 28 Oct 2014 09:15:06 +0200
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <20141027184800.GA17333@abstractj.org>
References: <20141027184800.GA17333@abstractj.org>
Message-ID: <9B252034-DCAB-46D7-8329-E12145C73714@gmail.com>

nice work Bruno! 

thanks for the heads-up!

-
Christos

On Oct 27, 2014, at 8:48 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
> 
> As you may know few months ago we started to work on Docker images, with
> the support of Marek Goldmann ? the main responsible for leading the efforts on
> Docker (https://github.com/jboss-dockerfiles).
> 
> I asked Matthias to create a fork of
> https://github.com/jboss-dockerfiles/aerogear, into this way the
> team can make our images more mature, before send to the official repository.
> Also, my files were moved from my personal repository to AeroGear's fork
> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
> 
> The AeroGear organization was created on Docker Hub
> https://registry.hub.docker.com/repos/aerogear/ to host our official
> images, the build of the images were automated and Marek was added as one of the admins.
> 
> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
> on Docker Hub.
> 
> If you have any questions, go ahead.
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From daniel.bevenius at gmail.com  Tue Oct 28 03:17:49 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 28 Oct 2014 08:17:49 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <66956EEB-6CD7-4C26-8863-7214F8B1D594@gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
	<CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
	<CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>
	<66956EEB-6CD7-4C26-8863-7214F8B1D594@gmail.com>
Message-ID: <CAFJm-3HTXNQEqP-3aa0PE=Tom_7mRdy8AdNT4aTmiRx-0k2WzA@mail.gmail.com>

+1 for user-data

On 28 October 2014 08:11, Christos Vasilakis <cvasilak at gmail.com> wrote:

> +1 for user-data
>
> -
> Christos
>
>
> On Oct 28, 2014, at 2:30 AM, Daniel Passos <daniel at passos.me> wrote:
>
> -1 to payload, +1 to user-data || userData
>
> -- Passos
>
> On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me> wrote:
>>
>>> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
>>> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
>>> > > 'payload' is the term used for this kind of "in-message custom data"
>>> > > since the early years of EIP tools (before camel was born)
>>> > >
>>> > > nested payload, inside of message, I am not sure
>>> > >
>>> >
>>> > Thinking a bit more about it, I don?t like data (it?s to generic
>>> > everything is data) and I don?t like payload either (because
>>> > everything is message payload) can?t we use something like
>>> > ?customData? , ?userData?, `userKeys` or perhaps something that says a
>>> > little bit more to what this is.
>>> +1 to userData, clearly communicates intent (if y'all dislike payload) :D
>>>
>>
>> how about user-data  ?
>> (due to consistency ?) :)
>>
>>
>>
>>
>>>
>>> --
>>> qmx
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141028/63114ed0/attachment.html 

From matzew at apache.org  Tue Oct 28 04:20:14 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 09:20:14 +0100
Subject: [aerogear-dev] [site] community page overhaul ?
Message-ID: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>

Hi,

I realized that atm we don't link to our users list, a quick/urgent fix for
that is here:
https://github.com/aerogear/aerogear.org/pull/410

That perhaps not enough! On the 'community' link we basically include the
archive of the dev list.

What should we do with that community section? How about the following

Instead of including the archive (as part of the website), we can tweak the
'community' page a bit.
E.g. we list the different options we have for users to reach out:
 ** links to users/dev ML subscribe page
 ** links to users/dev ML archives
 ** info on IRC
 ** link to our github landing page
 ** info on our twitter account

I think the benefit of including this on a dedicated page, makes the info
also a bit more visible, instead of just having links to ML at the footer
of our website


What are your thoughts?

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/20141028/e610795c/attachment.html 

From edewit at redhat.com  Tue Oct 28 04:26:11 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 28 Oct 2014 09:26:11 +0100
Subject: [aerogear-dev] oath2 cordova plugin
Message-ID: <7654908B-708F-4B22-AB69-5C2AA01A02DE@redhat.com>

Hi,

I was working on a Oath2 plugin for cordova with the latest swift bits, but using swift for a cordova plugin is not very user friendly. The generated project that gets downloaded when you do a `cordova platform add ios` has to be change by opening Xcode.

Things that need to be changed by hand are the following:
	* iOS Deployment target needs to be set to something higher then the 6.0 it?s now at
	* Bridging-Header.h to Objective-c Bridging Header under the Swift Compiler - Code Generation options 
		e.g (HelloCordova/Plugins/org.jboss.aerogear.cordova.oauth2/Bridging-Header.h)
	* the following to LD_RUNPATH_SEARCH_PATHS to "$(inherited) @executable_path/Frameworks?

That is just a little to much for a user to do, and I see no way to hook this into the cordova project / plugin configuration. The cordova team are planning to change the way the project is created and how settings are maintained in version 4.0 I?ve created two PR that help that effort, but these have not been merged yet. 

So I propose that we don?t release the plugin, but wait on cordova to update so that manual steps will no longer be needed, or we add a big Notice on how to install use this plugin.

WDYT?

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

From daniel.bevenius at gmail.com  Tue Oct 28 04:31:11 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 28 Oct 2014 09:31:11 +0100
Subject: [aerogear-dev] [site] community page overhaul ?
In-Reply-To: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>
References: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>
Message-ID: <CAFJm-3HeU=KKppca7zSnGZ3Uz3BG57oBOT_Pkwan55sYLKqoSA@mail.gmail.com>

+1 I like the suggestion

On 28 October 2014 09:20, Matthias Wessendorf <matzew at apache.org> wrote:

> Hi,
>
> I realized that atm we don't link to our users list, a quick/urgent fix
> for that is here:
> https://github.com/aerogear/aerogear.org/pull/410
>
> That perhaps not enough! On the 'community' link we basically include the
> archive of the dev list.
>
> What should we do with that community section? How about the following
>
> Instead of including the archive (as part of the website), we can tweak
> the 'community' page a bit.
> E.g. we list the different options we have for users to reach out:
>  ** links to users/dev ML subscribe page
>  ** links to users/dev ML archives
>  ** info on IRC
>  ** link to our github landing page
>  ** info on our twitter account
>
> I think the benefit of including this on a dedicated page, makes the info
> also a bit more visible, instead of just having links to ML at the footer
> of our website
>
>
> What are your thoughts?
>
> 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/20141028/5dcfdb0a/attachment.html 

From corinnekrych at gmail.com  Tue Oct 28 04:32:57 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 28 Oct 2014 09:32:57 +0100
Subject: [aerogear-dev] [site] community page overhaul ?
In-Reply-To: <CAFJm-3HeU=KKppca7zSnGZ3Uz3BG57oBOT_Pkwan55sYLKqoSA@mail.gmail.com>
References: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>
	<CAFJm-3HeU=KKppca7zSnGZ3Uz3BG57oBOT_Pkwan55sYLKqoSA@mail.gmail.com>
Message-ID: <2F4E5C21-FBC4-45E9-8AA7-A07891FEFA2F@gmail.com>

+1 instead of embedding ag-dev archive a list of usefull links looks better

On 28 Oct 2014, at 09:31, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> +1 I like the suggestion
> 
> On 28 October 2014 09:20, Matthias Wessendorf <matzew at apache.org> wrote:
> Hi,
> 
> I realized that atm we don't link to our users list, a quick/urgent fix for that is here:
> https://github.com/aerogear/aerogear.org/pull/410
> 
> That perhaps not enough! On the 'community' link we basically include the archive of the dev list.
> 
> What should we do with that community section? How about the following
> 
> Instead of including the archive (as part of the website), we can tweak the 'community' page a bit.
> E.g. we list the different options we have for users to reach out:
>  ** links to users/dev ML subscribe page
>  ** links to users/dev ML archives
>  ** info on IRC
>  ** link to our github landing page
>  ** info on our twitter account 
> 
> I think the benefit of including this on a dedicated page, makes the info also a bit more visible, instead of just having links to ML at the footer of our website
> 
> 
> What are your thoughts?
> 
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/3b16a3fc/attachment.bin 

From corinnekrych at gmail.com  Tue Oct 28 04:39:47 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 28 Oct 2014 09:39:47 +0100
Subject: [aerogear-dev] oath2 cordova plugin
In-Reply-To: <7654908B-708F-4B22-AB69-5C2AA01A02DE@redhat.com>
References: <7654908B-708F-4B22-AB69-5C2AA01A02DE@redhat.com>
Message-ID: <9CD4B8D6-2509-4FE7-B458-037736953667@gmail.com>


On 28 Oct 2014, at 09:26, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
> 
> I was working on a Oath2 plugin for cordova with the latest swift bits, but using swift for a cordova plugin is not very user friendly. The generated project that gets downloaded when you do a `cordova platform add ios` has to be change by opening Xcode.
> 
> Things that need to be changed by hand are the following:
> 	* iOS Deployment target needs to be set to something higher then the 6.0 it?s now at

would it help if we label which version  works with 6.0, which one with 6.1?

> 	* Bridging-Header.h to Objective-c Bridging Header under the Swift Compiler - Code Generation options 
> 		e.g (HelloCordova/Plugins/org.jboss.aerogear.cordova.oauth2/Bridging-Header.h)
> 	* the following to LD_RUNPATH_SEARCH_PATHS to "$(inherited) @executable_path/Frameworks?
> 
> That is just a little to much for a user to do, and I see no way to hook this into the cordova project / plugin configuration. The cordova team are planning to change the way the project is created and how settings are maintained in version 4.0 I?ve created two PR that help that effort, but these have not been merged yet. 

I?m following this PR:
https://github.com/apache/cordova-ios/pull/104
what is the other one?

> 
> So I propose that we don?t release the plugin, but wait on cordova to update so that manual steps will no longer be needed, or we add a big Notice on how to install use this plugin.
> 
> WDYT?

what about doing an early adopter release of the plugin with its demo and blog post explaining the current difficulties (which require manual steps) and talk about what?s next in cordova-ios: workspace instead of just project? I can hel with testing and blog post.

where is your current demo? is it this repo:
https://github.com/edewit/aerogear-cordova-cookbook/tree/swift-oauth2-plugin
? 

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/f21001f1/attachment.bin 

From matzew at apache.org  Tue Oct 28 04:46:06 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 09:46:06 +0100
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <20141027184800.GA17333@abstractj.org>
References: <20141027184800.GA17333@abstractj.org>
Message-ID: <CAAg5f2ShJNrYL8fJNU0SBOBNLKYMNQLbSDAFj1VcB19KqBUsbg@mail.gmail.com>

Hrm, at some point it worked for me, on my box :)

but, now I did it again, and I got a timeout:

docker run -it -p 8443:8443 aerogear/unifiedpush-wildfly
2014/10/28 09:44:51 Post http://192.168.59.103:2375/v1.15/containers/create:
dial tcp 192.168.59.103:2375: i/o timeout


docker --version
Docker version 1.3.0, build c78088f



Anyone noticed that too ?




On Mon, Oct 27, 2014 at 7:48 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> As you may know few months ago we started to work on Docker images, with
> the support of Marek Goldmann ? the main responsible for leading the
> efforts on
> Docker (https://github.com/jboss-dockerfiles).
>
> I asked Matthias to create a fork of
> https://github.com/jboss-dockerfiles/aerogear, into this way the
> team can make our images more mature, before send to the official
> repository.
> Also, my files were moved from my personal repository to AeroGear's fork
> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
>
> The AeroGear organization was created on Docker Hub
> https://registry.hub.docker.com/repos/aerogear/ to host our official
> images, the build of the images were automated and Marek was added as one
> of the admins.
>
> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
> on Docker Hub.
>
> If you have any questions, go ahead.
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev




-- 
Matthias Wessendorf

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

From edewit at redhat.com  Tue Oct 28 04:49:27 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 28 Oct 2014 09:49:27 +0100
Subject: [aerogear-dev] oath2 cordova plugin
In-Reply-To: <9CD4B8D6-2509-4FE7-B458-037736953667@gmail.com>
References: <7654908B-708F-4B22-AB69-5C2AA01A02DE@redhat.com>
	<9CD4B8D6-2509-4FE7-B458-037736953667@gmail.com>
Message-ID: <308CFDE6-5E48-4E96-BDC7-C694BAC13328@redhat.com>


On 28 Oct,2014, at 9:39 , Corinne Krych <corinnekrych at gmail.com> wrote:

> 
> would it help if we label which version  works with 6.0, which one with 6.1?

So swift is supported from 7.0 and higher

> I?m following this PR:
> https://github.com/apache/cordova-ios/pull/104
> what is the other one?

That is one the other one it https://github.com/apache/cordova-lib/pull/90


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

From matzew at apache.org  Tue Oct 28 04:50:31 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 09:50:31 +0100
Subject: [aerogear-dev] oath2 cordova plugin
In-Reply-To: <9CD4B8D6-2509-4FE7-B458-037736953667@gmail.com>
References: <7654908B-708F-4B22-AB69-5C2AA01A02DE@redhat.com>
	<9CD4B8D6-2509-4FE7-B458-037736953667@gmail.com>
Message-ID: <CAAg5f2REmN0-J6g9J9i4vgb8SiOiNi6LriTjxwhq6LEPHF128A@mail.gmail.com>

On Tue, Oct 28, 2014 at 9:39 AM, Corinne Krych <corinnekrych at gmail.com>
wrote:

>
> On 28 Oct 2014, at 09:26, Erik Jan de Wit <edewit at redhat.com> wrote:
>
> > Hi,
> >
> > I was working on a Oath2 plugin for cordova with the latest swift bits,
> but using swift for a cordova plugin is not very user friendly. The
> generated project that gets downloaded when you do a `cordova platform add
> ios` has to be change by opening Xcode.
> >
> > Things that need to be changed by hand are the following:
> >       * iOS Deployment target needs to be set to something higher then
> the 6.0 it?s now at
>
> would it help if we label which version  works with 6.0, which one with
> 6.1?
>
> >       * Bridging-Header.h to Objective-c Bridging Header under the Swift
> Compiler - Code Generation options
> >               e.g
> (HelloCordova/Plugins/org.jboss.aerogear.cordova.oauth2/Bridging-Header.h)
> >       * the following to LD_RUNPATH_SEARCH_PATHS to "$(inherited)
> @executable_path/Frameworks?
> >
> > That is just a little to much for a user to do, and I see no way to hook
> this into the cordova project / plugin configuration. The cordova team are
> planning to change the way the project is created and how settings are
> maintained in version 4.0 I?ve created two PR that help that effort, but
> these have not been merged yet.
>

great way of interacting w/ the Apache Cordova folks! Glad seeing our team
is submitting PRs to the core ios project :)



>
> I?m following this PR:
> https://github.com/apache/cordova-ios/pull/104
> what is the other one?
>
> >
> > So I propose that we don?t release the plugin, but wait on cordova to
> update so that manual steps will no longer be needed, or we add a big
> Notice on how to install use this plugin.
> >
> > WDYT?
>
> what about doing an early adopter release of the plugin with its demo and
> blog post explaining the current difficulties (which require manual steps)
> and talk about what?s next in cordova-ios: workspace instead of just
> project?


+1 I like the idea

Especially since our Cordova OAuth2 plugin is not just about iOS. It's
about Android as well.

I am in line w/ Corinne: mark the iOS side of the OAuth2 plugin as
'experiemental, and release note (or blog) the odd parts. I'd prefer a blog
post on Aerogear.org, instead of a private one



> I can hel with testing and blog post.
>

+1 count me in!


>
> where is your current demo? is it this repo:
>
> https://github.com/edewit/aerogear-cordova-cookbook/tree/swift-oauth2-plugin
> ?
>
> >
> >       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
>



-- 
Matthias Wessendorf

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

From edewit at redhat.com  Tue Oct 28 06:03:57 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 28 Oct 2014 11:03:57 +0100
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <CAAg5f2ShJNrYL8fJNU0SBOBNLKYMNQLbSDAFj1VcB19KqBUsbg@mail.gmail.com>
References: <20141027184800.GA17333@abstractj.org>
	<CAAg5f2ShJNrYL8fJNU0SBOBNLKYMNQLbSDAFj1VcB19KqBUsbg@mail.gmail.com>
Message-ID: <4D884830-CA57-4750-BCD7-18814B52CFFB@redhat.com>

I never got docker to work on my box, always have this error you report. You could try Boot2Docker although that kinda defies the purpose of docker.

On 28 Oct,2014, at 9:46 , Matthias Wessendorf <matzew at apache.org> wrote:

> Hrm, at some point it worked for me, on my box :)
> 
> but, now I did it again, and I got a timeout:
> 
> docker run -it -p 8443:8443 aerogear/unifiedpush-wildfly
> 2014/10/28 09:44:51 Post http://192.168.59.103:2375/v1.15/containers/create: dial tcp 192.168.59.103:2375: i/o timeout
> 
> 
> docker --version
> Docker version 1.3.0, build c78088f
> 
> 
> 
> Anyone noticed that too ? 
> 
> 
> 
> 
> On Mon, Oct 27, 2014 at 7:48 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> Good morning,
> 
> As you may know few months ago we started to work on Docker images, with
> the support of Marek Goldmann ? the main responsible for leading the efforts on
> Docker (https://github.com/jboss-dockerfiles).
> 
> I asked Matthias to create a fork of
> https://github.com/jboss-dockerfiles/aerogear, into this way the
> team can make our images more mature, before send to the official repository.
> Also, my files were moved from my personal repository to AeroGear's fork
> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
> 
> The AeroGear organization was created on Docker Hub
> https://registry.hub.docker.com/repos/aerogear/ to host our official
> images, the build of the images were automated and Marek was added as one of the admins.
> 
> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
> on Docker Hub.
> 
> If you have any questions, go ahead.
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/05dfb753/attachment.html 

From cvasilak at gmail.com  Tue Oct 28 06:59:44 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 28 Oct 2014 12:59:44 +0200
Subject: [aerogear-dev] [site] community page overhaul ?
In-Reply-To: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>
References: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>
Message-ID: <54828BAA-28BF-42FA-9C22-539BC954098F@gmail.com>

+1 on the idea, maybe reuse and update accordingly existing [1]

I can give it a spin if you like later this week, create a JIRA if it doesn?t exist already and assign to me

-
Christos

 
[1] http://aerogear.org/docs/guides/Contributing/


On Oct 28, 2014, at 10:20 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> Hi,
> 
> I realized that atm we don't link to our users list, a quick/urgent fix for that is here:
> https://github.com/aerogear/aerogear.org/pull/410
> 
> That perhaps not enough! On the 'community' link we basically include the archive of the dev list.
> 
> What should we do with that community section? How about the following
> 
> Instead of including the archive (as part of the website), we can tweak the 'community' page a bit.
> E.g. we list the different options we have for users to reach out:
>  ** links to users/dev ML subscribe page
>  ** links to users/dev ML archives
>  ** info on IRC
>  ** link to our github landing page
>  ** info on our twitter account 
> 
> I think the benefit of including this on a dedicated page, makes the info also a bit more visible, instead of just having links to ML at the footer of our website
> 
> 
> What are your thoughts?
> 
> 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/20141028/cb3cd989/attachment.html 

From qmx at qmx.me  Tue Oct 28 07:01:56 2014
From: qmx at qmx.me (Douglas Campos)
Date: Tue, 28 Oct 2014 09:01:56 -0200
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <4D884830-CA57-4750-BCD7-18814B52CFFB@redhat.com>
References: <20141027184800.GA17333@abstractj.org>
	<CAAg5f2ShJNrYL8fJNU0SBOBNLKYMNQLbSDAFj1VcB19KqBUsbg@mail.gmail.com>
	<4D884830-CA57-4750-BCD7-18814B52CFFB@redhat.com>
Message-ID: <20141028110156.GE2256@darkstar.local>

On Tue, Oct 28, 2014 at 11:03:57AM +0100, Erik Jan de Wit wrote:
> I never got docker to work on my box, always have this error you
> report. You could try Boot2Docker although that kinda defies the
> purpose of docker.
If you're on OSX boot2docker is definitely the way to go. Lots of
workarounds on OSX weirdnesses :)


-- 
qmx

From matzew at apache.org  Tue Oct 28 07:56:47 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 12:56:47 +0100
Subject: [aerogear-dev] [site] community page overhaul ?
In-Reply-To: <54828BAA-28BF-42FA-9C22-539BC954098F@gmail.com>
References: <CAAg5f2RBmn1NrZvF88hrPYPb7TkLhpQAG+KOjQT7cGkaMRkavQ@mail.gmail.com>
	<54828BAA-28BF-42FA-9C22-539BC954098F@gmail.com>
Message-ID: <CAAg5f2SN9yEoKvrPqvCbi3hAEYNkx8T322OXgBH3=0dwp9e5ww@mail.gmail.com>

oh, that page is outdated too. Still talks about CLA :)

I will address both later this week

On Tue, Oct 28, 2014 at 11:59 AM, Christos Vasilakis <cvasilak at gmail.com>
wrote:

> +1 on the idea, maybe reuse and update accordingly existing [1]
>
> I can give it a spin if you like later this week, create a JIRA if it
> doesn?t exist already and assign to me
>
> -
> Christos
>
>
> [1] http://aerogear.org/docs/guides/Contributing/
>
>
> On Oct 28, 2014, at 10:20 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> Hi,
>
> I realized that atm we don't link to our users list, a quick/urgent fix
> for that is here:
> https://github.com/aerogear/aerogear.org/pull/410
>
> That perhaps not enough! On the 'community' link we basically include the
> archive of the dev list.
>
> What should we do with that community section? How about the following
>
> Instead of including the archive (as part of the website), we can tweak
> the 'community' page a bit.
> E.g. we list the different options we have for users to reach out:
>  ** links to users/dev ML subscribe page
>  ** links to users/dev ML archives
>  ** info on IRC
>  ** link to our github landing page
>  ** info on our twitter account
>
> I think the benefit of including this on a dedicated page, makes the info
> also a bit more visible, instead of just having links to ML at the footer
> of our website
>
>
> What are your thoughts?
>
> 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/20141028/bc532ca2/attachment.html 

From matzew at apache.org  Tue Oct 28 08:35:19 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 13:35:19 +0100
Subject: [aerogear-dev] [UPS] Integrating of Keycloak 1.0.3
Message-ID: <CAAg5f2RYdZ+4YqXWRfxQ0MrhtDywVxR3oPK3Vkqbp+fKKyBCiQ@mail.gmail.com>

Hi,

the Keycloak team is close to release their 1.0.3 version.

To speed things up, I prepared our parent already:
https://github.com/aerogear/aerogear-parent/commit/05413271735d4deeafd9f9cee5e1e72a06e97677


and tested our latest against their 1.0.3 release branch:
http://lists.jboss.org/pipermail/keycloak-dev/2014-October/002899.html

Once the bits are available on maven central, we can immediately jump on
that train  (see [1]) and afterwards get our 1.0.2 released as well

-Matthias

[1] https://issues.jboss.org/browse/AGPUSH-1079


-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Tue Oct 28 08:37:18 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 08:37:18 -0400
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <20141027184800.GA17333@abstractj.org>
References: <20141027184800.GA17333@abstractj.org>
Message-ID: <EB253872-8342-42E4-A44A-EB48B79C693D@redhat.com>

this is rad!
> On Oct 27, 2014, at 2:48 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> 
> Good morning,
> 
> As you may know few months ago we started to work on Docker images, with
> the support of Marek Goldmann ? the main responsible for leading the efforts on
> Docker (https://github.com/jboss-dockerfiles).
> 
> I asked Matthias to create a fork of
> https://github.com/jboss-dockerfiles/aerogear, into this way the
> team can make our images more mature, before send to the official repository.
> Also, my files were moved from my personal repository to AeroGear's fork
> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
> 
> The AeroGear organization was created on Docker Hub
> https://registry.hub.docker.com/repos/aerogear/ to host our official
> images, the build of the images were automated and Marek was added as one of the admins.
> 
> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
> on Docker Hub.
> 
> If you have any questions, go ahead.
> 
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> 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 Oct 28 09:15:18 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 28 Oct 2014 14:15:18 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAFJm-3HTXNQEqP-3aa0PE=Tom_7mRdy8AdNT4aTmiRx-0k2WzA@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
	<CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
	<CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>
	<66956EEB-6CD7-4C26-8863-7214F8B1D594@gmail.com>
	<CAFJm-3HTXNQEqP-3aa0PE=Tom_7mRdy8AdNT4aTmiRx-0k2WzA@mail.gmail.com>
Message-ID: <CAD_dpu210ywekGYjjWSy3LS1BcFYxWKJp5pnB+LsUNfY7YfzaA@mail.gmail.com>

Okay "user-data" seems to be the winner ;)
Let's go for that  !

NB : For the JavaSender, it will be camelCased  message.userData(...)



On Tue, Oct 28, 2014 at 8:17 AM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> +1 for user-data
>
> On 28 October 2014 08:11, Christos Vasilakis <cvasilak at gmail.com> wrote:
>
>> +1 for user-data
>>
>> -
>> Christos
>>
>>
>> On Oct 28, 2014, at 2:30 AM, Daniel Passos <daniel at passos.me> wrote:
>>
>> -1 to payload, +1 to user-data || userData
>>
>> -- Passos
>>
>> On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me> wrote:
>>>
>>>> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
>>>> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me> wrote:
>>>> > > 'payload' is the term used for this kind of "in-message custom data"
>>>> > > since the early years of EIP tools (before camel was born)
>>>> > >
>>>> > > nested payload, inside of message, I am not sure
>>>> > >
>>>> >
>>>> > Thinking a bit more about it, I don?t like data (it?s to generic
>>>> > everything is data) and I don?t like payload either (because
>>>> > everything is message payload) can?t we use something like
>>>> > ?customData? , ?userData?, `userKeys` or perhaps something that says a
>>>> > little bit more to what this is.
>>>> +1 to userData, clearly communicates intent (if y'all dislike payload)
>>>> :D
>>>>
>>>
>>> how about user-data  ?
>>> (due to consistency ?) :)
>>>
>>>
>>>
>>>
>>>>
>>>> --
>>>> qmx
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20141028/ab2e9b02/attachment.html 

From matzew at apache.org  Tue Oct 28 09:21:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 14:21:24 +0100
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAD_dpu210ywekGYjjWSy3LS1BcFYxWKJp5pnB+LsUNfY7YfzaA@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
	<CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
	<CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>
	<66956EEB-6CD7-4C26-8863-7214F8B1D594@gmail.com>
	<CAFJm-3HTXNQEqP-3aa0PE=Tom_7mRdy8AdNT4aTmiRx-0k2WzA@mail.gmail.com>
	<CAD_dpu210ywekGYjjWSy3LS1BcFYxWKJp5pnB+LsUNfY7YfzaA@mail.gmail.com>
Message-ID: <CAAg5f2RDv0fhXFBkj6=V3+c3-GiQY3yif752tDc5FB7RSStPdg@mail.gmail.com>

On Tue, Oct 28, 2014 at 2:15 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Okay "user-data" seems to be the winner ;)
> Let's go for that  !
>
> NB : For the JavaSender, it will be camelCased  message.userData(...)
>

+1


>
>
>
> On Tue, Oct 28, 2014 at 8:17 AM, Daniel Bevenius <
> daniel.bevenius at gmail.com> wrote:
>
>> +1 for user-data
>>
>> On 28 October 2014 08:11, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>
>>> +1 for user-data
>>>
>>> -
>>> Christos
>>>
>>>
>>> On Oct 28, 2014, at 2:30 AM, Daniel Passos <daniel at passos.me> wrote:
>>>
>>> -1 to payload, +1 to user-data || userData
>>>
>>> -- Passos
>>>
>>> On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me> wrote:
>>>>
>>>>> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
>>>>> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me>
>>>>> wrote:
>>>>> > > 'payload' is the term used for this kind of "in-message custom
>>>>> data"
>>>>> > > since the early years of EIP tools (before camel was born)
>>>>> > >
>>>>> > > nested payload, inside of message, I am not sure
>>>>> > >
>>>>> >
>>>>> > Thinking a bit more about it, I don?t like data (it?s to generic
>>>>> > everything is data) and I don?t like payload either (because
>>>>> > everything is message payload) can?t we use something like
>>>>> > ?customData? , ?userData?, `userKeys` or perhaps something that says
>>>>> a
>>>>> > little bit more to what this is.
>>>>> +1 to userData, clearly communicates intent (if y'all dislike payload)
>>>>> :D
>>>>>
>>>>
>>>> how about user-data  ?
>>>> (due to consistency ?) :)
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> --
>>>>> qmx
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141028/73a9e111/attachment.html 

From lholmqui at redhat.com  Tue Oct 28 09:33:06 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 09:33:06 -0400
Subject: [aerogear-dev] message format change proposal
In-Reply-To: <CAAg5f2RDv0fhXFBkj6=V3+c3-GiQY3yif752tDc5FB7RSStPdg@mail.gmail.com>
References: <BD5E57BE-1324-4E22-A476-176A3F45783F@redhat.com>
	<CAAg5f2SO5bAmahM5Xf=5tFxyviCJkBJsyp=DAKjf7O_mRQ13bA@mail.gmail.com>
	<CAD_dpu3RykV-A2Tg0BzS8FuvOHSN9Ua08OW81Wmt=DUpdUuQjg@mail.gmail.com>
	<20141027141544.GA2256@darkstar.local>
	<CAAg5f2TSEejWmzh_zuD6pB+M3MvXOR3s34GqwDsa_nn1Fsxn+g@mail.gmail.com>
	<C7A03AAF-4D1C-4F00-880D-8936296B2FB7@redhat.com>
	<20141027165028.GB2256@darkstar.local>
	<CAAg5f2TxoThVzvis+zPMSdXKLABPD1PpFxuJbdCcVQ5ZfCD4rQ@mail.gmail.com>
	<CAKjsGbu9heOJ2-r=X+tG1837SiAbkMKWC9xN0oFHffG5XEd5dw@mail.gmail.com>
	<66956EEB-6CD7-4C26-8863-7214F8B1D594@gmail.com>
	<CAFJm-3HTXNQEqP-3aa0PE=Tom_7mRdy8AdNT4aTmiRx-0k2WzA@mail.gmail.com>
	<CAD_dpu210ywekGYjjWSy3LS1BcFYxWKJp5pnB+LsUNfY7YfzaA@mail.gmail.com>
	<CAAg5f2RDv0fhXFBkj6=V3+c3-GiQY3yif752tDc5FB7RSStPdg@mail.gmail.com>
Message-ID: <8A8C942C-A255-42C8-8B5A-473FF622180C@redhat.com>


> On Oct 28, 2014, at 9:21 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Tue, Oct 28, 2014 at 2:15 PM, Sebastien Blanc <scm.blanc at gmail.com <mailto:scm.blanc at gmail.com>> wrote:
> Okay "user-data" seems to be the winner ;) 
> Let's go for that  !
> 
> NB : For the JavaSender, it will be camelCased  message.userData(...)
> 
> +1

should be no change other than docs for the node sender then

>  
> 
> 
> 
> On Tue, Oct 28, 2014 at 8:17 AM, Daniel Bevenius <daniel.bevenius at gmail.com <mailto:daniel.bevenius at gmail.com>> wrote:
> +1 for user-data
> 
> On 28 October 2014 08:11, Christos Vasilakis <cvasilak at gmail.com <mailto:cvasilak at gmail.com>> wrote:
> +1 for user-data
> 
> -
> Christos
> 
> 
> On Oct 28, 2014, at 2:30 AM, Daniel Passos <daniel at passos.me <mailto:daniel at passos.me>> wrote:
> 
>> -1 to payload, +1 to user-data || userData
>> 
>> -- Passos
>> 
>> On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> 
>> On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx at qmx.me <mailto:qmx at qmx.me>> wrote:
>> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote:
>> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx at qmx.me <mailto:qmx at qmx.me>> wrote:
>> > > 'payload' is the term used for this kind of "in-message custom data"
>> > > since the early years of EIP tools (before camel was born)
>> > >
>> > > nested payload, inside of message, I am not sure
>> > >
>> >
>> > Thinking a bit more about it, I don?t like data (it?s to generic
>> > everything is data) and I don?t like payload either (because
>> > everything is message payload) can?t we use something like
>> > ?customData? , ?userData?, `userKeys` or perhaps something that says a
>> > little bit more to what this is.
>> +1 to userData, clearly communicates intent (if y'all dislike payload) :D
>> 
>> how about user-data  ? 
>> (due to consistency ?) :)
>> 
>> 
>>  
>> 
>> --
>> qmx
>> _______________________________________________
>> 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>
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
> 
> _______________________________________________
> 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>
> 
> 
> _______________________________________________
> 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>
> 
> 
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/adc6fc5c/attachment-0001.html 

From matzew at apache.org  Tue Oct 28 10:31:38 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 15:31:38 +0100
Subject: [aerogear-dev] external config for senders ?
Message-ID: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>

Hi,

on the Cordova 1.0.2 push plugin, we now have the handy option to configure
the server settings in an external JSON file.


A few days we spoke about this for the senders as well. Now, after a few
days, I am wondering, does it make sense to have an external configuration
file for our node.js/java senders ?

-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/20141028/76fecca5/attachment.html 

From lholmqui at redhat.com  Tue Oct 28 10:36:17 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 10:36:17 -0400
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
Message-ID: <C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>


> On Oct 28, 2014, at 10:31 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> Hi,
> 
> on the Cordova 1.0.2 push plugin, we now have the handy option to configure the server settings in an external JSON file.
> 
> 
> A few days we spoke about this for the senders as well. Now, after a few days, I am wondering, does it make sense to have an external configuration file for our node.js/java senders ? 

for the node sender, this would be a nice thing, loading it should be as easy as  ?require(?external_config.json')"

> 
> -Matthias
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141028/14c99e28/attachment.html 

From scm.blanc at gmail.com  Tue Oct 28 10:39:31 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 28 Oct 2014 15:39:31 +0100
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
Message-ID: <CAD_dpu1iiHvw7Fj5-gNfTHQnOz6JUozqJXEJYwxLg5hxe92WTQ@mail.gmail.com>

+1
Since we are talking about the sender part maybe in the config we could add
more than 1 config , (think of multitenant apps using different UPS configs)

[
{
 "name":"Customer1App",
 "url":"url",
 "PushId":"shht",
 "MasterSecret":"shht"
},
{
 "name":"Customer2App",
 "url":"url",
 "PushId":"shht",
 "MasterSecret":"shht"
},
...
]
We could even pass a "default" flag for one of the config items.

wdyt ?




On Tue, Oct 28, 2014 at 3:31 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> on the Cordova 1.0.2 push plugin, we now have the handy option to
> configure the server settings in an external JSON file.
>
>
> A few days we spoke about this for the senders as well. Now, after a few
> days, I am wondering, does it make sense to have an external configuration
> file for our node.js/java senders ?
>
> -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/20141028/200c1f76/attachment.html 

From matzew at apache.org  Tue Oct 28 10:42:25 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 15:42:25 +0100
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAD_dpu1iiHvw7Fj5-gNfTHQnOz6JUozqJXEJYwxLg5hxe92WTQ@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<CAD_dpu1iiHvw7Fj5-gNfTHQnOz6JUozqJXEJYwxLg5hxe92WTQ@mail.gmail.com>
Message-ID: <CAAg5f2SyLUNLVePHzris63uFP8djFoLyeFAkVF2y_qenpTr_YA@mail.gmail.com>

On Tue, Oct 28, 2014 at 3:39 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> +1
> Since we are talking about the sender part maybe in the config we could
> add more than 1 config , (think of multitenant apps using different UPS
> configs)
>
> [
> {
>  "name":"Customer1App",
>  "url":"url",
>  "PushId":"shht",
>  "MasterSecret":"shht"
> },
> {
>  "name":"Customer2App",
>  "url":"url",
>  "PushId":"shht",
>  "MasterSecret":"shht"
> },
> ...
> ]
> We could even pass a "default" flag for one of the config items.
>
> wdyt ?
>

uh, not sure. Can you explain, why I want a global config?

I'd rather have something, per app



>
>
>
>
> On Tue, Oct 28, 2014 at 3:31 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> on the Cordova 1.0.2 push plugin, we now have the handy option to
>> configure the server settings in an external JSON file.
>>
>>
>> A few days we spoke about this for the senders as well. Now, after a few
>> days, I am wondering, does it make sense to have an external configuration
>> file for our node.js/java senders ?
>>
>> -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/20141028/17359e81/attachment.html 

From matzew at apache.org  Tue Oct 28 10:43:00 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 15:43:00 +0100
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>
Message-ID: <CAAg5f2RZkNxvAEq6AWZnRuYHOsrM--vuyGyQg9qGP=qCJFrN3g@mail.gmail.com>

On Tue, Oct 28, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

>
> On Oct 28, 2014, at 10:31 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> Hi,
>
> on the Cordova 1.0.2 push plugin, we now have the handy option to
> configure the server settings in an external JSON file.
>
>
> A few days we spoke about this for the senders as well. Now, after a few
> days, I am wondering, does it make sense to have an external configuration
> file for our node.js/java senders ?
>
>
> for the node sender, this would be a nice thing, loading it should be as
> easy as  ?require(?external_config.json')"
>


oh, that sounds quick :) sounds reasonable to do for next release ;-)


>
>
> -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/20141028/e04b6f62/attachment.html 

From lholmqui at redhat.com  Tue Oct 28 10:48:22 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 10:48:22 -0400
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAAg5f2RZkNxvAEq6AWZnRuYHOsrM--vuyGyQg9qGP=qCJFrN3g@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>
	<CAAg5f2RZkNxvAEq6AWZnRuYHOsrM--vuyGyQg9qGP=qCJFrN3g@mail.gmail.com>
Message-ID: <4E257F32-880D-4BC7-9F55-FBED536E2FF9@redhat.com>

technically, a user can already load the settings from an external config,

> On Oct 28, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Tue, Oct 28, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> On Oct 28, 2014, at 10:31 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> Hi,
>> 
>> on the Cordova 1.0.2 push plugin, we now have the handy option to configure the server settings in an external JSON file.
>> 
>> 
>> A few days we spoke about this for the senders as well. Now, after a few days, I am wondering, does it make sense to have an external configuration file for our node.js/java senders ? 
> 
> for the node sender, this would be a nice thing, loading it should be as easy as  ?require(?external_config.json')"
> 
> 
> oh, that sounds quick :) sounds reasonable to do for next release ;-)
>  
> 
>> 
>> -Matthias
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141028/dc01e479/attachment-0001.html 

From scm.blanc at gmail.com  Tue Oct 28 10:53:52 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 28 Oct 2014 15:53:52 +0100
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAAg5f2SyLUNLVePHzris63uFP8djFoLyeFAkVF2y_qenpTr_YA@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<CAD_dpu1iiHvw7Fj5-gNfTHQnOz6JUozqJXEJYwxLg5hxe92WTQ@mail.gmail.com>
	<CAAg5f2SyLUNLVePHzris63uFP8djFoLyeFAkVF2y_qenpTr_YA@mail.gmail.com>
Message-ID: <CAD_dpu1ELXrSXW23yaXJZH2ckVD67wWZ4EY+nPc-uf+GXJK5Fg@mail.gmail.com>

On Tue, Oct 28, 2014 at 3:42 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Tue, Oct 28, 2014 at 3:39 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> +1
>> Since we are talking about the sender part maybe in the config we could
>> add more than 1 config , (think of multitenant apps using different UPS
>> configs)
>>
>> [
>> {
>>  "name":"Customer1App",
>>  "url":"url",
>>  "PushId":"shht",
>>  "MasterSecret":"shht"
>> },
>> {
>>  "name":"Customer2App",
>>  "url":"url",
>>  "PushId":"shht",
>>  "MasterSecret":"shht"
>> },
>> ...
>> ]
>> We could even pass a "default" flag for one of the config items.
>>
>> wdyt ?
>>
>
> uh, not sure. Can you explain, why I want a global config?
>
> I'd rather have something, per app
>

I think, that often, one single Backend will have to deal with different
Push Applications. Imagine a company using UPS to deploy its own
UrbanAirship/Parse stuff , having a plenty of users or a custom mBaaS
solution.

Or even, to be able to switch easily from a test/dev/user acceptance
environement.



>
>
>>
>>
>>
>>
>> On Tue, Oct 28, 2014 at 3:31 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> on the Cordova 1.0.2 push plugin, we now have the handy option to
>>> configure the server settings in an external JSON file.
>>>
>>>
>>> A few days we spoke about this for the senders as well. Now, after a few
>>> days, I am wondering, does it make sense to have an external configuration
>>> file for our node.js/java senders ?
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/c11c045c/attachment.html 

From matzew at apache.org  Tue Oct 28 10:54:41 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 15:54:41 +0100
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <4E257F32-880D-4BC7-9F55-FBED536E2FF9@redhat.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>
	<CAAg5f2RZkNxvAEq6AWZnRuYHOsrM--vuyGyQg9qGP=qCJFrN3g@mail.gmail.com>
	<4E257F32-880D-4BC7-9F55-FBED536E2FF9@redhat.com>
Message-ID: <CAAg5f2Rdo8Rt+JyRSHcouePb-sJpvB-MRTZ0D0z_-W7y=r=fiw@mail.gmail.com>

On Tue, Oct 28, 2014 at 3:48 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

> technically, a user can already load the settings from an external config,
>

so, it's just a matter of updating the demo and 'document' it ?


>
> On Oct 28, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>
>
> On Tue, Oct 28, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>> On Oct 28, 2014, at 10:31 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>> Hi,
>>
>> on the Cordova 1.0.2 push plugin, we now have the handy option to
>> configure the server settings in an external JSON file.
>>
>>
>> A few days we spoke about this for the senders as well. Now, after a few
>> days, I am wondering, does it make sense to have an external configuration
>> file for our node.js/java senders ?
>>
>>
>> for the node sender, this would be a nice thing, loading it should be as
>> easy as  ?require(?external_config.json')"
>>
>
>
> oh, that sounds quick :) sounds reasonable to do for next release ;-)
>
>
>>
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Tue Oct 28 10:56:54 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 15:56:54 +0100
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAD_dpu1ELXrSXW23yaXJZH2ckVD67wWZ4EY+nPc-uf+GXJK5Fg@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<CAD_dpu1iiHvw7Fj5-gNfTHQnOz6JUozqJXEJYwxLg5hxe92WTQ@mail.gmail.com>
	<CAAg5f2SyLUNLVePHzris63uFP8djFoLyeFAkVF2y_qenpTr_YA@mail.gmail.com>
	<CAD_dpu1ELXrSXW23yaXJZH2ckVD67wWZ4EY+nPc-uf+GXJK5Fg@mail.gmail.com>
Message-ID: <CAAg5f2SrdG0=VH66mpisYN5LT3ydNfEVZ-PopZW9vXgdMB8VwQ@mail.gmail.com>

On Tue, Oct 28, 2014 at 3:53 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> On Tue, Oct 28, 2014 at 3:42 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Tue, Oct 28, 2014 at 3:39 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> +1
>>> Since we are talking about the sender part maybe in the config we could
>>> add more than 1 config , (think of multitenant apps using different UPS
>>> configs)
>>>
>>> [
>>> {
>>>  "name":"Customer1App",
>>>  "url":"url",
>>>  "PushId":"shht",
>>>  "MasterSecret":"shht"
>>> },
>>> {
>>>  "name":"Customer2App",
>>>  "url":"url",
>>>  "PushId":"shht",
>>>  "MasterSecret":"shht"
>>> },
>>> ...
>>> ]
>>> We could even pass a "default" flag for one of the config items.
>>>
>>> wdyt ?
>>>
>>
>> uh, not sure. Can you explain, why I want a global config?
>>
>> I'd rather have something, per app
>>
>
> I think, that often, one single Backend will have to deal with different
> Push Applications. Imagine a company using UPS to deploy its own
> UrbanAirship/Parse stuff , having a plenty of users or a custom mBaaS
> solution.
>

hrm, not sure.

How would you than trigger, or glue the different settings? and when do you
know which one is used ?

I'd rather perfer "one.json" and "two.json" being on the classpath, and
than have the Sender 'reference' to it:

somesender = new Sender(new file("one.json"));

// somewhere lese in the app:
someOtherSender = new Sender(new file("two.json"));



>
> Or even, to be able to switch easily from a test/dev/user acceptance
> environement.
>
>
>
>>
>>
>>>
>>>
>>>
>>>
>>> On Tue, Oct 28, 2014 at 3:31 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> on the Cordova 1.0.2 push plugin, we now have the handy option to
>>>> configure the server settings in an external JSON file.
>>>>
>>>>
>>>> A few days we spoke about this for the senders as well. Now, after a
>>>> few days, I am wondering, does it make sense to have an external
>>>> configuration file for our node.js/java senders ?
>>>>
>>>> -Matthias
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Tue Oct 28 11:00:02 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 11:00:02 -0400
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <CAAg5f2Rdo8Rt+JyRSHcouePb-sJpvB-MRTZ0D0z_-W7y=r=fiw@mail.gmail.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>
	<CAAg5f2RZkNxvAEq6AWZnRuYHOsrM--vuyGyQg9qGP=qCJFrN3g@mail.gmail.com>
	<4E257F32-880D-4BC7-9F55-FBED536E2FF9@redhat.com>
	<CAAg5f2Rdo8Rt+JyRSHcouePb-sJpvB-MRTZ0D0z_-W7y=r=fiw@mail.gmail.com>
Message-ID: <5B13B270-B280-46B2-9A68-D41A5CEF9648@redhat.com>


> On Oct 28, 2014, at 10:54 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Tue, Oct 28, 2014 at 3:48 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> technically, a user can already load the settings from an external config,
> 
> so, it's just a matter of updating the demo and 'document' it ? 

yea,  pretty much

>  
> 
>> On Oct 28, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> 
>> 
>> On Tue, Oct 28, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> 
>>> On Oct 28, 2014, at 10:31 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>> 
>>> Hi,
>>> 
>>> on the Cordova 1.0.2 push plugin, we now have the handy option to configure the server settings in an external JSON file.
>>> 
>>> 
>>> A few days we spoke about this for the senders as well. Now, after a few days, I am wondering, does it make sense to have an external configuration file for our node.js/java senders ? 
>> 
>> for the node sender, this would be a nice thing, loading it should be as easy as  ?require(?external_config.json')"
>> 
>> 
>> oh, that sounds quick :) sounds reasonable to do for next release ;-)
>>  
>> 
>>> 
>>> -Matthias
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>> twitter: http://twitter.com/mwessendorf <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 <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>
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/2d793889/attachment.html 

From bruno at abstractj.org  Tue Oct 28 12:01:55 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 28 Oct 2014 09:01:55 -0700 (PDT)
Subject: [aerogear-dev] Docker images on AeroGear
In-Reply-To: <CAAg5f2ShJNrYL8fJNU0SBOBNLKYMNQLbSDAFj1VcB19KqBUsbg@mail.gmail.com>
References: <CAAg5f2ShJNrYL8fJNU0SBOBNLKYMNQLbSDAFj1VcB19KqBUsbg@mail.gmail.com>
Message-ID: <1414512115032.881fefe9@Nodemailer>

Nothing here. Is boot2docker? How you docker environment variables look?



?

abstractj
PGP: 0x84DC9914

On Tue, Oct 28, 2014 at 6:46 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hrm, at some point it worked for me, on my box :)
> but, now I did it again, and I got a timeout:
> docker run -it -p 8443:8443 aerogear/unifiedpush-wildfly
> 2014/10/28 09:44:51 Post http://192.168.59.103:2375/v1.15/containers/create:
> dial tcp 192.168.59.103:2375: i/o timeout
> docker --version
> Docker version 1.3.0, build c78088f
> Anyone noticed that too ?
> On Mon, Oct 27, 2014 at 7:48 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>> Good morning,
>>
>> As you may know few months ago we started to work on Docker images, with
>> the support of Marek Goldmann ? the main responsible for leading the
>> efforts on
>> Docker (https://github.com/jboss-dockerfiles).
>>
>> I asked Matthias to create a fork of
>> https://github.com/jboss-dockerfiles/aerogear, into this way the
>> team can make our images more mature, before send to the official
>> repository.
>> Also, my files were moved from my personal repository to AeroGear's fork
>> (https://github.com/abstractj/docker/blob/master/aerogear/README.md)
>>
>> The AeroGear organization was created on Docker Hub
>> https://registry.hub.docker.com/repos/aerogear/ to host our official
>> images, the build of the images were automated and Marek was added as one
>> of the admins.
>>
>> The reason for having images like: aerogear/unifiedpush-as7-dev instead of
>> jboss/aerogear-unifiedpush-as7-dev. Is the limitation of 30 characters
>> on Docker Hub.
>>
>> If you have any questions, go ahead.
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> -- 
> Matthias Wessendorf
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/71e7cb6f/attachment.html 

From bruno at abstractj.org  Tue Oct 28 13:32:17 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 28 Oct 2014 15:32:17 -0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
 cartridge
In-Reply-To: <CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
References: <1413994384.6296.51.camel@kpiwko-x220>
	<CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
Message-ID: <20141028173217.GA41648@abstractj.org>

On 2014-10-23, Matthias Wessendorf wrote:
> On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:
>
> > Hi All,
> >
> > I'd like to know your opinion on following changes to UnifiedPush
> > Server. They are both focused on improving customization process for the
> > cartridge.
> >
> > Just in short, current update process now:
> > 1/ Clone official git repository of cartridge
> > 2/ Extract wars and do the modifications or build ones
> > 3/ Package wars
> > 4/ Push cartridge to your own repository
> > 5/ Create cartridge from your own repository
> >
> > Whereas, I'm proposing:
> > 1/ Create cartridge from official repository
> > 2/ Clone git repository for gear created by Openshift (by default if rhc
> > is used)
> > 3/ Modify some files there we expose for user modification
> > 4/ Push back to make changes live
> >
> > What particular configuration elements I'm interested to have
> > externalized?
> >
> > 1/ Ability to load keycloak.json from external location
> >
> > => This allows user to create cartridge and modify it prior the first
> > access. This allows users to configure it to be consumable by other
> > services automatically, e.g. they can add developer users, roles, etc.
> >
>
> hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
> have an idea here

Everything is possible with software, the question is: do we really need
this? How would you feel if keycloak.json was changed by the wrong
person?

Can we as a project guarantee the security of this file outside the
server?

>
>
>
> >
> > 2/ Externalize GCM/APNs locations
> >
> > => Now, URLs are hardcoded in GCM/APNs JARs.
>
>
> yes, they are considered stable APIs :)
>
> We are not going to 'externalize' these URLs
>
>
> > If they would be loaded
> > from external location (defaults can still be hardcoded), this allows
> > user to easily check business logic that queries data in UPS and not
> > sending any messages. Also allows to put proxy in between UPS and
> > APNs/GCMs.
> >
> > Both these will significantly reduce QE overhead. However, I believe
> > they are valuable for other as well.
> >
> > Feedback and tomatoes (I prefer plum ones) are welcomed.
> >
> > Thanks,
> >
> > Karel
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Tue Oct 28 13:33:36 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 28 Oct 2014 15:33:36 -0200
Subject: [aerogear-dev] Improving customization abilities of OpenShift
 cartridge
In-Reply-To: <CAAg5f2TKV0VZzQhHpN7bupLwjq1Kndzi15=jLJ7v=LVZq7vG1g@mail.gmail.com>
References: <1413994384.6296.51.camel@kpiwko-x220>
	<CAAg5f2SCxdC6SbPxQgf4gfsfoYcc4T-wS3hEL7HnPuWgOpOpMw@mail.gmail.com>
	<CAAg5f2Qj9dGsOwmmEbzPs55gfMGmhrd7agqq_89sQELDCe3jgQ@mail.gmail.com>
	<CAD_dpu1Haqdj38nYsGQ_ftArS3VaoNMMMyDHp5yWL-YisXyUYQ@mail.gmail.com>
	<CAAg5f2TKV0VZzQhHpN7bupLwjq1Kndzi15=jLJ7v=LVZq7vG1g@mail.gmail.com>
Message-ID: <20141028173336.GB41648@abstractj.org>

+1 for leave as is.

On 2014-10-23, Matthias Wessendorf wrote:
> yes, our cartridge will still function like that
>
> I think what we can do for Karel, is have the realm.json file, for UPS so
> he and team can  import it into running keycloak.
>
> Our cartridge will stay as is, at least that's my (current) understanding
>
> On Thu, Oct 23, 2014 at 4:07 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
> > If we go for this let's make sure we have default values.
> > A lot of people might create an OpenShift App just using the online
> > interface and not clone it locally (and thus not modify the config files)
> >
> >
> > On Thu, Oct 23, 2014 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >
> >>
> >>
> >> On Thu, Oct 23, 2014 at 1:51 PM, Matthias Wessendorf <matzew at apache.org>
> >> wrote:
> >>
> >>>
> >>>
> >>> On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <kpiwko at redhat.com> wrote:
> >>>
> >>>> Hi All,
> >>>>
> >>>> I'd like to know your opinion on following changes to UnifiedPush
> >>>> Server. They are both focused on improving customization process for the
> >>>> cartridge.
> >>>>
> >>>> Just in short, current update process now:
> >>>> 1/ Clone official git repository of cartridge
> >>>> 2/ Extract wars and do the modifications or build ones
> >>>> 3/ Package wars
> >>>> 4/ Push cartridge to your own repository
> >>>> 5/ Create cartridge from your own repository
> >>>>
> >>>> Whereas, I'm proposing:
> >>>> 1/ Create cartridge from official repository
> >>>> 2/ Clone git repository for gear created by Openshift (by default if rhc
> >>>> is used)
> >>>> 3/ Modify some files there we expose for user modification
> >>>> 4/ Push back to make changes live
> >>>>
> >>>> What particular configuration elements I'm interested to have
> >>>> externalized?
> >>>>
> >>>> 1/ Ability to load keycloak.json from external location
> >>>>
> >>>> => This allows user to create cartridge and modify it prior the first
> >>>> access. This allows users to configure it to be consumable by other
> >>>> services automatically, e.g. they can add developer users, roles, etc.
> >>>>
> >>>
> >>> hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj
> >>> have an idea here
> >>>
> >>
> >> we could have our real in a JSON file, so that it is easy/easier to
> >> import it into an existing KC server, to run UPS against that
> >>
> >>
> >>>
> >>>
> >>>
> >>>>
> >>>> 2/ Externalize GCM/APNs locations
> >>>>
> >>>> => Now, URLs are hardcoded in GCM/APNs JARs.
> >>>
> >>>
> >>> yes, they are considered stable APIs :)
> >>>
> >>> We are not going to 'externalize' these URLs
> >>>
> >>>
> >>>> If they would be loaded
> >>>> from external location (defaults can still be hardcoded), this allows
> >>>> user to easily check business logic that queries data in UPS and not
> >>>> sending any messages. Also allows to put proxy in between UPS and
> >>>> APNs/GCMs.
> >>>>
> >>>> Both these will significantly reduce QE overhead. However, I believe
> >>>> they are valuable for other as well.
> >>>>
> >>>> Feedback and tomatoes (I prefer plum ones) are welcomed.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Karel
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From lholmqui at redhat.com  Tue Oct 28 15:21:34 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 15:21:34 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
Message-ID: <6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>

Here is the initial addition in one of my branches:  https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push <https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push>
> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com <mailto:edewit at redhat.com>> wrote:
>> 
>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> 
>>> 
>>> So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>
>>> 
>>> but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 
>> 
>> Right now a sender is configured to send notifications for one specific variant type, this mapping is configured on the top of the class:
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40>
>> 
>> so APNsPushNotificationSender will only be use for iOSVariant variants, so either we change the way this works or you create a new Sender ( that extends this one maybe )
> 
> I think i?ll just create a new sender of now just to get something working since the SafariVariant and iOSVariant will be combined into an APNsVariant in the near future.
> 
> sounds reasonable on getting this started
> 
> -M 
> 
> 
> 
>> 
>> Cheers,
>> 	Erik Jan
>> 
>> 
>> _______________________________________________
>> 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>
> 
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/c787ff7b/attachment.html 

From lholmqui at redhat.com  Tue Oct 28 15:35:59 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 28 Oct 2014 15:35:59 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
Message-ID: <D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>


The branch on the main repo  https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push <https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push>

subsequent PR?s will target this one

> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
> Here is the initial addition in one of my branches:  https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push <https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push>
>> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> 
>> 
>> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> 
>>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com <mailto:edewit at redhat.com>> wrote:
>>> 
>>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>>> 
>>>> 
>>>> So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>
>>>> 
>>>> but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 
>>> 
>>> Right now a sender is configured to send notifications for one specific variant type, this mapping is configured on the top of the class:
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40>
>>> 
>>> so APNsPushNotificationSender will only be use for iOSVariant variants, so either we change the way this works or you create a new Sender ( that extends this one maybe )
>> 
>> I think i?ll just create a new sender of now just to get something working since the SafariVariant and iOSVariant will be combined into an APNsVariant in the near future.
>> 
>> sounds reasonable on getting this started
>> 
>> -M 
>> 
>> 
>> 
>>> 
>>> Cheers,
>>> 	Erik Jan
>>> 
>>> 
>>> _______________________________________________
>>> 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>
>> 
>> _______________________________________________
>> 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>
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <https://lists.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/20141028/b73a5dcb/attachment-0001.html 

From ken at kenfinnigan.me  Tue Oct 28 16:15:35 2014
From: ken at kenfinnigan.me (Ken Finnigan)
Date: Tue, 28 Oct 2014 16:15:35 -0400
Subject: [aerogear-dev] SDKs for LiveOak
Message-ID: <CAKeeVe6yjwLfjRai+0+WwL8OdDZygWn4N3huZ4LS7CRYtyvk0w@mail.gmail.com>

All,

For the next release we're looking to create some SDKs for iOS, Android,
JavaScript and a Cordova plugin for use with LiveOak.

Our preference is to build on top of what Aerogear has already developed,
or even simply use the AeroGear SDK's with a different set of connection
options??

As the AeroGear team are well versed in various issues of developing SDKs,
I was hoping to get some advice as to the best way for us to develop ours
such that they're only a very thin layer on top of AeroGear's SDKs.

Thanks in advance!

Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/e9169420/attachment.html 

From matzew at apache.org  Tue Oct 28 16:42:33 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 28 Oct 2014 21:42:33 +0100
Subject: [aerogear-dev]  SDKs for LiveOak
In-Reply-To: <CAKeeVe6yjwLfjRai+0+WwL8OdDZygWn4N3huZ4LS7CRYtyvk0w@mail.gmail.com>
References: <CAKeeVe6yjwLfjRai+0+WwL8OdDZygWn4N3huZ4LS7CRYtyvk0w@mail.gmail.com>
Message-ID: <CAAg5f2T6OB27-=hrDJWOV+u+HypHiUWNz5xyYnsnCpUbsT_W-g@mail.gmail.com>

Hi Ken,

a while ago, I wrote a little prototype for an iOS SDK for LiveOak:

https://github.com/matzew/LOKIT

NOTE: Uses an old/outdated iOS library. For iOS you want our 2.x series,
with swift </note>

But to give an example:

That poc was (in the past) running against the chat example:
https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m

Internally (similar to your web-based demo at that time), it used:
- AeroGear-iOS for http communication
- Stomp-Kit for the Stomp connection

All behind one thin API (was matching the JS client at that time).

I think that's the direction you are interested in, right?

If yes, we can talk about more concrete ideas ;)

-Matthias



On Tue, Oct 28, 2014 at 9:15 PM, Ken Finnigan <ken at kenfinnigan.me
<javascript:_e(%7B%7D,'cvml','ken at kenfinnigan.me');>> wrote:

> All,
>
> For the next release we're looking to create some SDKs for iOS, Android,
> JavaScript and a Cordova plugin for use with LiveOak.
>
> Our preference is to build on top of what Aerogear has already developed,
> or even simply use the AeroGear SDK's with a different set of connection
> options??
>
> As the AeroGear team are well versed in various issues of developing SDKs,
> I was hoping to get some advice as to the best way for us to develop ours
> such that they're only a very thin layer on top of AeroGear's SDKs.
>
> Thanks in advance!
>
> Ken
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/d8426cf8/attachment.html 

From ken at kenfinnigan.me  Tue Oct 28 18:25:03 2014
From: ken at kenfinnigan.me (Ken Finnigan)
Date: Tue, 28 Oct 2014 18:25:03 -0400
Subject: [aerogear-dev] SDKs for LiveOak
In-Reply-To: <CAAg5f2T6OB27-=hrDJWOV+u+HypHiUWNz5xyYnsnCpUbsT_W-g@mail.gmail.com>
References: <CAKeeVe6yjwLfjRai+0+WwL8OdDZygWn4N3huZ4LS7CRYtyvk0w@mail.gmail.com>
	<CAAg5f2T6OB27-=hrDJWOV+u+HypHiUWNz5xyYnsnCpUbsT_W-g@mail.gmail.com>
Message-ID: <CAKeeVe4Xw0ysJNnL-AaNBtc7bp=s7UbsJyJK=+rcrnE1kT3r9A@mail.gmail.com>

Exactly what we're looking for.

Just something thin on top of AeroGear that handles any LiveOak specifics
like connecting and subscribing to STOMP, and what's needed for the REST
calls.

On Tue, Oct 28, 2014 at 4:42 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Ken,
>
> a while ago, I wrote a little prototype for an iOS SDK for LiveOak:
>
> https://github.com/matzew/LOKIT
>
> NOTE: Uses an old/outdated iOS library. For iOS you want our 2.x series,
> with swift </note>
>
> But to give an example:
>
> That poc was (in the past) running against the chat example:
> https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m
>
> Internally (similar to your web-based demo at that time), it used:
> - AeroGear-iOS for http communication
> - Stomp-Kit for the Stomp connection
>
> All behind one thin API (was matching the JS client at that time).
>
> I think that's the direction you are interested in, right?
>
> If yes, we can talk about more concrete ideas ;)
>
> -Matthias
>
>
>
> On Tue, Oct 28, 2014 at 9:15 PM, Ken Finnigan <ken at kenfinnigan.me> wrote:
>
>> All,
>>
>> For the next release we're looking to create some SDKs for iOS, Android,
>> JavaScript and a Cordova plugin for use with LiveOak.
>>
>> Our preference is to build on top of what Aerogear has already developed,
>> or even simply use the AeroGear SDK's with a different set of connection
>> options??
>>
>> As the AeroGear team are well versed in various issues of developing
>> SDKs, I was hoping to get some advice as to the best way for us to develop
>> ours such that they're only a very thin layer on top of AeroGear's SDKs.
>>
>> Thanks in advance!
>>
>> Ken
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> --
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141028/a39e3699/attachment.html 

From bruno at abstractj.org  Tue Oct 28 23:47:50 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 29 Oct 2014 01:47:50 -0200
Subject: [aerogear-dev] Logging on UPS
Message-ID: <20141029034750.GA51740@abstractj.org>

Good morning,

In the past we had
https://github.com/aerogear/aerogear-unifiedpush-server/pull/149. Any
specific reason for not having JBoss Logging or Log4j on UPS?

With the amount of traffic on UPS, it tends to become more complex to handle
log messages/files.

Thoughts?

--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Wed Oct 29 02:43:53 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 29 Oct 2014 07:43:53 +0100
Subject: [aerogear-dev] RELEASE: aerogear-parent 0.2.9
Message-ID: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>

Ahoy!

I am proposing another release, mainly to pick up new keycloak version
(1.0.3.Final), which contains several fixes.

The staging repo is here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/

Let me know about the release so we can get it out soon, to be on time for
our UPS release ;-)



-- 
Matthias Wessendorf

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

From matzew at apache.org  Wed Oct 29 02:50:07 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 29 Oct 2014 07:50:07 +0100
Subject: [aerogear-dev] Logging on UPS
In-Reply-To: <20141029034750.GA51740@abstractj.org>
References: <20141029034750.GA51740@abstractj.org>
Message-ID: <CAAg5f2QeoDRtHpgXPBSo2s4HrNLV=fhXirWc-QD0fbEzM3VLjw@mail.gmail.com>

On Wed, Oct 29, 2014 at 4:47 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> In the past we had
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/149. Any
> specific reason for not having JBoss Logging or Log4j on UPS?
>

yeah, there were some arguments against adding another dependency (since
JUL is part of the Java platform).
Also, as Burr said (see [1]) "we use it, we own it". That means, at some
point, we might be less or more the owner (e.g. regarding bugs inside of
JBoss logging),
also there cases when the runtime has a different version of JBoss logging
versus the one in UPS.

All these seamed not to be worth to go that route, in April this year


>
> With the amount of traffic on UPS, it tends to become more complex to
> handle
> log messages/files.
>
> Thoughts?
>

Sure, we can revisit this for the future 1.1.x line of the UnifiedPush
Server!

-Matthias

[1] http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007289.html



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



-- 
Matthias Wessendorf

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

From matzew at apache.org  Wed Oct 29 02:55:22 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 29 Oct 2014 07:55:22 +0100
Subject: [aerogear-dev] SDKs for LiveOak
In-Reply-To: <CAKeeVe4Xw0ysJNnL-AaNBtc7bp=s7UbsJyJK=+rcrnE1kT3r9A@mail.gmail.com>
References: <CAKeeVe6yjwLfjRai+0+WwL8OdDZygWn4N3huZ4LS7CRYtyvk0w@mail.gmail.com>
	<CAAg5f2T6OB27-=hrDJWOV+u+HypHiUWNz5xyYnsnCpUbsT_W-g@mail.gmail.com>
	<CAKeeVe4Xw0ysJNnL-AaNBtc7bp=s7UbsJyJK=+rcrnE1kT3r9A@mail.gmail.com>
Message-ID: <CAAg5f2RoDX_TxDTODL_8-KtFBec3TDT_wHBAKaobdwdizL7zyg@mail.gmail.com>

Perfect!

I think what I'd do is, to pick one platform (e.g. Android) and get a
feeling for a potential LiveOak SDK.

Our Android 2.0.0 (to continue on this platform for your POC) has been
split into a few modules, which different repos:
* https://github.com/aerogear/aerogear-android-core
* https://github.com/aerogear/aerogear-android-pipe
* https://github.com/aerogear/aerogear-android-auth
* https://github.com/aerogear/aerogear-android-authz
* https://github.com/aerogear/aerogear-android-security
* https://github.com/aerogear/aerogear-android-store
* https://github.com/aerogear/aerogear-android-push

If you need more details or have questions on our Android 2.0.0 series, I
think new, specific mailing list threads are the way go!

Greetings,
Matthias


On Tue, Oct 28, 2014 at 11:25 PM, Ken Finnigan <ken at kenfinnigan.me> wrote:

> Exactly what we're looking for.
>
> Just something thin on top of AeroGear that handles any LiveOak specifics
> like connecting and subscribing to STOMP, and what's needed for the REST
> calls.
>
> On Tue, Oct 28, 2014 at 4:42 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Ken,
>>
>> a while ago, I wrote a little prototype for an iOS SDK for LiveOak:
>>
>> https://github.com/matzew/LOKIT
>>
>> NOTE: Uses an old/outdated iOS library. For iOS you want our 2.x series,
>> with swift </note>
>>
>> But to give an example:
>>
>> That poc was (in the past) running against the chat example:
>> https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m
>>
>> Internally (similar to your web-based demo at that time), it used:
>> - AeroGear-iOS for http communication
>> - Stomp-Kit for the Stomp connection
>>
>> All behind one thin API (was matching the JS client at that time).
>>
>> I think that's the direction you are interested in, right?
>>
>> If yes, we can talk about more concrete ideas ;)
>>
>> -Matthias
>>
>>
>>
>> On Tue, Oct 28, 2014 at 9:15 PM, Ken Finnigan <ken at kenfinnigan.me> wrote:
>>
>>> All,
>>>
>>> For the next release we're looking to create some SDKs for iOS, Android,
>>> JavaScript and a Cordova plugin for use with LiveOak.
>>>
>>> Our preference is to build on top of what Aerogear has already
>>> developed, or even simply use the AeroGear SDK's with a different set of
>>> connection options??
>>>
>>> As the AeroGear team are well versed in various issues of developing
>>> SDKs, I was hoping to get some advice as to the best way for us to develop
>>> ours such that they're only a very thin layer on top of AeroGear's SDKs.
>>>
>>> Thanks in advance!
>>>
>>> Ken
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141029/dab6432c/attachment.html 

From avibelli at redhat.com  Wed Oct 29 04:39:56 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 29 Oct 2014 01:39:56 -0700 (PDT)
Subject: [aerogear-dev] RELEASE: aerogear-parent 0.2.9
In-Reply-To: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>
References: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>
Message-ID: <1414571996929-9670.post@n5.nabble.com>

Hi Matt, 
totally +1, go for it! :-)

Thanks
Andrea


Matthias Wessendorf wrote
> Ahoy!
> 
> I am proposing another release, mainly to pick up new keycloak version
> (1.0.3.Final), which contains several fixes.
> 
> The staging repo is here:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
> 
> Let me know about the release so we can get it out soon, to be on time for
> our UPS release ;-)
> 
> 
> 
> -- 
> Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From abstractj at redhat.com  Wed Oct 29 07:13:38 2014
From: abstractj at redhat.com (Bruno Oliveira)
Date: Wed, 29 Oct 2014 09:13:38 -0200
Subject: [aerogear-dev] Logging on UPS
In-Reply-To: <CAAg5f2QeoDRtHpgXPBSo2s4HrNLV=fhXirWc-QD0fbEzM3VLjw@mail.gmail.com>
References: <20141029034750.GA51740@abstractj.org>
	<CAAg5f2QeoDRtHpgXPBSo2s4HrNLV=fhXirWc-QD0fbEzM3VLjw@mail.gmail.com>
Message-ID: <20141029111338.GB54773@redhat.com>

On 2014-10-29, Matthias Wessendorf wrote:
> On Wed, Oct 29, 2014 at 4:47 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Good morning,
> >
> > In the past we had
> > https://github.com/aerogear/aerogear-unifiedpush-server/pull/149. Any
> > specific reason for not having JBoss Logging or Log4j on UPS?
> >
>
> yeah, there were some arguments against adding another dependency (since
> JUL is part of the Java platform).
> Also, as Burr said (see [1]) "we use it, we own it". That means, at some
> point, we might be less or more the owner (e.g. regarding bugs inside of
> JBoss logging),
> also there cases when the runtime has a different version of JBoss logging
> versus the one in UPS.
>
> All these seamed not to be worth to go that route, in April this year

I totally understand, but I think is the same thing with Java APNS for
example. Also, today, I have no clue about how to audit the logs if
something goes wrong.

Just read WildFly/EAP logs and hope for the best?

>
>
> >
> > With the amount of traffic on UPS, it tends to become more complex to
> > handle
> > log messages/files.
> >
> > Thoughts?
> >
>
> Sure, we can revisit this for the future 1.1.x line of the UnifiedPush
> Server!
>
> -Matthias
>
> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007289.html
>
>
>
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Wed Oct 29 08:27:50 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 29 Oct 2014 13:27:50 +0100
Subject: [aerogear-dev] RELEASE: aerogear-parent 0.2.9
In-Reply-To: <1414571996929-9670.post@n5.nabble.com>
References: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>
	<1414571996929-9670.post@n5.nabble.com>
Message-ID: <CAAg5f2RjFQGQ-sM=gZ9VjDf4QMAPn+L=88PWXe8g9OLux2ZJiA@mail.gmail.com>

Hi,

I am canceling this release - we need to wait for 1.0.4.Final of Keycloak


https://issues.jboss.org/browse/KEYCLOAK-797





On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hi Matt,
> totally +1, go for it! :-)
>
> Thanks
> Andrea
>
>
> Matthias Wessendorf wrote
> > Ahoy!
> >
> > I am proposing another release, mainly to pick up new keycloak version
> > (1.0.3.Final), which contains several fixes.
> >
> > The staging repo is here:
> >
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
> >
> > Let me know about the release so we can get it out soon, to be on time
> for
> > our UPS release ;-)
> >
> >
> >
> > --
> > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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/20141029/59031f26/attachment.html 

From ken at kenfinnigan.me  Wed Oct 29 08:45:06 2014
From: ken at kenfinnigan.me (Ken Finnigan)
Date: Wed, 29 Oct 2014 08:45:06 -0400
Subject: [aerogear-dev] SDKs for LiveOak
In-Reply-To: <CAAg5f2RoDX_TxDTODL_8-KtFBec3TDT_wHBAKaobdwdizL7zyg@mail.gmail.com>
References: <CAKeeVe6yjwLfjRai+0+WwL8OdDZygWn4N3huZ4LS7CRYtyvk0w@mail.gmail.com>
	<CAAg5f2T6OB27-=hrDJWOV+u+HypHiUWNz5xyYnsnCpUbsT_W-g@mail.gmail.com>
	<CAKeeVe4Xw0ysJNnL-AaNBtc7bp=s7UbsJyJK=+rcrnE1kT3r9A@mail.gmail.com>
	<CAAg5f2RoDX_TxDTODL_8-KtFBec3TDT_wHBAKaobdwdizL7zyg@mail.gmail.com>
Message-ID: <CAKeeVe4Gg+t_MErVXvQ1sOONqVYZ2JaffkX78iRYry_VQnft2w@mail.gmail.com>

Thanks for the input Matthias!

Will let you know when we have prototyped something, as we'd appreciate
your input.

Ken

On Wed, Oct 29, 2014 at 2:55 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Perfect!
>
> I think what I'd do is, to pick one platform (e.g. Android) and get a
> feeling for a potential LiveOak SDK.
>
> Our Android 2.0.0 (to continue on this platform for your POC) has been
> split into a few modules, which different repos:
> * https://github.com/aerogear/aerogear-android-core
> * https://github.com/aerogear/aerogear-android-pipe
> * https://github.com/aerogear/aerogear-android-auth
> * https://github.com/aerogear/aerogear-android-authz
> * https://github.com/aerogear/aerogear-android-security
> * https://github.com/aerogear/aerogear-android-store
> * https://github.com/aerogear/aerogear-android-push
>
> If you need more details or have questions on our Android 2.0.0 series, I
> think new, specific mailing list threads are the way go!
>
> Greetings,
> Matthias
>
>
> On Tue, Oct 28, 2014 at 11:25 PM, Ken Finnigan <ken at kenfinnigan.me> wrote:
>
>> Exactly what we're looking for.
>>
>> Just something thin on top of AeroGear that handles any LiveOak specifics
>> like connecting and subscribing to STOMP, and what's needed for the REST
>> calls.
>>
>> On Tue, Oct 28, 2014 at 4:42 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi Ken,
>>>
>>> a while ago, I wrote a little prototype for an iOS SDK for LiveOak:
>>>
>>> https://github.com/matzew/LOKIT
>>>
>>> NOTE: Uses an old/outdated iOS library. For iOS you want our 2.x series,
>>> with swift </note>
>>>
>>> But to give an example:
>>>
>>> That poc was (in the past) running against the chat example:
>>> https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m
>>>
>>> Internally (similar to your web-based demo at that time), it used:
>>> - AeroGear-iOS for http communication
>>> - Stomp-Kit for the Stomp connection
>>>
>>> All behind one thin API (was matching the JS client at that time).
>>>
>>> I think that's the direction you are interested in, right?
>>>
>>> If yes, we can talk about more concrete ideas ;)
>>>
>>> -Matthias
>>>
>>>
>>>
>>> On Tue, Oct 28, 2014 at 9:15 PM, Ken Finnigan <ken at kenfinnigan.me>
>>> wrote:
>>>
>>>> All,
>>>>
>>>> For the next release we're looking to create some SDKs for iOS,
>>>> Android, JavaScript and a Cordova plugin for use with LiveOak.
>>>>
>>>> Our preference is to build on top of what Aerogear has already
>>>> developed, or even simply use the AeroGear SDK's with a different set of
>>>> connection options??
>>>>
>>>> As the AeroGear team are well versed in various issues of developing
>>>> SDKs, I was hoping to get some advice as to the best way for us to develop
>>>> ours such that they're only a very thin layer on top of AeroGear's SDKs.
>>>>
>>>> Thanks in advance!
>>>>
>>>> Ken
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20141029/32ff0cd6/attachment-0001.html 

From bruno at abstractj.org  Wed Oct 29 10:15:37 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 29 Oct 2014 12:15:37 -0200
Subject: [aerogear-dev] Security meeting minutes
Message-ID: <20141029141537.GA63352@abstractj.org>

There we go.

12:14]  <jbott>	 Meeting ended Wed Oct 29 14:13:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[12:14]  <jbott> Minutes:        http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-29-14.00.html
[12:14]  <jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-29-14.00.txt
[12:14]  <jbott> Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-29-14.00.log.html

--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct 29 10:17:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 29 Oct 2014 12:17:32 -0200
Subject: [aerogear-dev] RELEASE: aerogear-parent 0.2.9
In-Reply-To: <CAAg5f2RjFQGQ-sM=gZ9VjDf4QMAPn+L=88PWXe8g9OLux2ZJiA@mail.gmail.com>
References: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>
	<1414571996929-9670.post@n5.nabble.com>
	<CAAg5f2RjFQGQ-sM=gZ9VjDf4QMAPn+L=88PWXe8g9OLux2ZJiA@mail.gmail.com>
Message-ID: <20141029141732.GB63352@abstractj.org>

+1 thanks for the heads up

On 2014-10-29, Matthias Wessendorf wrote:
> Hi,
>
> I am canceling this release - we need to wait for 1.0.4.Final of Keycloak
>
>
> https://issues.jboss.org/browse/KEYCLOAK-797
>
>
>
>
>
> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli <avibelli at redhat.com> wrote:
>
> > Hi Matt,
> > totally +1, go for it! :-)
> >
> > Thanks
> > Andrea
> >
> >
> > Matthias Wessendorf wrote
> > > Ahoy!
> > >
> > > I am proposing another release, mainly to pick up new keycloak version
> > > (1.0.3.Final), which contains several fixes.
> > >
> > > The staging repo is here:
> > >
> > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
> > >
> > > Let me know about the release so we can get it out soon, to be on time
> > for
> > > our UPS release ;-)
> > >
> > >
> > >
> > > --
> > > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct 29 11:46:27 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 29 Oct 2014 13:46:27 -0200
Subject: [aerogear-dev] [UPS] A thought: On MASTER only support WildFly?
In-Reply-To: <1413967257.6296.29.camel@kpiwko-x220>
References: <CAAg5f2Q555Pi6dWQDP_-xc=Zc9wAsvZLRJDeabNdbD2g+J6asA@mail.gmail.com>
	<1413967257.6296.29.camel@kpiwko-x220>
Message-ID: <20141029154627.GA93215@abstractj.org>

Kill it.

On 2014-10-22, Karel Piwko wrote:
> On Wed, 2014-10-22 at 08:43 +0200, Matthias Wessendorf wrote:
> > Hello,
> >
> > as said in the other email thread earlier this week ([1]) there is a bug in
> > the last JBoss AS 7.1 release (see [2]), that basically means the server
> > works properly only on EAP6.x and WildFly.
> >
> > Because of that, I am wondering about removing the -as7 module (see [3]),
> > on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
> > usage reasons.
>
> Sounds reasonable to me if there is an easy way how to backport from -wf
> in 1.1.x (or 2.0.x) to -as7 in 1.0.x in case there is issue that
> potentially affect both wars. Which should be pretty easy looking at
> architecture of UPS ;-).
>
> >
> > What do you guys think?
> >
> > -Matthias
> >
> > [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> > [2] https://issues.jboss.org/browse/AS7-4694
> > [3]
> > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/servers/ups-as7
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct 29 11:54:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 29 Oct 2014 13:54:32 -0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY37gJ=6CAMK9nCT+iHm2obmFpwNmdW6-qnjr4uGojziFgw@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
	<A880182B-A813-4AF7-A656-63ABF6610237@redhat.com>
	<CAEroY37+G3M5HtQEeeK361zofABGbSknrgGBEZfeL2RLBvX9ag@mail.gmail.com>
	<4BF09CAF-5D93-4B6F-A9F0-F83CFCCF0CCF@redhat.com>
	<CAEroY37gJ=6CAMK9nCT+iHm2obmFpwNmdW6-qnjr4uGojziFgw@mail.gmail.com>
Message-ID: <20141029155432.GB93215@abstractj.org>

I'm sorry, I'm late for this train, because was involved into other
stuff.

Like everyone already mentioned into this thread, store messages is
really bad and the major concern is about privacy. You don't want people
sneaking at your push messages.

Unless we implement a OTR model like Pond
(https://pond.imperialviolet.org/) or something like that. I'm -1.

Fire and forget can't guarantee privacy.

On 2014-10-20, Luk?? Fry? wrote:
> I understand the implications,
>
> but are you worried about storing messages per se or rather fact that UPS
> would need to store anything?
>
> Storing messages is required part in case of SimplePush deployment - all
> other networks can be approached as fire&forget.
>
> While up to the point you start to use SImplePush you are free of managing
> custom storage and exposing your storage endpoint to the client, at that
> point you simply have to -> ouch, that hurts.
>
> ---
>
> In case this does not get into UPS, I would suggest at least having
> interceptor on UPS side that would enable extension developers to plug such
> a storage (we are limited by a fact that Push Sender does not know an
> endpoint URL, actually it does not have any connection to Sender at all, so
> there are limited options to connect those two).
>
> Or maybe he can even do that today with JAX-RS interceptors? :-)
>
> On Mon, Oct 20, 2014 at 3:46 PM, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
> >
> > On Oct 20, 2014, at 9:44 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> >
> > Clarification: this was meant as UnifiedPushClient extension, rather then
> > SimplePush's one (bad wording)
> >
> >
> > i think i might still be a no,  because of storing messages
> >
> >
> > On Mon, Oct 20, 2014 at 3:25 PM, Lucas Holmquist <lholmqui at redhat.com>
> > wrote:
> >
> >> I vote no for this.
> >>
> >> I think storing messages, for any period of time is bad.
> >>
> >> I think SimplePush should stay ?Simple? and we should follow the spec on
> >> this.
> >>
> >> On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> >>
> >> I'm just worried about storing the message, for stuff like privacy, for
> >> instance. Let's make a really short TTL or better let's delete the mesage
> >> right after it has been retrieved.
> >>
> >>
> >> On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> >>
> >>> Awesome, great to hear that SimplePush will get a native support for a
> >>> full message content.
> >>>
> >>> As Erik said, in the meantime, we could unify this behavior.
> >>> I have created the associated issue:
> >>> https://issues.jboss.org/browse/AGPUSH-1073
> >>>
> >>>
> >>> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
> >>> wrote:
> >>>
> >>>> Hi Luk??,
> >>>>
> >>>> I like that idea, because in the end our goal is to unify. And I think
> >>>> that the simple push protocol will be changed in the future to allow
> >>>> for ?normal? message sending. So we could fallback afterwards.
> >>>>
> >>>> Cheers,
> >>>> Erik Jan
> >>>>
> >>>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> >>>>
> >>>> Hey guys,
> >>>>
> >>>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
> >>>> as Firefox OS using our Cordova plugin.
> >>>>
> >>>> But as you know, with FFOS it is not that simple - since SimplePush
> >>>> protocol allows to transfer just incremental versions, we are not able to
> >>>> deliver any interesting message.
> >>>>
> >>>> UnifiedPush Server could be a correct place where we unify and shield
> >>>> our users from this limitation:
> >>>>
> >>>>
> >>>> my idea is storing the message on UPS under the SimplePush endpoint
> >>>> URL. Once the message with version reaches the client, he would contact UPS
> >>>> to retrieve this message under a key ( pushEndpoint, version ).
> >>>>
> >>>> The messages could have default built-in TTL to allow periodic cleanup.
> >>>>
> >>>> What do you think?
> >>>>
> >>>>
> >>>> Cheers,
> >>>>
> >>>> ~ Lukas
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Wed Oct 29 11:55:47 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 29 Oct 2014 13:55:47 -0200
Subject: [aerogear-dev] Beyond SimplePush's simplicity
In-Reply-To: <CAEroY34hNYC+QfUkmjFjfc8e1h7v08OW0TAAPvt5Ltru4AudCA@mail.gmail.com>
References: <CAEroY37O27j7M1QY1NQZ79xcmdv2Q4HxyDjc+eKzK3gEt5gANg@mail.gmail.com>
	<1CD35C45-A5B9-4274-85A4-2A968A2DA782@redhat.com>
	<CAEroY35GUy-GWPSq16_gZHfooYAeyofap_qJJX6CY=W+9o5ncA@mail.gmail.com>
	<CAD_dpu0msE4SvoH4S9U=8x6TBAdTMf7mr69mr_BYeDHpWwCGwg@mail.gmail.com>
	<CAEroY34hNYC+QfUkmjFjfc8e1h7v08OW0TAAPvt5Ltru4AudCA@mail.gmail.com>
Message-ID: <20141029155547.GC93215@abstractj.org>

On 2014-10-20, Luk?? Fry? wrote:
> Removing after retrieval was the idea, I ve noted that in the JIRA.
>
> I believe that push messages themselves are not really secure, since you
> hand over each message to third-party without encryption.
> If we leave push message encryption up to app developer, then SimplePush is
> no different, or is it?

If you leave message encryption up to app developer, they won't do it.
And I'm very serious here.

>
> On Mon, Oct 20, 2014 at 2:59 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
> > I'm just worried about storing the message, for stuff like privacy, for
> > instance. Let's make a really short TTL or better let's delete the mesage
> > right after it has been retrieved.
> >
>
> >
> > On Mon, Oct 20, 2014 at 2:51 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> >
> >> Awesome, great to hear that SimplePush will get a native support for a
> >> full message content.
> >>
> >> As Erik said, in the meantime, we could unify this behavior.
> >> I have created the associated issue:
> >> https://issues.jboss.org/browse/AGPUSH-1073
> >>
> >>
> >> On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <edewit at redhat.com>
> >> wrote:
> >>
> >>> Hi Luk??,
> >>>
> >>> I like that idea, because in the end our goal is to unify. And I think
> >>> that the simple push protocol will be changed in the future to allow
> >>> for ?normal? message sending. So we could fallback afterwards.
> >>>
> >>> Cheers,
> >>> Erik Jan
> >>>
> >>> On 20 Oct,2014, at 13:58 , Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> >>>
> >>> Hey guys,
> >>>
> >>> I'm working on a demo of UPS pushing to iOS, Android, Windows, as well
> >>> as Firefox OS using our Cordova plugin.
> >>>
> >>> But as you know, with FFOS it is not that simple - since SimplePush
> >>> protocol allows to transfer just incremental versions, we are not able to
> >>> deliver any interesting message.
> >>>
> >>> UnifiedPush Server could be a correct place where we unify and shield
> >>> our users from this limitation:
> >>>
> >>>
> >>> my idea is storing the message on UPS under the SimplePush endpoint URL.
> >>> Once the message with version reaches the client, he would contact UPS to
> >>> retrieve this message under a key ( pushEndpoint, version ).
> >>>
> >>> The messages could have default built-in TTL to allow periodic cleanup.
> >>>
> >>> What do you think?
> >>>
> >>>
> >>> Cheers,
> >>>
> >>> ~ Lukas
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

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


--

abstractj
PGP: 0x84DC9914

From lholmqui at redhat.com  Wed Oct 29 13:48:02 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Wed, 29 Oct 2014 13:48:02 -0400
Subject: [aerogear-dev] external config for senders ?
In-Reply-To: <5B13B270-B280-46B2-9A68-D41A5CEF9648@redhat.com>
References: <CAAg5f2SR+OwJnsbbJo73MpJQYLJaYZ6J4FCABbxp_fsNf9nGgQ@mail.gmail.com>
	<C2FFC0EB-B3F2-4CB1-9E05-7264C57B7BB3@redhat.com>
	<CAAg5f2RZkNxvAEq6AWZnRuYHOsrM--vuyGyQg9qGP=qCJFrN3g@mail.gmail.com>
	<4E257F32-880D-4BC7-9F55-FBED536E2FF9@redhat.com>
	<CAAg5f2Rdo8Rt+JyRSHcouePb-sJpvB-MRTZ0D0z_-W7y=r=fiw@mail.gmail.com>
	<5B13B270-B280-46B2-9A68-D41A5CEF9648@redhat.com>
Message-ID: <45405CAF-0A49-4D66-BC10-D1C8D1C59B4F@redhat.com>


> On Oct 28, 2014, at 11:00 AM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
>> 
>> On Oct 28, 2014, at 10:54 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> 
>> 
>> On Tue, Oct 28, 2014 at 3:48 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> technically, a user can already load the settings from an external config,
>> 
>> so, it's just a matter of updating the demo and 'document' it ? 
> 
> yea,  pretty much

i made some slight modifications to the node sender,  https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/11 <https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/11>

basically,  the constructor was only taking in the url of the UPS.  I changed this so you now pass in an Object with the url, applicationId, and masterSecret (which can be loaded from an external config file).

this makes the ?send??s options now optional.

see the update example in the PR to see the change

> 
>>  
>> 
>>> On Oct 28, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>> 
>>> 
>>> 
>>> On Tue, Oct 28, 2014 at 3:36 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>>> 
>>>> On Oct 28, 2014, at 10:31 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> on the Cordova 1.0.2 push plugin, we now have the handy option to configure the server settings in an external JSON file.
>>>> 
>>>> 
>>>> A few days we spoke about this for the senders as well. Now, after a few days, I am wondering, does it make sense to have an external configuration file for our node.js/java senders ? 
>>> 
>>> for the node sender, this would be a nice thing, loading it should be as easy as  ?require(?external_config.json')"
>>> 
>>> 
>>> oh, that sounds quick :) sounds reasonable to do for next release ;-)
>>>  
>>> 
>>>> 
>>>> -Matthias
>>>> 
>>>> -- 
>>>> Matthias Wessendorf 
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>>> twitter: http://twitter.com/mwessendorf <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 <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>
>>> 
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>> twitter: http://twitter.com/mwessendorf <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 <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>
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141029/8ec6a4a2/attachment-0001.html 

From lholmqui at redhat.com  Wed Oct 29 14:16:21 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Wed, 29 Oct 2014 14:16:21 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
	<D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
Message-ID: <9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>

i?ve created a safari-push branch on my fork of the open shift cartridge, 

https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push <https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push>


i?ve been trying to create an app with it but haven?t been successful,  perhaps something i?m doing,  anyone mind giving it a try
> On Oct 28, 2014, at 3:35 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
> 
> The branch on the main repo  https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push <https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push>
> 
> subsequent PR?s will target this one
> 
>> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> 
>> Here is the initial addition in one of my branches:  https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push <https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push>
>>> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>> 
>>> 
>>> 
>>> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>>> 
>>>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com <mailto:edewit at redhat.com>> wrote:
>>>> 
>>>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>>>> 
>>>>> 
>>>>> So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>
>>>>> 
>>>>> but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 
>>>> 
>>>> Right now a sender is configured to send notifications for one specific variant type, this mapping is configured on the top of the class:
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40>
>>>> 
>>>> so APNsPushNotificationSender will only be use for iOSVariant variants, so either we change the way this works or you create a new Sender ( that extends this one maybe )
>>> 
>>> I think i?ll just create a new sender of now just to get something working since the SafariVariant and iOSVariant will be combined into an APNsVariant in the near future.
>>> 
>>> sounds reasonable on getting this started
>>> 
>>> -M 
>>> 
>>> 
>>> 
>>>> 
>>>> Cheers,
>>>> 	Erik Jan
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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>
>>> 
>>> _______________________________________________
>>> 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>
>>> 
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>> twitter: http://twitter.com/mwessendorf <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 <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
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141029/7bacc7ad/attachment.html 

From matzew at apache.org  Wed Oct 29 17:01:25 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 29 Oct 2014 22:01:25 +0100
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
	<D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
	<9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>
Message-ID: <CAAg5f2SWJX1imhdjX6gVn8Os5_E+WVt6afGXogPBiSnOL2Ewrg@mail.gmail.com>

any log from rhc client?

On Wednesday, October 29, 2014, Lucas Holmquist <lholmqui at redhat.com> wrote:

> i?ve created a safari-push branch on my fork of the open shift cartridge,
>
>
> https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push
>
>
> i?ve been trying to create an app with it but haven?t been successful,
>  perhaps something i?m doing,  anyone mind giving it a try
>
> On Oct 28, 2014, at 3:35 PM, Lucas Holmquist <lholmqui at redhat.com
> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>
>
> The branch on the main repo
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push
>
> subsequent PR?s will target this one
>
> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com
> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>
> Here is the initial addition in one of my branches:
> https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push
>
> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>
>
> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com
> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>
>>
>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com
>> <javascript:_e(%7B%7D,'cvml','edewit at redhat.com');>> wrote:
>>
>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com
>> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>>
>>
>> So i?ve run into a bit of a problem, I?m trying to send notifications,
>>  using
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52
>>
>> but i?m not sure how to also tell it to use the new SafarVariant.class
>> that i?ve created.
>>
>>
>> Right now a sender is configured to send notifications for one specific
>> variant type, this mapping is configured on the top of the class:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40
>>
>> so APNsPushNotificationSender will only be use for iOSVariant variants,
>> so either we change the way this works or you create a new Sender ( that
>> extends this one maybe )
>>
>>
>> I think i?ll just create a new sender of now just to get something
>> working since the SafariVariant and iOSVariant will be combined into an
>> APNsVariant in the near future.
>>
>
> sounds reasonable on getting this started
>
> -M
>
>>
>>
>>
>>
>> Cheers,
>> Erik Jan
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://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:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141029/93f0eaf2/attachment-0001.html 

From supittma at redhat.com  Wed Oct 29 23:10:38 2014
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 29 Oct 2014 23:10:38 -0400
Subject: [aerogear-dev] RELEASE: aerogear-parent 0.2.9
In-Reply-To: <CAAg5f2RjFQGQ-sM=gZ9VjDf4QMAPn+L=88PWXe8g9OLux2ZJiA@mail.gmail.com>
References: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>	<1414571996929-9670.post@n5.nabble.com>
	<CAAg5f2RjFQGQ-sM=gZ9VjDf4QMAPn+L=88PWXe8g9OLux2ZJiA@mail.gmail.com>
Message-ID: <5451AC2E.9000905@redhat.com>

On 10/29/2014 08:27 AM, Matthias Wessendorf wrote:
> Hi,
>
> I am canceling this release - we need to wait for 1.0.4.Final of Keycloak
But I was already wearing my release pants!

>
>
> https://issues.jboss.org/browse/KEYCLOAK-797
>
>
>
>
>
> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli <avibelli at redhat.com 
> <mailto:avibelli at redhat.com>> wrote:
>
>     Hi Matt,
>     totally +1, go for it! :-)
>
>     Thanks
>     Andrea
>
>
>     Matthias Wessendorf wrote
>     > Ahoy!
>     >
>     > I am proposing another release, mainly to pick up new keycloak
>     version
>     > (1.0.3.Final), which contains several fixes.
>     >
>     > The staging repo is here:
>     >
>     https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
>     >
>     > Let me know about the release so we can get it out soon, to be
>     on time for
>     > our UPS release ;-)
>     >
>     >
>     >
>     > --
>     > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.html
>     Sent from the aerogear-dev mailing list archive at Nabble.com.
>     _______________________________________________
>     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


-- 
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/20141029/2372e1eb/attachment.html 

From matzew at apache.org  Thu Oct 30 01:53:49 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 06:53:49 +0100
Subject: [aerogear-dev] RELEASE: aerogear-parent 0.2.9
In-Reply-To: <5451AC2E.9000905@redhat.com>
References: <CAAg5f2StpmUC7y2zj62nO6u1s-CnKBhTGAYdduuNF_WYosbR9Q@mail.gmail.com>
	<1414571996929-9670.post@n5.nabble.com>
	<CAAg5f2RjFQGQ-sM=gZ9VjDf4QMAPn+L=88PWXe8g9OLux2ZJiA@mail.gmail.com>
	<5451AC2E.9000905@redhat.com>
Message-ID: <CAAg5f2QCYHCZE5D0pFxgoy5VNSRtrpkbkVtkmiSaJ7iYZn5Ymw@mail.gmail.com>

fancy pants! keep em around - the party starts soon :)

On Thu, Oct 30, 2014 at 4:10 AM, Summers Pittman <supittma at redhat.com>
wrote:

>  On 10/29/2014 08:27 AM, Matthias Wessendorf wrote:
>
> Hi,
>
>  I am canceling this release - we need to wait for 1.0.4.Final of Keycloak
>
> But I was already wearing my release pants!
>
>
>
>
>  https://issues.jboss.org/browse/KEYCLOAK-797
>
>
>
>
>
> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli <avibelli at redhat.com>
> wrote:
>
>> Hi Matt,
>> totally +1, go for it! :-)
>>
>> Thanks
>> Andrea
>>
>>
>> Matthias Wessendorf wrote
>>  > Ahoy!
>> >
>> > I am proposing another release, mainly to pick up new keycloak version
>> > (1.0.3.Final), which contains several fixes.
>> >
>> > The staging repo is here:
>> >
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
>> >
>> > Let me know about the release so we can get it out soon, to be on time
>> for
>> > our UPS release ;-)
>> >
>> >
>> >
>> > --
>> > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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 listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 30 02:47:45 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 07:47:45 +0100
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2SWJX1imhdjX6gVn8Os5_E+WVt6afGXogPBiSnOL2Ewrg@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
	<D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
	<9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>
	<CAAg5f2SWJX1imhdjX6gVn8Os5_E+WVt6afGXogPBiSnOL2Ewrg@mail.gmail.com>
Message-ID: <CAAg5f2TCarNpNvGYv_5=097r+KcqjpKFDfT5ZhXejXEwSPZZqg@mail.gmail.com>

Here is what I did, on command line:
rhc app create --no-git safari "
https://cartreflect-claytondev.rhcloud.com/reflect?github=lholmquist/openshift-origin-cartridge-aerogear-push-wildfly&commit=086fe4f75f8991e7780c9df078c7371377c68aa2
"



One the console, I am getting:
Creating application 'safari' ... Server returned an unexpected error code:
504




but.... well, here is the server ->
https://safari-pushee.rhcloud.com/ag-push



What I do not understand it the 504 :)





On Wed, Oct 29, 2014 at 10:01 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> any log from rhc client?
>
>
> On Wednesday, October 29, 2014, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
>> i?ve created a safari-push branch on my fork of the open shift cartridge,
>>
>>
>> https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push
>>
>>
>> i?ve been trying to create an app with it but haven?t been successful,
>>  perhaps something i?m doing,  anyone mind giving it a try
>>
>> On Oct 28, 2014, at 3:35 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>>
>>
>> The branch on the main repo
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push
>>
>> subsequent PR?s will target this one
>>
>> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>>
>> Here is the initial addition in one of my branches:
>> https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push
>>
>> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>
>>
>> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>
>>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>
>>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com> wrote:
>>>
>>>
>>> So i?ve run into a bit of a problem, I?m trying to send notifications,
>>>  using
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52
>>>
>>> but i?m not sure how to also tell it to use the new SafarVariant.class
>>> that i?ve created.
>>>
>>>
>>> Right now a sender is configured to send notifications for one specific
>>> variant type, this mapping is configured on the top of the class:
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40
>>>
>>> so APNsPushNotificationSender will only be use for iOSVariant variants,
>>> so either we change the way this works or you create a new Sender ( that
>>> extends this one maybe )
>>>
>>>
>>> I think i?ll just create a new sender of now just to get something
>>> working since the SafariVariant and iOSVariant will be combined into an
>>> APNsVariant in the near future.
>>>
>>
>> sounds reasonable on getting this started
>>
>> -M
>>
>>>
>>>
>>>
>>>
>>> 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
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20141030/b5c5229e/attachment-0001.html 

From matzew at apache.org  Thu Oct 30 02:48:59 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 07:48:59 +0100
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2TCarNpNvGYv_5=097r+KcqjpKFDfT5ZhXejXEwSPZZqg@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
	<D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
	<9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>
	<CAAg5f2SWJX1imhdjX6gVn8Os5_E+WVt6afGXogPBiSnOL2Ewrg@mail.gmail.com>
	<CAAg5f2TCarNpNvGYv_5=097r+KcqjpKFDfT5ZhXejXEwSPZZqg@mail.gmail.com>
Message-ID: <CAAg5f2TVRuMEhq0V3kMTx6bwYtstEKL-GHXbV9LkF431CJx8vw@mail.gmail.com>

hahaha, than it disappeared ??? :-)

looks like the 'delete' was triggered by the 504 ?

On Thu, Oct 30, 2014 at 7:47 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Here is what I did, on command line:
> rhc app create --no-git safari "
> https://cartreflect-claytondev.rhcloud.com/reflect?github=lholmquist/openshift-origin-cartridge-aerogear-push-wildfly&commit=086fe4f75f8991e7780c9df078c7371377c68aa2
> "
>
>
>
> One the console, I am getting:
> Creating application 'safari' ... Server returned an unexpected error
> code: 504
>
>
>
>
> but.... well, here is the server ->
> https://safari-pushee.rhcloud.com/ag-push
>
>
>
> What I do not understand it the 504 :)
>
>
>
>
>
> On Wed, Oct 29, 2014 at 10:01 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> any log from rhc client?
>>
>>
>> On Wednesday, October 29, 2014, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> i?ve created a safari-push branch on my fork of the open shift
>>> cartridge,
>>>
>>>
>>> https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push
>>>
>>>
>>> i?ve been trying to create an app with it but haven?t been successful,
>>>  perhaps something i?m doing,  anyone mind giving it a try
>>>
>>> On Oct 28, 2014, at 3:35 PM, Lucas Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>
>>> The branch on the main repo
>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push
>>>
>>> subsequent PR?s will target this one
>>>
>>> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>> Here is the initial addition in one of my branches:
>>> https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push
>>>
>>> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>
>>>
>>> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>>
>>>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>>
>>>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com> wrote:
>>>>
>>>>
>>>> So i?ve run into a bit of a problem, I?m trying to send notifications,
>>>>  using
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52
>>>>
>>>> but i?m not sure how to also tell it to use the new SafarVariant.class
>>>> that i?ve created.
>>>>
>>>>
>>>> Right now a sender is configured to send notifications for one specific
>>>> variant type, this mapping is configured on the top of the class:
>>>>
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40
>>>>
>>>> so APNsPushNotificationSender will only be use for iOSVariant variants,
>>>> so either we change the way this works or you create a new Sender ( that
>>>> extends this one maybe )
>>>>
>>>>
>>>> I think i?ll just create a new sender of now just to get something
>>>> working since the SafariVariant and iOSVariant will be combined into an
>>>> APNsVariant in the near future.
>>>>
>>>
>>> sounds reasonable on getting this started
>>>
>>> -M
>>>
>>>>
>>>>
>>>>
>>>>
>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.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
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 30 02:57:36 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 07:57:36 +0100
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2TVRuMEhq0V3kMTx6bwYtstEKL-GHXbV9LkF431CJx8vw@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
	<D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
	<9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>
	<CAAg5f2SWJX1imhdjX6gVn8Os5_E+WVt6afGXogPBiSnOL2Ewrg@mail.gmail.com>
	<CAAg5f2TCarNpNvGYv_5=097r+KcqjpKFDfT5ZhXejXEwSPZZqg@mail.gmail.com>
	<CAAg5f2TVRuMEhq0V3kMTx6bwYtstEKL-GHXbV9LkF431CJx8vw@mail.gmail.com>
Message-ID: <CAAg5f2Q9nJcq=jOxZ3t-kgdeSnWjhpSokJaBkyLjyB8XTV6Ghg@mail.gmail.com>

I tried the same, again with -d (rhc -d), that worked fine....


hrm...

On Thu, Oct 30, 2014 at 7:48 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> hahaha, than it disappeared ??? :-)
>
> looks like the 'delete' was triggered by the 504 ?
>
> On Thu, Oct 30, 2014 at 7:47 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Here is what I did, on command line:
>> rhc app create --no-git safari "
>> https://cartreflect-claytondev.rhcloud.com/reflect?github=lholmquist/openshift-origin-cartridge-aerogear-push-wildfly&commit=086fe4f75f8991e7780c9df078c7371377c68aa2
>> "
>>
>>
>>
>> One the console, I am getting:
>> Creating application 'safari' ... Server returned an unexpected error
>> code: 504
>>
>>
>>
>>
>> but.... well, here is the server ->
>> https://safari-pushee.rhcloud.com/ag-push
>>
>>
>>
>> What I do not understand it the 504 :)
>>
>>
>>
>>
>>
>> On Wed, Oct 29, 2014 at 10:01 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> any log from rhc client?
>>>
>>>
>>> On Wednesday, October 29, 2014, Lucas Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> i?ve created a safari-push branch on my fork of the open shift
>>>> cartridge,
>>>>
>>>>
>>>> https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push
>>>>
>>>>
>>>> i?ve been trying to create an app with it but haven?t been successful,
>>>>  perhaps something i?m doing,  anyone mind giving it a try
>>>>
>>>> On Oct 28, 2014, at 3:35 PM, Lucas Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>
>>>> The branch on the main repo
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push
>>>>
>>>> subsequent PR?s will target this one
>>>>
>>>> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>> Here is the initial addition in one of my branches:
>>>> https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push
>>>>
>>>> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com>
>>>>> wrote:
>>>>>
>>>>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>> So i?ve run into a bit of a problem, I?m trying to send notifications,
>>>>>  using
>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52
>>>>>
>>>>> but i?m not sure how to also tell it to use the new SafarVariant.class
>>>>> that i?ve created.
>>>>>
>>>>>
>>>>> Right now a sender is configured to send notifications for one
>>>>> specific variant type, this mapping is configured on the top of the class:
>>>>>
>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40
>>>>>
>>>>> so APNsPushNotificationSender will only be use for iOSVariant variants,
>>>>> so either we change the way this works or you create a new Sender ( that
>>>>> extends this one maybe )
>>>>>
>>>>>
>>>>> I think i?ll just create a new sender of now just to get something
>>>>> working since the SafariVariant and iOSVariant will be combined into an
>>>>> APNsVariant in the near future.
>>>>>
>>>>
>>>> sounds reasonable on getting this started
>>>>
>>>> -M
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.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
>>
>
>
>
> --
> 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/20141030/5cd2b7b8/attachment-0001.html 

From michael.yates at abc.net.au  Thu Oct 30 08:16:56 2014
From: michael.yates at abc.net.au (michael)
Date: Thu, 30 Oct 2014 05:16:56 -0700 (PDT)
Subject: [aerogear-dev] Large user base with Aerogear Unified Push
Message-ID: <1414671416154-9687.post@n5.nabble.com>

All,
We have been evaluating Aerogear Unified Push and things are going well so
far.
But up until now we have only had a small numbers of users (in the tens)
registering or requiring a push.

We are looking at adding push functionality into one of our core products.
Last time we did a major revision to our core product we had in the order of
half a million users upgrade to the new version in the first 24 hours.
Unfortunately I don't have stats to hand on the busiest hour during that
period.

If we add push to our Android and iOS versions of our application and a
large proportion of our users accept the new permission in app we could be
looking at hundreds of thousands of registrations in a day and tens of
thousands in an hour. Note that we are not migrating from another provider
so this will be a "cold start".

So my questions are:
- Has anyone used Aerogear at this sort of scale? (happy to talk out of band
if you don't want to put your name out in a forum)
- What is the best deployment architecture to go for in this case? 
- Similar to the above question - will Aerogear work nicely behind a load
balancer?
- If there are multiple instances of the app running can it take advantage
of read slaves if DB is a bottle neck?
- Has anyone done any sizing or transaction rates against AWS instances?
- Do any of the database back ends perform better or worse for this sort of
on boarding?

Obviously once we get all of our users on we will want to push them some
messages. So has anyone done pushes to hundreds of thousands of users using
Aerogear? What was the approximate time from the start to the end of the
process?

Note I've read JIRA and haven't seen much related to scalability except
- https://issues.jboss.org/browse/AGPUSH-661 from 
http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007793.html

I also note with interest that dealing with pushing messages at scale isn't
without its challenges
-
http://stackoverflow.com/questions/16352131/apple-push-notifications-in-bulk

Any help greatly appreciated.

Regards,
Michael

PS - Assuming we do go with Aerogear we will happily write up our findings
on how it ended up ;)


 



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Large-user-base-with-Aerogear-Unified-Push-tp9687.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From lholmqui at redhat.com  Thu Oct 30 09:13:50 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 30 Oct 2014 09:13:50 -0400
Subject: [aerogear-dev] Safari Push notifications
In-Reply-To: <CAAg5f2Q9nJcq=jOxZ3t-kgdeSnWjhpSokJaBkyLjyB8XTV6Ghg@mail.gmail.com>
References: <AD61E0FB-57B8-4C83-B144-AACD77DFC50D@redhat.com>
	<CAAg5f2QmASTT-miL4HQtfrv0_ZNjcvAonWzXzrzVBEFTZdff+w@mail.gmail.com>
	<FD5BBEF7-C3ED-4933-81B2-3243503607DE@redhat.com>
	<CAAg5f2S63PchG8WwEbyC2XoF2kJ8fmnqVGVz=Q1aULm-CbRCoQ@mail.gmail.com>
	<0F0A5DAF-9D0C-47B4-B402-7975C902ABCA@redhat.com>
	<FF5DABF9-BDB7-4F2F-9E7E-182092A994F6@redhat.com>
	<2371EC83-66F8-430C-A35D-E5F58F08119B@redhat.com>
	<CAAg5f2R-UzfQqysSirRw2ELKAfJD4muh_CW4e00KrWo1arwbEw@mail.gmail.com>
	<6B8B19DF-C401-4628-872C-91085A5BD704@redhat.com>
	<D5EB95CF-F366-4D24-9439-58193A7D60C3@redhat.com>
	<9D9CF372-9731-4F59-8055-2F0F4F076014@redhat.com>
	<CAAg5f2SWJX1imhdjX6gVn8Os5_E+WVt6afGXogPBiSnOL2Ewrg@mail.gmail.com>
	<CAAg5f2TCarNpNvGYv_5=097r+KcqjpKFDfT5ZhXejXEwSPZZqg@mail.gmail.com>
	<CAAg5f2TVRuMEhq0V3kMTx6bwYtstEKL-GHXbV9LkF431CJx8vw@mail.gmail.com>
	<CAAg5f2Q9nJcq=jOxZ3t-kgdeSnWjhpSokJaBkyLjyB8XTV6Ghg@mail.gmail.com>
Message-ID: <DAF547B8-300A-4497-8472-0057162EE203@redhat.com>

hmm, indeed,  let me try that also
> On Oct 30, 2014, at 2:57 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> I tried the same, again with -d (rhc -d), that worked fine....
> 
> 
> hrm...
> 
> On Thu, Oct 30, 2014 at 7:48 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> hahaha, than it disappeared ??? :-) 
> 
> looks like the 'delete' was triggered by the 504 ? 
> 
> On Thu, Oct 30, 2014 at 7:47 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> Here is what I did, on command line:
> rhc app create --no-git safari "https://cartreflect-claytondev.rhcloud.com/reflect?github=lholmquist/openshift-origin-cartridge-aerogear-push-wildfly&commit=086fe4f75f8991e7780c9df078c7371377c68aa2 <https://cartreflect-claytondev.rhcloud.com/reflect?github=lholmquist/openshift-origin-cartridge-aerogear-push-wildfly&commit=086fe4f75f8991e7780c9df078c7371377c68aa2>"
> 
> 
> 
> One the console, I am getting:
> Creating application 'safari' ... Server returned an unexpected error code: 504
> 
> 
> 
> 
> but.... well, here is the server -> https://safari-pushee.rhcloud.com/ag-push <https://safari-pushee.rhcloud.com/ag-push>
> 
> 
> 
> What I do not understand it the 504 :) 
> 
> 
> 
> 
> 
> On Wed, Oct 29, 2014 at 10:01 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> any log from rhc client?
> 
> 
> On Wednesday, October 29, 2014, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> i?ve created a safari-push branch on my fork of the open shift cartridge, 
> 
> https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push <https://github.com/lholmquist/openshift-origin-cartridge-aerogear-push-wildfly/tree/safari-push>
> 
> 
> i?ve been trying to create an app with it but haven?t been successful,  perhaps something i?m doing,  anyone mind giving it a try
>> On Oct 28, 2014, at 3:35 PM, Lucas Holmquist <lholmqui at redhat.com <>> wrote:
>> 
>> 
>> The branch on the main repo  https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push <https://github.com/aerogear/aerogear-unifiedpush-server/tree/safari-push>
>> 
>> subsequent PR?s will target this one
>> 
>>> On Oct 28, 2014, at 3:21 PM, Lucas Holmquist <lholmqui at redhat.com <>> wrote:
>>> 
>>> Here is the initial addition in one of my branches:  https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push <https://github.com/lholmquist/aerogear-unified-push-server/tree/safari-push>
>>>> On Oct 27, 2014, at 9:42 AM, Matthias Wessendorf <matzew at apache.org <>> wrote:
>>>> 
>>>> 
>>>> 
>>>> On Mon, Oct 27, 2014 at 2:28 PM, Lucas Holmquist <lholmqui at redhat.com <>> wrote:
>>>> 
>>>>> On Oct 27, 2014, at 9:20 AM, Erik Jan de Wit <edewit at redhat.com <>> wrote:
>>>>> 
>>>>> On 27 Oct,2014, at 14:15 , Lucas Holmquist <lholmqui at redhat.com <>> wrote:
>>>>> 
>>>>>> 
>>>>>> So i?ve run into a bit of a problem, I?m trying to send notifications,  using https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L52>
>>>>>> 
>>>>>> but i?m not sure how to also tell it to use the new SafarVariant.class that i?ve created. 
>>>>> 
>>>>> Right now a sender is configured to send notifications for one specific variant type, this mapping is configured on the top of the class:
>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40 <https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L40>
>>>>> 
>>>>> so APNsPushNotificationSender will only be use for iOSVariant variants, so either we change the way this works or you create a new Sender ( that extends this one maybe )
>>>> 
>>>> I think i?ll just create a new sender of now just to get something working since the SafariVariant and iOSVariant will be combined into an APNsVariant in the near future.
>>>> 
>>>> sounds reasonable on getting this started
>>>> 
>>>> -M 
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> Cheers,
>>>>> 	Erik Jan
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> 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 <>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Matthias Wessendorf 
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>>> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>_______________________________________________
>>>> aerogear-dev mailing list
>>>> 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 <>
>>> 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 <>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> 
> -- 
> Sent from Gmail Mobile
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141030/968824c7/attachment-0001.html 

From matzew at apache.org  Thu Oct 30 09:41:28 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 14:41:28 +0100
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re:  OAuth2,
 OpenID connect and AeroGear)
Message-ID: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>

Hello team!

On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js.


Great point on being compatible with passport.js! To ensure our OAuth2
client SDKs do work against node.js (w/ passport.js), how about we build a
Node.js based version of our "Shoot-n-Share backend" ([1]), that is
protected by Passport.js?

It could be a (simple) a 'clone' of our java version. I think for Luke, our
Node.js pro, it would be a fairly simple task :)

On the client side, the Android/iOS versions of Shoot-n-Share would simply
offer a new upload target for Passport.js, instead of 'just' FB,
Google-Drive and Keycloak.

That way we will also learn how much Passport.js is actually different,
similar to what we learned on how Google/FB are different ;-)

Another interesting aspect of this is that, once we are ready to release
our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo
as well, instead of just a Java-based backend demo. That would clearly
show, our client libs are working across different backend technologies.

Any thoughts?

-Matthias


[1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot




> In the end, OAuth2 is just a protocol and
> should support other servers.
>
> - Should we provide examples for OpenID connect? Or abstractions?
>
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
>
>
> [1] -
>
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>
> [3] - https://issues.jboss.org/browse/AGSEC-180
>
> [4] - https://issues.jboss.org/browse/AGSEC-190
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From matzew at apache.org  Thu Oct 30 09:58:00 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 14:58:00 +0100
Subject: [aerogear-dev] Large user base with Aerogear Unified Push
In-Reply-To: <1414671416154-9687.post@n5.nabble.com>
References: <1414671416154-9687.post@n5.nabble.com>
Message-ID: <CAAg5f2RaoGwTUY_2OTKQZcWhxcDwieRuwrKH2RdPqEMPFxMNHw@mail.gmail.com>

Hi Michael,

thanks for the interest in AeroGear and our UnifiedPush Server!

On Thu, Oct 30, 2014 at 1:16 PM, michael <michael.yates at abc.net.au> wrote:

> All,
> We have been evaluating Aerogear Unified Push and things are going well so
> far.
> But up until now we have only had a small numbers of users (in the tens)
> registering or requiring a push.
>
> We are looking at adding push functionality into one of our core products.
> Last time we did a major revision to our core product we had in the order
> of
> half a million users upgrade to the new version in the first 24 hours.
> Unfortunately I don't have stats to hand on the busiest hour during that
> period.
>
> If we add push to our Android and iOS versions of our application and a
> large proportion of our users accept the new permission in app we could be
> looking at hundreds of thousands of registrations in a day and tens of
> thousands in an hour. Note that we are not migrating from another provider
> so this will be a "cold start".
>
> So my questions are:
> - Has anyone used Aerogear at this sort of scale? (happy to talk out of
> band
> if you don't want to put your name out in a forum)
>

not that we know of. We know about a few users, but we don't know their
app/device numbers.


> - What is the best deployment architecture to go for in this case?
>

I'd recommend using latest greatest on WildFly8.x


> - Similar to the above question - will Aerogear work nicely behind a load
> balancer?
>

we know of usage behind nginx


> - If there are multiple instances of the app running can it take advantage
> of read slaves if DB is a bottle neck?
>

yes, that would help


> - Has anyone done any sizing or transaction rates against AWS instances?
>

nope


> - Do any of the database back ends perform better or worse for this sort of
> on boarding?
>

we have support for Postgres and MySQL.


>
> Obviously once we get all of our users on we will want to push them some
> messages. So has anyone done pushes to hundreds of thousands of users using
> Aerogear?


we don't know exact number of our users installation base.


> What was the approximate time from the start to the end of the
> process?
>
> Note I've read JIRA and haven't seen much related to scalability except
> - https://issues.jboss.org/browse/AGPUSH-661 from
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007793.html


in our testing https://issues.jboss.org/browse/AGPUSH-999 came up.
This should reduce some perf. issues; More to details come!


>
>
> I also note with interest that dealing with pushing messages at scale isn't
> without its challenges
> -
>
> http://stackoverflow.com/questions/16352131/apple-push-notifications-in-bulk


For APNs we use java-apns, which is used by major companies as well.


>
>
> Any help greatly appreciated.
>
> Regards,
> Michael
>
> PS - Assuming we do go with Aerogear we will happily write up our findings
> on how it ended up ;)
>

sweet!


>
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Large-user-base-with-Aerogear-Unified-Push-tp9687.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/20141030/e9e26c6e/attachment.html 

From matzew at apache.org  Thu Oct 30 10:48:51 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 15:48:51 +0100
Subject: [aerogear-dev] RELEASE: next try of aerogear-parent 0.2.9 release
Message-ID: <CAAg5f2Rj7bkHbNip+oZ7xQ6Z_XBbrSaW=tbPNBUK=MCr1KRXTg@mail.gmail.com>

Hi,

KC 1.0.4 hit maven central, and the version has been integrated in our
parent pom.

main reason for this release is in fact the new KC version.

The staging repo is here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4137/

Let me know about the release so we can get it out soon, to be on time for
our UPS release ;-)

Cheers,
Matthias




On Wed, Oct 29, 2014 at 1:27 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I am canceling this release - we need to wait for 1.0.4.Final of Keycloak
>
>
> https://issues.jboss.org/browse/KEYCLOAK-797
>
>
>
>
>
> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli <avibelli at redhat.com>
> wrote:
>
>> Hi Matt,
>> totally +1, go for it! :-)
>>
>> Thanks
>> Andrea
>>
>>
>> Matthias Wessendorf wrote
>> > Ahoy!
>> >
>> > I am proposing another release, mainly to pick up new keycloak version
>> > (1.0.3.Final), which contains several fixes.
>> >
>> > The staging repo is here:
>> >
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
>> >
>> > Let me know about the release so we can get it out soon, to be on time
>> for
>> > our UPS release ;-)
>> >
>> >
>> >
>> > --
>> > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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/20141030/6ab9436f/attachment.html 

From avibelli at redhat.com  Thu Oct 30 10:55:00 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Thu, 30 Oct 2014 07:55:00 -0700 (PDT)
Subject: [aerogear-dev] RELEASE: next try of aerogear-parent 0.2.9
 release
In-Reply-To: <CAAg5f2Rj7bkHbNip+oZ7xQ6Z_XBbrSaW=tbPNBUK=MCr1KRXTg@mail.gmail.com>
References: <CAAg5f2Rj7bkHbNip+oZ7xQ6Z_XBbrSaW=tbPNBUK=MCr1KRXTg@mail.gmail.com>
Message-ID: <1414680900579-9692.post@n5.nabble.com>

+1 go go go!! :-)

Thanks
Andrea


Matthias Wessendorf wrote
> Hi,
> 
> KC 1.0.4 hit maven central, and the version has been integrated in our
> parent pom.
> 
> main reason for this release is in fact the new KC version.
> 
> The staging repo is here:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4137/
> 
> Let me know about the release so we can get it out soon, to be on time for
> our UPS release ;-)
> 
> Cheers,
> Matthias
> 
> 
> 
> 
> On Wed, Oct 29, 2014 at 1:27 PM, Matthias Wessendorf &lt;

> matzew@

> &gt;
> wrote:
> 
>> Hi,
>>
>> I am canceling this release - we need to wait for 1.0.4.Final of Keycloak
>>
>>
>> https://issues.jboss.org/browse/KEYCLOAK-797
>>
>>
>>
>>
>>
>> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli &lt;

> avibelli@

> &gt;
>> wrote:
>>
>>> Hi Matt,
>>> totally +1, go for it! :-)
>>>
>>> Thanks
>>> Andrea
>>>
>>>
>>> Matthias Wessendorf wrote
>>> > Ahoy!
>>> >
>>> > I am proposing another release, mainly to pick up new keycloak version
>>> > (1.0.3.Final), which contains several fixes.
>>> >
>>> > The staging repo is here:
>>> >
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
>>> >
>>> > Let me know about the release so we can get it out soon, to be on time
>>> for
>>> > our UPS release ;-)
>>> >
>>> >
>>> >
>>> > --
>>> > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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
>>
> 
> 
> 
> -- 
> Matthias 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-RELEASE-next-try-of-aerogear-parent-0-2-9-release-tp9691p9692.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Thu Oct 30 12:50:45 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 30 Oct 2014 17:50:45 +0100
Subject: [aerogear-dev] RELEASE: next try of aerogear-parent 0.2.9
	release
In-Reply-To: <1414680900579-9692.post@n5.nabble.com>
References: <CAAg5f2Rj7bkHbNip+oZ7xQ6Z_XBbrSaW=tbPNBUK=MCr1KRXTg@mail.gmail.com>
	<1414680900579-9692.post@n5.nabble.com>
Message-ID: <CAD_dpu0_LnOQJ0-751kTNdDYvRG_1qGOLO8MQeGfmLZc5SZM2A@mail.gmail.com>

+1 Tested UPS with the staged parent repo,it all looks good.


On Thu, Oct 30, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com> wrote:

> +1 go go go!! :-)
>
> Thanks
> Andrea
>
>
> Matthias Wessendorf wrote
> > Hi,
> >
> > KC 1.0.4 hit maven central, and the version has been integrated in our
> > parent pom.
> >
> > main reason for this release is in fact the new KC version.
> >
> > The staging repo is here:
> >
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4137/
> >
> > Let me know about the release so we can get it out soon, to be on time
> for
> > our UPS release ;-)
> >
> > Cheers,
> > Matthias
> >
> >
> >
> >
> > On Wed, Oct 29, 2014 at 1:27 PM, Matthias Wessendorf &lt;
>
> > matzew@
>
> > &gt;
> > wrote:
> >
> >> Hi,
> >>
> >> I am canceling this release - we need to wait for 1.0.4.Final of
> Keycloak
> >>
> >>
> >> https://issues.jboss.org/browse/KEYCLOAK-797
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli &lt;
>
> > avibelli@
>
> > &gt;
> >> wrote:
> >>
> >>> Hi Matt,
> >>> totally +1, go for it! :-)
> >>>
> >>> Thanks
> >>> Andrea
> >>>
> >>>
> >>> Matthias Wessendorf wrote
> >>> > Ahoy!
> >>> >
> >>> > I am proposing another release, mainly to pick up new keycloak
> version
> >>> > (1.0.3.Final), which contains several fixes.
> >>> >
> >>> > The staging repo is here:
> >>> >
> >>>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
> >>> >
> >>> > Let me know about the release so we can get it out soon, to be on
> time
> >>> for
> >>> > our UPS release ;-)
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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
> >>
> >
> >
> >
> > --
> > Matthias 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-RELEASE-next-try-of-aerogear-parent-0-2-9-release-tp9691p9692.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/20141030/d8bdc718/attachment.html 

From lholmqui at redhat.com  Thu Oct 30 13:38:41 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 30 Oct 2014 13:38:41 -0400
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
	OpenID connect and AeroGear)
In-Reply-To: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
Message-ID: <9F3066F4-86BA-49ED-A0C5-B2DC4A3498B9@redhat.com>

i think this could be interesting.


> On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> Hello team!
> 
> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org <mailto:bruno at abstractj.org>> wrote:
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js.
> 
> Great point on being compatible with passport.js! To ensure our OAuth2 client SDKs do work against node.js (w/ passport.js), how about we build a Node.js based version of our "Shoot-n-Share backend" ([1]), that is protected by Passport.js?
> 
> It could be a (simple) a 'clone' of our java version. I think for Luke, our Node.js pro, it would be a fairly simple task :)

not sure i?ve looked at the java version  :)
> 
> On the client side, the Android/iOS versions of Shoot-n-Share would simply offer a new upload target for Passport.js, instead of 'just' FB, Google-Drive and Keycloak.
> 
> That way we will also learn how much Passport.js is actually different, similar to what we learned on how Google/FB are different ;-)
> 
> Another interesting aspect of this is that, once we are ready to release our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo as well, instead of just a Java-based backend demo. That would clearly show, our client libs are working across different backend technologies.
> 
> Any thoughts?
> 
> -Matthias
> 
> 
> [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot <https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot>
> 
> 
>  
> In the end, OAuth2 is just a protocol and
> should support other servers.
> 
> - Should we provide examples for OpenID connect? Or abstractions?
> 
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
> 
> 
> [1] -
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html <http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html>
> 
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1 <https://gist.github.com/abstractj/04136c6df85cea5f35d1>
> 
> [3] - https://issues.jboss.org/browse/AGSEC-180 <https://issues.jboss.org/browse/AGSEC-180>
> 
> [4] - https://issues.jboss.org/browse/AGSEC-190 <https://issues.jboss.org/browse/AGSEC-190>
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141030/75ebff99/attachment.html 

From cvasilak at gmail.com  Thu Oct 30 13:47:42 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Thu, 30 Oct 2014 19:47:42 +0200
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
	OpenID connect and AeroGear)
In-Reply-To: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
Message-ID: <723EF27D-F609-4CF0-AFAF-591E5373FF38@gmail.com>


On Oct 30, 2014, at 3:41 PM, Matthias Wessendorf <matzew at apache.org> wrote:

> Hello team!
> 
> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js.
> 
> Great point on being compatible with passport.js! To ensure our OAuth2 client SDKs do work against node.js (w/ passport.js), how about we build a Node.js based version of our "Shoot-n-Share backend" ([1]), that is protected by Passport.js?
> 
> It could be a (simple) a 'clone' of our java version. I think for Luke, our Node.js pro, it would be a fairly simple task :)

sounds good, not a JS ninja but can help on the documentation part.

> 
> On the client side, the Android/iOS versions of Shoot-n-Share would simply offer a new upload target for Passport.js, instead of 'just' FB, Google-Drive and Keycloak.
> 
> That way we will also learn how much Passport.js is actually different, similar to what we learned on how Google/FB are different ;-)

guess if Passport.js is completely different, we can always extend the generic iOS OAuth2 module we have and provide a Passport.js adapter (as we do with the FB for example)

Thanks,
Christos

> 
> Another interesting aspect of this is that, once we are ready to release our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo as well, instead of just a Java-based backend demo. That would clearly show, our client libs are working across different backend technologies.
> 
> Any thoughts?
> 
> -Matthias
> 
> 
> [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
> 
> 
>  
> In the end, OAuth2 is just a protocol and
> should support other servers.
> 
> - Should we provide examples for OpenID connect? Or abstractions?
> 
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
> 
> 
> [1] -
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
> 
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
> 
> [3] - https://issues.jboss.org/browse/AGSEC-180
> 
> [4] - https://issues.jboss.org/browse/AGSEC-190
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From lholmqui at redhat.com  Thu Oct 30 14:13:18 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 30 Oct 2014 14:13:18 -0400
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
	OpenID connect and AeroGear)
In-Reply-To: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
Message-ID: <75676CE5-D487-4446-8751-71173D91DABE@redhat.com>


> On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> Hello team!
> 
> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org <mailto:bruno at abstractj.org>> wrote:
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js.
> 
> Great point on being compatible with passport.js! To ensure our OAuth2 client SDKs do work against node.js (w/ passport.js), how about we build a Node.js based version of our "Shoot-n-Share backend" ([1]), that is protected by Passport.js?

So to clear up some confusion that might be happening with what passport is, it is not an OAuth2 server thing.

it?s really just middleware(think of it as a servlet filter for you java weenies) for express.js,  and by using adapters(like a FB or google), it can secure RESTful endpoints in that express.js app.

I think the thing that we can do here is make a keycloack adapter for passport, using the OAuth2 protocol( similar to passports FB and google adapters );



> 
> It could be a (simple) a 'clone' of our java version. I think for Luke, our Node.js pro, it would be a fairly simple task :)
> 
> On the client side, the Android/iOS versions of Shoot-n-Share would simply offer a new upload target for Passport.js, instead of 'just' FB, Google-Drive and Keycloak.
> 
> That way we will also learn how much Passport.js is actually different, similar to what we learned on how Google/FB are different ;-)
> 
> Another interesting aspect of this is that, once we are ready to release our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo as well, instead of just a Java-based backend demo. That would clearly show, our client libs are working across different backend technologies.
> 
> Any thoughts?
> 
> -Matthias
> 
> 
> [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot <https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot>
> 
> 
>  
> In the end, OAuth2 is just a protocol and
> should support other servers.
> 
> - Should we provide examples for OpenID connect? Or abstractions?
> 
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
> 
> 
> [1] -
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html <http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html>
> 
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1 <https://gist.github.com/abstractj/04136c6df85cea5f35d1>
> 
> [3] - https://issues.jboss.org/browse/AGSEC-180 <https://issues.jboss.org/browse/AGSEC-180>
> 
> [4] - https://issues.jboss.org/browse/AGSEC-190 <https://issues.jboss.org/browse/AGSEC-190>
> --
> 
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141030/cb588ae1/attachment.html 

From matzew at apache.org  Thu Oct 30 14:20:04 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 19:20:04 +0100
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
 OpenID connect and AeroGear)
In-Reply-To: <75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
	<75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
Message-ID: <CAAg5f2SAp74AhnrmUSHibbr40-+k6Np1DJ-UX3f49=_8N3x-PQ@mail.gmail.com>

On Thu, Oct 30, 2014 at 7:13 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

>
> On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> Hello team!
>
> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> Note: Not only for Keycloak, but also compatible with other technologies
>> like passport on Node.js.
>
>
> Great point on being compatible with passport.js! To ensure our OAuth2
> client SDKs do work against node.js (w/ passport.js), how about we build a
> Node.js based version of our "Shoot-n-Share backend" ([1]), that is
> protected by Passport.js?
>
>
> So to clear up some confusion that might be happening with what passport
> is, it is not an OAuth2 server thing.
>
> it?s really just middleware(think of it as a servlet filter for you java
> weenies) for express.js,  and by using adapters(like a FB or google), it
> can secure RESTful endpoints in that express.js app.
>
> I think the thing that we can do here is make a keycloack adapter for
> passport, using the OAuth2 protocol( similar to passports FB and google
> adapters );
>

+1 would be nice to get this in https://issues.jboss.org/browse/AGJS-252

On short term, it would be possible to use their existing adapters for
FB/Google and protect the node.js backend with these adapters, right ?


Sounds like the AGJS-252 is the ultimate solution we want, but I think for
a quick test/verification (or even example) of our Android/iOS OAuth2
clients, using the FB/Google adapters from passprt.js would be a good first
start ?

-Matthias





>
>
>
>
> It could be a (simple) a 'clone' of our java version. I think for Luke,
> our Node.js pro, it would be a fairly simple task :)
>
> On the client side, the Android/iOS versions of Shoot-n-Share would simply
> offer a new upload target for Passport.js, instead of 'just' FB,
> Google-Drive and Keycloak.
>
> That way we will also learn how much Passport.js is actually different,
> similar to what we learned on how Google/FB are different ;-)
>
> Another interesting aspect of this is that, once we are ready to release
> our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo
> as well, instead of just a Java-based backend demo. That would clearly
> show, our client libs are working across different backend technologies.
>
> Any thoughts?
>
> -Matthias
>
>
> [1]
> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
>
>
>
>
>> In the end, OAuth2 is just a protocol and
>> should support other servers.
>>
>> - Should we provide examples for OpenID connect? Or abstractions?
>>
>> To track this issue, we have the following Jira[3] and another for
>> OpenID connect[4]. Fell free to link to your respective project.
>>
>>
>> [1] -
>>
>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>>
>> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>>
>> [3] - https://issues.jboss.org/browse/AGSEC-180
>>
>> [4] - https://issues.jboss.org/browse/AGSEC-190
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>  _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Thu Oct 30 14:21:57 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 30 Oct 2014 14:21:57 -0400
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
	OpenID connect and AeroGear)
In-Reply-To: <CAAg5f2SAp74AhnrmUSHibbr40-+k6Np1DJ-UX3f49=_8N3x-PQ@mail.gmail.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
	<75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
	<CAAg5f2SAp74AhnrmUSHibbr40-+k6Np1DJ-UX3f49=_8N3x-PQ@mail.gmail.com>
Message-ID: <6FDF58BF-A883-46BE-AE35-3001230D2E9A@redhat.com>


> On Oct 30, 2014, at 2:20 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Thu, Oct 30, 2014 at 7:13 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> Hello team!
>> 
>> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org <mailto:bruno at abstractj.org>> wrote:
>> Note: Not only for Keycloak, but also compatible with other technologies
>> like passport on Node.js. 
>> 
>> Great point on being compatible with passport.js! To ensure our OAuth2 client SDKs do work against node.js (w/ passport.js), how about we build a Node.js based version of our "Shoot-n-Share backend" ([1]), that is protected by Passport.js?
> 
> So to clear up some confusion that might be happening with what passport is, it is not an OAuth2 server thing.
> 
> it?s really just middleware(think of it as a servlet filter for you java weenies) for express.js,  and by using adapters(like a FB or google), it can secure RESTful endpoints in that express.js app.
> 
> I think the thing that we can do here is make a keycloack adapter for passport, using the OAuth2 protocol( similar to passports FB and google adapters );
> 
> +1 would be nice to get this in https://issues.jboss.org/browse/AGJS-252 <https://issues.jboss.org/browse/AGJS-252>
> 
> On short term, it would be possible to use their existing adapters for FB/Google and protect the node.js backend with these adapters, right ?

i think we can do that

> 
> 
> Sounds like the AGJS-252 is the ultimate solution we want, but I think for a quick test/verification (or even example) of our Android/iOS OAuth2 clients, using the FB/Google adapters from passprt.js would be a good first start ?
> 
> -Matthias
> 
> 
> 
>  
> 
> 
> 
>> 
>> It could be a (simple) a 'clone' of our java version. I think for Luke, our Node.js pro, it would be a fairly simple task :)
>> 
>> On the client side, the Android/iOS versions of Shoot-n-Share would simply offer a new upload target for Passport.js, instead of 'just' FB, Google-Drive and Keycloak.
>> 
>> That way we will also learn how much Passport.js is actually different, similar to what we learned on how Google/FB are different ;-)
>> 
>> Another interesting aspect of this is that, once we are ready to release our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo as well, instead of just a Java-based backend demo. That would clearly show, our client libs are working across different backend technologies.
>> 
>> Any thoughts?
>> 
>> -Matthias
>> 
>> 
>> [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot <https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot>
>> 
>> 
>>  
>> In the end, OAuth2 is just a protocol and
>> should support other servers.
>> 
>> - Should we provide examples for OpenID connect? Or abstractions?
>> 
>> To track this issue, we have the following Jira[3] and another for
>> OpenID connect[4]. Fell free to link to your respective project.
>> 
>> 
>> [1] -
>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html <http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html>
>> 
>> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1 <https://gist.github.com/abstractj/04136c6df85cea5f35d1>
>> 
>> [3] - https://issues.jboss.org/browse/AGSEC-180 <https://issues.jboss.org/browse/AGSEC-180>
>> 
>> [4] - https://issues.jboss.org/browse/AGSEC-190 <https://issues.jboss.org/browse/AGSEC-190>
>> --
>> 
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> 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>
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141030/6433f25d/attachment-0001.html 

From bleathem at gmail.com  Thu Oct 30 14:43:12 2014
From: bleathem at gmail.com (Brian Leathem)
Date: Thu, 30 Oct 2014 11:43:12 -0700
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
 OpenID connect and AeroGear)
In-Reply-To: <6FDF58BF-A883-46BE-AE35-3001230D2E9A@redhat.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
	<75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
	<CAAg5f2SAp74AhnrmUSHibbr40-+k6Np1DJ-UX3f49=_8N3x-PQ@mail.gmail.com>
	<6FDF58BF-A883-46BE-AE35-3001230D2E9A@redhat.com>
Message-ID: <545286C0.7000701@gmail.com>

As a learning exercise I just wrote a MEAN application with both web and
mobile (cordova) front-ends.  The Node.js backend is using passport.js
to both authenticate against Gooale's Oauth2 and to secure the REST API
I implemented with Express.

I should be able to spare some cycles if you could use some extra hands
on this.

Brian

On 14-10-30 11:21 AM, Lucas Holmquist wrote:
>
>> On Oct 30, 2014, at 2:20 PM, Matthias Wessendorf <matzew at apache.org
>> <mailto:matzew at apache.org>> wrote:
>>
>>
>>
>> On Thu, Oct 30, 2014 at 7:13 PM, Lucas Holmquist <lholmqui at redhat.com
>> <mailto:lholmqui at redhat.com>> wrote:
>>
>>
>>>     On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf
>>>     <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>>
>>>     Hello team!
>>>
>>>     On Thu, Oct 9, 2014 at 4:49 AM, Bruno
>>>     Oliveira <bruno at abstractj.org <mailto:bruno at abstractj.org>> wrote:
>>>     Note: Not only for Keycloak, but also compatible with other
>>>     technologies
>>>     like passport on Node.js. 
>>>
>>>     Great point on being compatible with passport.js! To ensure our
>>>     OAuth2 client SDKs do work against node.js (w/ passport.js), how
>>>     about we build a Node.js based version of our "Shoot-n-Share
>>>     backend" ([1]), that is protected by Passport.js?
>>
>>     So to clear up some confusion that might be happening with what
>>     passport is, it is not an OAuth2 server thing.
>>
>>     it?s really just middleware(think of it as a servlet filter for
>>     you java weenies) for express.js,  and by using adapters(like a
>>     FB or google), it can secure RESTful endpoints in that express.js
>>     app.
>>
>>     I think the thing that we can do here is make a keycloack adapter
>>     for passport, using the OAuth2 protocol( similar to passports FB
>>     and google adapters );
>>
>>
>> +1 would be nice to get this in https://issues.jboss.org/browse/AGJS-252
>>
>> On short term, it would be possible to use their existing adapters
>> for FB/Google and protect the node.js backend with these adapters,
>> right ?
>
> i think we can do that
>
>>
>>
>> Sounds like the AGJS-252 is the ultimate solution we want, but I
>> think for a quick test/verification (or even example) of our
>> Android/iOS OAuth2 clients, using the FB/Google adapters from
>> passprt.js would be a good first start ?
>>
>> -Matthias
>>
>>
>>
>>  
>>
>>
>>
>>
>>>
>>>     It could be a (simple) a 'clone' of our java version. I think
>>>     for Luke, our Node.js pro, it would be a fairly simple task :)
>>>
>>>     On the client side, the Android/iOS versions of Shoot-n-Share
>>>     would simply offer a new upload target for Passport.js, instead
>>>     of 'just' FB, Google-Drive and Keycloak.
>>>
>>>     That way we will also learn how much Passport.js is actually
>>>     different, similar to what we learned on how Google/FB are
>>>     different ;-)
>>>
>>>     Another interesting aspect of this is that, once we are ready to
>>>     release our OAuth2 SDKs, it would be awesome to actually ship a
>>>     node.js based demo as well, instead of just a Java-based backend
>>>     demo. That would clearly show, our client libs are working
>>>     across different backend technologies.
>>>
>>>     Any thoughts?
>>>
>>>     -Matthias
>>>
>>>
>>>     [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
>>>
>>>
>>>      
>>>
>>>         In the end, OAuth2 is just a protocol and
>>>         should support other servers.
>>>
>>>         - Should we provide examples for OpenID connect? Or
>>>         abstractions?
>>>
>>>         To track this issue, we have the following Jira[3] and
>>>         another for
>>>         OpenID connect[4]. Fell free to link to your respective project.
>>>
>>>
>>>         [1] -
>>>         http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>>>
>>>         [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>>>
>>>         [3] - https://issues.jboss.org/browse/AGSEC-180
>>>
>>>         [4] - https://issues.jboss.org/browse/AGSEC-190
>>>         --
>>>
>>>         abstractj
>>>         PGP: 0x84DC9914
>>>         _______________________________________________
>>>         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 <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 <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/20141030/dc4e655e/attachment-0001.html 

From matzew at apache.org  Thu Oct 30 15:11:12 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 30 Oct 2014 20:11:12 +0100
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
 OpenID connect and AeroGear)
In-Reply-To: <545286C0.7000701@gmail.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
	<75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
	<CAAg5f2SAp74AhnrmUSHibbr40-+k6Np1DJ-UX3f49=_8N3x-PQ@mail.gmail.com>
	<6FDF58BF-A883-46BE-AE35-3001230D2E9A@redhat.com>
	<545286C0.7000701@gmail.com>
Message-ID: <CAAg5f2RVhxfZG+8va8NN5dcu96F6ZjL1GvQDE6GCt2H+4SVkjQ@mail.gmail.com>

sounds good to me, if you wanna help ;)

On Thursday, October 30, 2014, Brian Leathem <bleathem at gmail.com> wrote:

>  As a learning exercise I just wrote a MEAN application with both web and
> mobile (cordova) front-ends.  The Node.js backend is using passport.js to
> both authenticate against Gooale's Oauth2 and to secure the REST API I
> implemented with Express.
>
> I should be able to spare some cycles if you could use some extra hands on
> this.
>
> Brian
>
> On 14-10-30 11:21 AM, Lucas Holmquist wrote:
>
>
>  On Oct 30, 2014, at 2:20 PM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>
>
> On Thu, Oct 30, 2014 at 7:13 PM, Lucas Holmquist <lholmqui at redhat.com
> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>
>>
>>  On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew at apache.org
>> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>>
>> Hello team!
>>
>> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org
>> <javascript:_e(%7B%7D,'cvml','bruno at abstractj.org');>> wrote:
>> Note: Not only for Keycloak, but also compatible with other technologies
>> like passport on Node.js.
>>
>>  Great point on being compatible with passport.js! To ensure our OAuth2
>> client SDKs do work against node.js (w/ passport.js), how about we build a
>> Node.js based version of our "Shoot-n-Share backend" ([1]), that is
>> protected by Passport.js?
>>
>>
>>  So to clear up some confusion that might be happening with what
>> passport is, it is not an OAuth2 server thing.
>>
>>  it?s really just middleware(think of it as a servlet filter for you
>> java weenies) for express.js,  and by using adapters(like a FB or google),
>> it can secure RESTful endpoints in that express.js app.
>>
>>  I think the thing that we can do here is make a keycloack adapter for
>> passport, using the OAuth2 protocol( similar to passports FB and google
>> adapters );
>>
>
>  +1 would be nice to get this in https://issues.jboss.org/browse/AGJS-252
>
>  On short term, it would be possible to use their existing adapters for
> FB/Google and protect the node.js backend with these adapters, right ?
>
>
>  i think we can do that
>
>
>
>  Sounds like the AGJS-252 is the ultimate solution we want, but I think
> for a quick test/verification (or even example) of our Android/iOS OAuth2
> clients, using the FB/Google adapters from passprt.js would be a good first
> start ?
>
>  -Matthias
>
>
>
>
>
>>
>>
>>
>>
>>  It could be a (simple) a 'clone' of our java version. I think for Luke,
>> our Node.js pro, it would be a fairly simple task :)
>>
>>  On the client side, the Android/iOS versions of Shoot-n-Share would
>> simply offer a new upload target for Passport.js, instead of 'just' FB,
>> Google-Drive and Keycloak.
>>
>>  That way we will also learn how much Passport.js is actually different,
>> similar to what we learned on how Google/FB are different ;-)
>>
>>  Another interesting aspect of this is that, once we are ready to
>> release our OAuth2 SDKs, it would be awesome to actually ship a node.js
>> based demo as well, instead of just a Java-based backend demo. That would
>> clearly show, our client libs are working across different backend
>> technologies.
>>
>>  Any thoughts?
>>
>>  -Matthias
>>
>>
>>  [1]
>> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
>>
>>
>>
>>
>>> In the end, OAuth2 is just a protocol and
>>> should support other servers.
>>>
>>> - Should we provide examples for OpenID connect? Or abstractions?
>>>
>>> To track this issue, we have the following Jira[3] and another for
>>> OpenID connect[4]. Fell free to link to your respective project.
>>>
>>>
>>> [1] -
>>>
>>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
>>>
>>> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>>>
>>> [3] - https://issues.jboss.org/browse/AGSEC-180
>>>
>>> [4] - https://issues.jboss.org/browse/AGSEC-190
>>> --
>>>
>>> abstractj
>>> PGP: 0x84DC9914
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>>  --
>> Matthias Wessendorf
>>
>> blog: http://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:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
>  --
> Matthias Wessendorf
>
> blog: http://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:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.org <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141030/4edea7e5/attachment.html 

From matzew at apache.org  Fri Oct 31 02:21:06 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 31 Oct 2014 07:21:06 +0100
Subject: [aerogear-dev] RELEASE: next try of aerogear-parent 0.2.9
	release
In-Reply-To: <CAD_dpu0_LnOQJ0-751kTNdDYvRG_1qGOLO8MQeGfmLZc5SZM2A@mail.gmail.com>
References: <CAAg5f2Rj7bkHbNip+oZ7xQ6Z_XBbrSaW=tbPNBUK=MCr1KRXTg@mail.gmail.com>
	<1414680900579-9692.post@n5.nabble.com>
	<CAD_dpu0_LnOQJ0-751kTNdDYvRG_1qGOLO8MQeGfmLZc5SZM2A@mail.gmail.com>
Message-ID: <CAAg5f2TTS3R+CO1HSiycq37wPupwEGbP7YR4_pD7gPZ8BzSkAA@mail.gmail.com>

I clicked the magic button to send the pom to maven central

Thanks for testing!

On Thu, Oct 30, 2014 at 5:50 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> +1 Tested UPS with the staged parent repo,it all looks good.
>
>
> On Thu, Oct 30, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>
> wrote:
>
>> +1 go go go!! :-)
>>
>> Thanks
>> Andrea
>>
>>
>> Matthias Wessendorf wrote
>> > Hi,
>> >
>> > KC 1.0.4 hit maven central, and the version has been integrated in our
>> > parent pom.
>> >
>> > main reason for this release is in fact the new KC version.
>> >
>> > The staging repo is here:
>> >
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4137/
>> >
>> > Let me know about the release so we can get it out soon, to be on time
>> for
>> > our UPS release ;-)
>> >
>> > Cheers,
>> > Matthias
>> >
>> >
>> >
>> >
>> > On Wed, Oct 29, 2014 at 1:27 PM, Matthias Wessendorf &lt;
>>
>> > matzew@
>>
>> > &gt;
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> I am canceling this release - we need to wait for 1.0.4.Final of
>> Keycloak
>> >>
>> >>
>> >> https://issues.jboss.org/browse/KEYCLOAK-797
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli &lt;
>>
>> > avibelli@
>>
>> > &gt;
>> >> wrote:
>> >>
>> >>> Hi Matt,
>> >>> totally +1, go for it! :-)
>> >>>
>> >>> Thanks
>> >>> Andrea
>> >>>
>> >>>
>> >>> Matthias Wessendorf wrote
>> >>> > Ahoy!
>> >>> >
>> >>> > I am proposing another release, mainly to pick up new keycloak
>> version
>> >>> > (1.0.3.Final), which contains several fixes.
>> >>> >
>> >>> > The staging repo is here:
>> >>> >
>> >>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/
>> >>> >
>> >>> > Let me know about the release so we can get it out soon, to be on
>> time
>> >>> for
>> >>> > our UPS release ;-)
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Matthias 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-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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
>> >>
>> >
>> >
>> >
>> > --
>> > Matthias 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-RELEASE-next-try-of-aerogear-parent-0-2-9-release-tp9691p9692.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/20141031/4d8f555a/attachment-0001.html 

From bruno at abstractj.org  Fri Oct 31 04:43:48 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 31 Oct 2014 06:43:48 -0200
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
 OpenID connect and AeroGear)
In-Reply-To: <75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
	<75676CE5-D487-4446-8751-71173D91DABE@redhat.com>
Message-ID: <20141031084348.GA26276@abstractj.org>

On 2014-10-30, Lucas Holmquist wrote:
>
> > On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> >
> > Hello team!
> >
> > On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org <mailto:bruno at abstractj.org>> wrote:
> > Note: Not only for Keycloak, but also compatible with other technologies
> > like passport on Node.js.
> >
> > Great point on being compatible with passport.js! To ensure our OAuth2 client SDKs do work against node.js (w/ passport.js), how about we build a Node.js based version of our "Shoot-n-Share backend" ([1]), that is protected by Passport.js?
>
> So to clear up some confusion that might be happening with what passport is, it is not an OAuth2 server thing.
>
> it?s really just middleware(think of it as a servlet filter for you java weenies) for express.js,  and by using adapters(like a FB or google), it can secure RESTful endpoints in that express.js app.
>
> I think the thing that we can do here is make a keycloack adapter for passport, using the OAuth2 protocol( similar to passports FB and google adapters );

You're correct. What I meant in my previous e-mail, was the fact that we
not necessarily need to be tied to some technology, but think about
other technologies as well.
>
>
>
> >
> > It could be a (simple) a 'clone' of our java version. I think for Luke, our Node.js pro, it would be a fairly simple task :)
> >
> > On the client side, the Android/iOS versions of Shoot-n-Share would simply offer a new upload target for Passport.js, instead of 'just' FB, Google-Drive and Keycloak.
> >
> > That way we will also learn how much Passport.js is actually different, similar to what we learned on how Google/FB are different ;-)
> >
> > Another interesting aspect of this is that, once we are ready to release our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo as well, instead of just a Java-based backend demo. That would clearly show, our client libs are working across different backend technologies.
> >
> > Any thoughts?
> >
> > -Matthias
> >
> >
> > [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot <https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot>
> >
> >
> >
> > In the end, OAuth2 is just a protocol and
> > should support other servers.
> >
> > - Should we provide examples for OpenID connect? Or abstractions?
> >
> > To track this issue, we have the following Jira[3] and another for
> > OpenID connect[4]. Fell free to link to your respective project.
> >
> >
> > [1] -
> > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html <http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html>
> >
> > [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1 <https://gist.github.com/abstractj/04136c6df85cea5f35d1>
> >
> > [3] - https://issues.jboss.org/browse/AGSEC-180 <https://issues.jboss.org/browse/AGSEC-180>
> >
> > [4] - https://issues.jboss.org/browse/AGSEC-190 <https://issues.jboss.org/browse/AGSEC-190>
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > 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>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> > sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> > twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>_______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>

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


--

abstractj
PGP: 0x84DC9914

From bruno at abstractj.org  Fri Oct 31 04:46:29 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 31 Oct 2014 06:46:29 -0200
Subject: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2,
 OpenID connect and AeroGear)
In-Reply-To: <723EF27D-F609-4CF0-AFAF-591E5373FF38@gmail.com>
References: <CAAg5f2S4D1VqtHJGzOd0yUgpd-C-+ea3vWJ4JWgcruEkx88deg@mail.gmail.com>
	<723EF27D-F609-4CF0-AFAF-591E5373FF38@gmail.com>
Message-ID: <20141031084629.GB26276@abstractj.org>

On 2014-10-30, Christos Vasilakis wrote:
>
> On Oct 30, 2014, at 3:41 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>
> > Hello team!
> >
> > On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
> > Note: Not only for Keycloak, but also compatible with other technologies
> > like passport on Node.js.
> >
> > Great point on being compatible with passport.js! To ensure our OAuth2 client SDKs do work against node.js (w/ passport.js), how about we build a Node.js based version of our "Shoot-n-Share backend" ([1]), that is protected by Passport.js?
> >
> > It could be a (simple) a 'clone' of our java version. I think for Luke, our Node.js pro, it would be a fairly simple task :)
>
> sounds good, not a JS ninja but can help on the documentation part.
>
> >
> > On the client side, the Android/iOS versions of Shoot-n-Share would simply offer a new upload target for Passport.js, instead of 'just' FB, Google-Drive and Keycloak.
> >
> > That way we will also learn how much Passport.js is actually different, similar to what we learned on how Google/FB are different ;-)
>
> guess if Passport.js is completely different, we can always extend the generic iOS OAuth2 module we have and provide a Passport.js adapter (as we do with the FB for example)

I'm ok with this, but a bit concerned about us being focused on
technologies instead of the RFC.

>
> Thanks,
> Christos
>
> >
> > Another interesting aspect of this is that, once we are ready to release our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo as well, instead of just a Java-based backend demo. That would clearly show, our client libs are working across different backend technologies.
> >
> > Any thoughts?
> >
> > -Matthias
> >
> >
> > [1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
> >
> >
> >
> > In the end, OAuth2 is just a protocol and
> > should support other servers.
> >
> > - Should we provide examples for OpenID connect? Or abstractions?
> >
> > To track this issue, we have the following Jira[3] and another for
> > OpenID connect[4]. Fell free to link to your respective project.
> >
> >
> > [1] -
> > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-10-08-14.00.html
> >
> > [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
> >
> > [3] - https://issues.jboss.org/browse/AGSEC-180
> >
> > [4] - https://issues.jboss.org/browse/AGSEC-190
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>

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


--

abstractj
PGP: 0x84DC9914

From matzew at apache.org  Fri Oct 31 07:29:38 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 31 Oct 2014 12:29:38 +0100
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
Message-ID: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>

Hello folks!

here is another release, containing some fixes since the last 1.0.1
release! Thanks to the team for all the hard work it put into this 1.0.2
release!

Here are a few highlights of this release:
* Keycloak 1.0.4 usage
* new developer role
* documentation updates
* SSLv3 version removed from docs
* UI fixes and improvements
* Polish UI to look nice(r) on mobile devices

You'll find details on all the JIRAs can be found here:
https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/

The staging repository is located here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/


NOTE: Once this release has been approved the matching tag will be used to
get the OpenShift online bits updated!

Let me know the results of your testing!
If I hear nothing bad by Tuesday evening, the release to maven central will
happen on Wednesday morning;

Greetings,
Matthias

-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Fri Oct 31 07:47:55 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 31 Oct 2014 07:47:55 -0400
Subject: [aerogear-dev] RELEASE: next try of aerogear-parent 0.2.9
	release
In-Reply-To: <CAAg5f2TTS3R+CO1HSiycq37wPupwEGbP7YR4_pD7gPZ8BzSkAA@mail.gmail.com>
References: <CAAg5f2Rj7bkHbNip+oZ7xQ6Z_XBbrSaW=tbPNBUK=MCr1KRXTg@mail.gmail.com>
	<1414680900579-9692.post@n5.nabble.com>
	<CAD_dpu0_LnOQJ0-751kTNdDYvRG_1qGOLO8MQeGfmLZc5SZM2A@mail.gmail.com>
	<CAAg5f2TTS3R+CO1HSiycq37wPupwEGbP7YR4_pD7gPZ8BzSkAA@mail.gmail.com>
Message-ID: <5A43E1AC-2C98-4385-8867-5B1D64402498@redhat.com>


> On Oct 31, 2014, at 2:21 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> I clicked the magic button to send the pom to maven central

i thought i felt a disturbance in the force :)

> 
> Thanks for testing!
> 
> On Thu, Oct 30, 2014 at 5:50 PM, Sebastien Blanc <scm.blanc at gmail.com <mailto:scm.blanc at gmail.com>> wrote:
> +1 Tested UPS with the staged parent repo,it all looks good.
> 
> 
> On Thu, Oct 30, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com <mailto:avibelli at redhat.com>> wrote:
> +1 go go go!! :-)
> 
> Thanks
> Andrea
> 
> 
> Matthias Wessendorf wrote
> > Hi,
> >
> > KC 1.0.4 hit maven central, and the version has been integrated in our
> > parent pom.
> >
> > main reason for this release is in fact the new KC version.
> >
> > The staging repo is here:
> > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4137/ <https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4137/>
> >
> > Let me know about the release so we can get it out soon, to be on time for
> > our UPS release ;-)
> >
> > Cheers,
> > Matthias
> >
> >
> >
> >
> > On Wed, Oct 29, 2014 at 1:27 PM, Matthias Wessendorf &lt;
> 
> > matzew@
> 
> > &gt;
> > wrote:
> >
> >> Hi,
> >>
> >> I am canceling this release - we need to wait for 1.0.4.Final of Keycloak
> >>
> >>
> >> https://issues.jboss.org/browse/KEYCLOAK-797 <https://issues.jboss.org/browse/KEYCLOAK-797>
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Oct 29, 2014 at 9:39 AM, Andrea Vibelli &lt;
> 
> > avibelli@
> 
> > &gt;
> >> wrote:
> >>
> >>> Hi Matt,
> >>> totally +1, go for it! :-)
> >>>
> >>> Thanks
> >>> Andrea
> >>>
> >>>
> >>> Matthias Wessendorf wrote
> >>> > Ahoy!
> >>> >
> >>> > I am proposing another release, mainly to pick up new keycloak version
> >>> > (1.0.3.Final), which contains several fixes.
> >>> >
> >>> > The staging repo is here:
> >>> >
> >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/ <https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4122/>
> >>> >
> >>> > Let me know about the release so we can get it out soon, to be on time
> >>> for
> >>> > our UPS release ;-)
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Matthias Wessendorf
> >>> >
> >>> > blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> >>> > sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> >>> > twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> >>> >
> >>> > _______________________________________________
> >>> > aerogear-dev mailing list
> >>>
> >>> > aerogear-dev at .jboss
> >>>
> >>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-RELEASE-aerogear-parent-0-2-9-tp9667p9670.html <http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-RELEASE-aerogear-parent-0-2-9-tp9667p9670.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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> >> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> >> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> >>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> > sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> > twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> >
> > _______________________________________________
> > aerogear-dev mailing list
> 
> > aerogear-dev at .jboss
> 
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
> 
> 
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-RELEASE-next-try-of-aerogear-parent-0-2-9-release-tp9691p9692.html <http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-RELEASE-next-try-of-aerogear-parent-0-2-9-release-tp9691p9692.html>
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> 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>
> 
> 
> _______________________________________________
> 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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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/20141031/6d2076d7/attachment-0001.html 

From daniel at passos.me  Fri Oct 31 08:07:05 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 31 Oct 2014 10:07:05 -0200
Subject: [aerogear-dev] Travis problem with Android Lollipop
Message-ID: <CAKjsGbvNmSv84D34N7Lc1bxF-GOR=NNDZ8fnTZvhgpCf=tNc8Q@mail.gmail.com>

Hi Guys,

I'm trying to update our library to use Android Lollipop, but I'm getting
problem with travis wait.for-emulator.sh script. It is not recognizing when
emulator is running and not start the tests..

It's blocking us to moving forward and update the push library.

https://github.com/danielpassos/aerogear-android-push/tree/update-pom-and-travis
https://travis-ci.org/danielpassos/aerogear-android-push/builds/38713813

I've created a blank project to do some tests and I got the same problem. I
sent it to the travis support and I'm waiting for the reply.

https://github.com/danielpassos/travis-lollipop-test
https://travis-ci.org/danielpassos/travis-lollipop-test

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

From matzew at apache.org  Fri Oct 31 09:19:54 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 31 Oct 2014 14:19:54 +0100
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
Message-ID: <CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>

Hi,

if you wonder what to test the UPS with, please use the helloword (1.0.x
branch):
https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x

and/or the quickstarts (but here the master branch):
https://github.com/aerogear/aerogear-push-quickstarts

Here it's also important to test with Cordova, since we do have a new
version (1.0.2) out there:
http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push

Please also give the native apps a test-drive, even we had no new release
on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)

If you want to test the new role, you will find some details here:
https://github.com/aerogear/aerogear.org/pull/411

Thanks!
Matthias


On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello folks!
>
> here is another release, containing some fixes since the last 1.0.1
> release! Thanks to the team for all the hard work it put into this 1.0.2
> release!
>
> Here are a few highlights of this release:
> * Keycloak 1.0.4 usage
> * new developer role
> * documentation updates
> * SSLv3 version removed from docs
> * UI fixes and improvements
> * Polish UI to look nice(r) on mobile devices
>
> You'll find details on all the JIRAs can be found here:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/
>
> The staging repository is located here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/
>
>
> NOTE: Once this release has been approved the matching tag will be used to
> get the OpenShift online bits updated!
>
> Let me know the results of your testing!
> If I hear nothing bad by Tuesday evening, the release to maven central
> will happen on Wednesday morning;
>
> Greetings,
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

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

From lholmqui at redhat.com  Fri Oct 31 10:38:41 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 31 Oct 2014 10:38:41 -0400
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
Message-ID: <6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>


> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> Hi,
> 
> if you wonder what to test the UPS with, please use the helloword (1.0.x branch):
> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x>
> 
> and/or the quickstarts (but here the master branch):
> https://github.com/aerogear/aerogear-push-quickstarts <https://github.com/aerogear/aerogear-push-quickstarts>
One thing i noticed starting to test the cordova quick start.  There is no link to the steps involved in creating a variant for Android/iOS

> 
> Here it's also important to test with Cordova, since we do have a new version (1.0.2) out there:
> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push <http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push>
> 
> Please also give the native apps a test-drive, even we had no new release on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)
> 
> If you want to test the new role, you will find some details here:
> https://github.com/aerogear/aerogear.org/pull/411 <https://github.com/aerogear/aerogear.org/pull/411>
> 
> Thanks!
> Matthias
> 
> 
> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> Hello folks!
> 
> here is another release, containing some fixes since the last 1.0.1 release! Thanks to the team for all the hard work it put into this 1.0.2 release!
> 
> Here are a few highlights of this release:
> * Keycloak 1.0.4 usage
> * new developer role
> * documentation updates
> * SSLv3 version removed from docs
> * UI fixes and improvements
> * Polish UI to look nice(r) on mobile devices
> 
> You'll find details on all the JIRAs can be found here:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/ <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/>
> 
> The staging repository is located here:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/ <https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/>
> 
> 
> NOTE: Once this release has been approved the matching tag will be used to get the OpenShift online bits updated!
> 
> Let me know the results of your testing!
> If I hear nothing bad by Tuesday evening, the release to maven central will happen on Wednesday morning;
> 
> Greetings,
> Matthias
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141031/6e05c856/attachment.html 

From matzew at apache.org  Fri Oct 31 10:43:56 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 31 Oct 2014 15:43:56 +0100
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
Message-ID: <CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>

On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

>
> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> Hi,
>
> if you wonder what to test the UPS with, please use the helloword (1.0.x
> branch):
> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x
>
> and/or the quickstarts (but here the master branch):
> https://github.com/aerogear/aerogear-push-quickstarts
>
>
> One thing i noticed starting to test the cordova quick start.  There is no
> link to the steps involved in creating a variant for Android/iOS
>

you mean like
https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services
  ?
Can you file JIRA for that ?


>
>
> Here it's also important to test with Cordova, since we do have a new
> version (1.0.2) out there:
> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push
>
> Please also give the native apps a test-drive, even we had no new release
> on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)
>
> If you want to test the new role, you will find some details here:
> https://github.com/aerogear/aerogear.org/pull/411
>
> Thanks!
> Matthias
>
>
> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hello folks!
>>
>> here is another release, containing some fixes since the last 1.0.1
>> release! Thanks to the team for all the hard work it put into this 1.0.2
>> release!
>>
>> Here are a few highlights of this release:
>> * Keycloak 1.0.4 usage
>> * new developer role
>> * documentation updates
>> * SSLv3 version removed from docs
>> * UI fixes and improvements
>> * Polish UI to look nice(r) on mobile devices
>>
>> You'll find details on all the JIRAs can be found here:
>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/
>>
>> The staging repository is located here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/
>>
>>
>> NOTE: Once this release has been approved the matching tag will be used
>> to get the OpenShift online bits updated!
>>
>> Let me know the results of your testing!
>> If I hear nothing bad by Tuesday evening, the release to maven central
>> will happen on Wednesday morning;
>>
>> Greetings,
>> Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141031/865525b2/attachment-0001.html 

From lholmqui at redhat.com  Fri Oct 31 10:45:52 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 31 Oct 2014 10:45:52 -0400
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
	<CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
Message-ID: <1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>


> On Oct 31, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> Hi,
>> 
>> if you wonder what to test the UPS with, please use the helloword (1.0.x branch):
>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x>
>> 
>> and/or the quickstarts (but here the master branch):
>> https://github.com/aerogear/aerogear-push-quickstarts <https://github.com/aerogear/aerogear-push-quickstarts>
> One thing i noticed starting to test the cordova quick start.  There is no link to the steps involved in creating a variant for Android/iOS
> 
> you mean like https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services>   ?
> Can you file JIRA for that ?
yup and yup


>  
> 
>> 
>> Here it's also important to test with Cordova, since we do have a new version (1.0.2) out there:
>> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push <http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push>
>> 
>> Please also give the native apps a test-drive, even we had no new release on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)
>> 
>> If you want to test the new role, you will find some details here:
>> https://github.com/aerogear/aerogear.org/pull/411 <https://github.com/aerogear/aerogear.org/pull/411>
>> 
>> Thanks!
>> Matthias
>> 
>> 
>> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> Hello folks!
>> 
>> here is another release, containing some fixes since the last 1.0.1 release! Thanks to the team for all the hard work it put into this 1.0.2 release!
>> 
>> Here are a few highlights of this release:
>> * Keycloak 1.0.4 usage
>> * new developer role
>> * documentation updates
>> * SSLv3 version removed from docs
>> * UI fixes and improvements
>> * Polish UI to look nice(r) on mobile devices
>> 
>> You'll find details on all the JIRAs can be found here:
>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/ <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/>
>> 
>> The staging repository is located here:
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/ <https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/>
>> 
>> 
>> NOTE: Once this release has been approved the matching tag will be used to get the OpenShift online bits updated!
>> 
>> Let me know the results of your testing!
>> If I hear nothing bad by Tuesday evening, the release to maven central will happen on Wednesday morning;
>> 
>> Greetings,
>> Matthias
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
> twitter: http://twitter.com/mwessendorf <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141031/2a3c63fc/attachment.html 

From scm.blanc at gmail.com  Fri Oct 31 10:51:15 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 31 Oct 2014 15:51:15 +0100
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
	<CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
	<1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>
Message-ID: <CAD_dpu2hbGN_=_T4_hJR+dUMUGhD1zHTQJq2LO8QsVnEackfqA@mail.gmail.com>

Ok I tested various flows with different roles + Quickstarts/HelloWorld
(Cordova)
All good, except Quickstart JQM but that is unrelated to UPS release
+1


On Fri, Oct 31, 2014 at 3:45 PM, Lucas Holmquist <lholmqui at redhat.com>
wrote:

>
> On Oct 31, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>
>
> On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>> Hi,
>>
>> if you wonder what to test the UPS with, please use the helloword (1.0.x
>> branch):
>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x
>>
>> and/or the quickstarts (but here the master branch):
>> https://github.com/aerogear/aerogear-push-quickstarts
>>
>>
>> One thing i noticed starting to test the cordova quick start.  There is
>> no link to the steps involved in creating a variant for Android/iOS
>>
>
> you mean like
> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services
>    ?
> Can you file JIRA for that ?
>
> yup and yup
>
>
>
>
>>
>>
>> Here it's also important to test with Cordova, since we do have a new
>> version (1.0.2) out there:
>> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push
>>
>> Please also give the native apps a test-drive, even we had no new release
>> on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)
>>
>> If you want to test the new role, you will find some details here:
>> https://github.com/aerogear/aerogear.org/pull/411
>>
>> Thanks!
>> Matthias
>>
>>
>> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org>
>>  wrote:
>>
>>> Hello folks!
>>>
>>> here is another release, containing some fixes since the last 1.0.1
>>> release! Thanks to the team for all the hard work it put into this 1.0.2
>>> release!
>>>
>>> Here are a few highlights of this release:
>>> * Keycloak 1.0.4 usage
>>> * new developer role
>>> * documentation updates
>>> * SSLv3 version removed from docs
>>> * UI fixes and improvements
>>> * Polish UI to look nice(r) on mobile devices
>>>
>>> You'll find details on all the JIRAs can be found here:
>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/
>>>
>>> The staging repository is located here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/
>>>
>>>
>>> NOTE: Once this release has been approved the matching tag will be used
>>> to get the OpenShift online bits updated!
>>>
>>> Let me know the results of your testing!
>>> If I hear nothing bad by Tuesday evening, the release to maven central
>>> will happen on Wednesday morning;
>>>
>>> Greetings,
>>> Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141031/4878954f/attachment-0001.html 

From lholmqui at redhat.com  Fri Oct 31 11:39:41 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 31 Oct 2014 11:39:41 -0400
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <CAD_dpu2hbGN_=_T4_hJR+dUMUGhD1zHTQJq2LO8QsVnEackfqA@mail.gmail.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
	<CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
	<1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>
	<CAD_dpu2hbGN_=_T4_hJR+dUMUGhD1zHTQJq2LO8QsVnEackfqA@mail.gmail.com>
Message-ID: <6F8A57A8-5294-4968-88BD-DA6F6B55EEA9@redhat.com>

So far tested the QuickStarts (Cordova). both work good. JQM works now after this fix from sebi ,https://issues.jboss.org/browse/AGPUSH-1090 <https://issues.jboss.org/browse/AGPUSH-1090>

the only real issue i have is the date picker won?t let me make the contact reaaaaaallly old

> On Oct 31, 2014, at 10:51 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> Ok I tested various flows with different roles + Quickstarts/HelloWorld (Cordova)
> All good, except Quickstart JQM but that is unrelated to UPS release
> +1
> 
> 
> On Fri, Oct 31, 2014 at 3:45 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
> 
>> On Oct 31, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>> 
>> 
>> 
>> On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> 
>>> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>> 
>>> Hi,
>>> 
>>> if you wonder what to test the UPS with, please use the helloword (1.0.x branch):
>>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x>
>>> 
>>> and/or the quickstarts (but here the master branch):
>>> https://github.com/aerogear/aerogear-push-quickstarts <https://github.com/aerogear/aerogear-push-quickstarts>
>> One thing i noticed starting to test the cordova quick start.  There is no link to the steps involved in creating a variant for Android/iOS
>> 
>> you mean like https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services>   ?
>> Can you file JIRA for that ?
> 
> yup and yup
> 
> 
>>  
>> 
>>> 
>>> Here it's also important to test with Cordova, since we do have a new version (1.0.2) out there:
>>> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push <http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push>
>>> 
>>> Please also give the native apps a test-drive, even we had no new release on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)
>>> 
>>> If you want to test the new role, you will find some details here:
>>> https://github.com/aerogear/aerogear.org/pull/411 <https://github.com/aerogear/aerogear.org/pull/411>
>>> 
>>> Thanks!
>>> Matthias
>>> 
>>> 
>>> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>> Hello folks!
>>> 
>>> here is another release, containing some fixes since the last 1.0.1 release! Thanks to the team for all the hard work it put into this 1.0.2 release!
>>> 
>>> Here are a few highlights of this release:
>>> * Keycloak 1.0.4 usage
>>> * new developer role
>>> * documentation updates
>>> * SSLv3 version removed from docs
>>> * UI fixes and improvements
>>> * Polish UI to look nice(r) on mobile devices
>>> 
>>> You'll find details on all the JIRAs can be found here:
>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/ <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/>
>>> 
>>> The staging repository is located here:
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/ <https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/>
>>> 
>>> 
>>> NOTE: Once this release has been approved the matching tag will be used to get the OpenShift online bits updated!
>>> 
>>> Let me know the results of your testing!
>>> If I hear nothing bad by Tuesday evening, the release to maven central will happen on Wednesday morning;
>>> 
>>> Greetings,
>>> Matthias
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>> twitter: http://twitter.com/mwessendorf <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 <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>
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>> twitter: http://twitter.com/mwessendorf <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 <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>
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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

From lholmqui at redhat.com  Fri Oct 31 11:40:14 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 31 Oct 2014 11:40:14 -0400
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <6F8A57A8-5294-4968-88BD-DA6F6B55EEA9@redhat.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
	<CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
	<1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>
	<CAD_dpu2hbGN_=_T4_hJR+dUMUGhD1zHTQJq2LO8QsVnEackfqA@mail.gmail.com>
	<6F8A57A8-5294-4968-88BD-DA6F6B55EEA9@redhat.com>
Message-ID: <1F5A6911-5B6D-418B-83F0-AB44E6A43CC0@redhat.com>


> On Oct 31, 2014, at 11:39 AM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
> So far tested the QuickStarts (Cordova). both work good. JQM works now after this fix from sebi ,https://issues.jboss.org/browse/AGPUSH-1090 <https://issues.jboss.org/browse/AGPUSH-1090>
should also note,  i?ve tested just the android cordova versions
> 
> the only real issue i have is the date picker won?t let me make the contact reaaaaaallly old
> 
>> On Oct 31, 2014, at 10:51 AM, Sebastien Blanc <scm.blanc at gmail.com <mailto:scm.blanc at gmail.com>> wrote:
>> 
>> Ok I tested various flows with different roles + Quickstarts/HelloWorld (Cordova)
>> All good, except Quickstart JQM but that is unrelated to UPS release
>> +1
>> 
>> 
>> On Fri, Oct 31, 2014 at 3:45 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>> 
>>> On Oct 31, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>> 
>>> 
>>> 
>>> On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>>> 
>>>> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> if you wonder what to test the UPS with, please use the helloword (1.0.x branch):
>>>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x>
>>>> 
>>>> and/or the quickstarts (but here the master branch):
>>>> https://github.com/aerogear/aerogear-push-quickstarts <https://github.com/aerogear/aerogear-push-quickstarts>
>>> One thing i noticed starting to test the cordova quick start.  There is no link to the steps involved in creating a variant for Android/iOS
>>> 
>>> you mean like https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services <https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services>   ?
>>> Can you file JIRA for that ?
>> 
>> yup and yup
>> 
>> 
>>>  
>>> 
>>>> 
>>>> Here it's also important to test with Cordova, since we do have a new version (1.0.2) out there:
>>>> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push <http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push>
>>>> 
>>>> Please also give the native apps a test-drive, even we had no new release on the Push SDKs for Android and iOS since our 1.0.0 release in August :-)
>>>> 
>>>> If you want to test the new role, you will find some details here:
>>>> https://github.com/aerogear/aerogear.org/pull/411 <https://github.com/aerogear/aerogear.org/pull/411>
>>>> 
>>>> Thanks!
>>>> Matthias
>>>> 
>>>> 
>>>> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>>>> Hello folks!
>>>> 
>>>> here is another release, containing some fixes since the last 1.0.1 release! Thanks to the team for all the hard work it put into this 1.0.2 release!
>>>> 
>>>> Here are a few highlights of this release:
>>>> * Keycloak 1.0.4 usage
>>>> * new developer role
>>>> * documentation updates
>>>> * SSLv3 version removed from docs
>>>> * UI fixes and improvements
>>>> * Polish UI to look nice(r) on mobile devices
>>>> 
>>>> You'll find details on all the JIRAs can be found here:
>>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/ <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/>
>>>> 
>>>> The staging repository is located here:
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/ <https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/>
>>>> 
>>>> 
>>>> NOTE: Once this release has been approved the matching tag will be used to get the OpenShift online bits updated!
>>>> 
>>>> Let me know the results of your testing!
>>>> If I hear nothing bad by Tuesday evening, the release to maven central will happen on Wednesday morning;
>>>> 
>>>> Greetings,
>>>> Matthias
>>>> 
>>>> -- 
>>>> Matthias Wessendorf 
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>>> twitter: http://twitter.com/mwessendorf <http://twitter.com/mwessendorf>
>>>> 
>>>> 
>>>> -- 
>>>> Matthias Wessendorf 
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>>> twitter: http://twitter.com/mwessendorf <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 <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>
>>> 
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/ <http://matthiaswessendorf.wordpress.com/>
>>> sessions: http://www.slideshare.net/mwessendorf <http://www.slideshare.net/mwessendorf>
>>> twitter: http://twitter.com/mwessendorf <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 <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>
>> 
>> _______________________________________________
>> 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
> 

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

From daniel.bevenius at gmail.com  Fri Oct 31 11:48:25 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 31 Oct 2014 16:48:25 +0100
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <1F5A6911-5B6D-418B-83F0-AB44E6A43CC0@redhat.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
	<CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
	<1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>
	<CAD_dpu2hbGN_=_T4_hJR+dUMUGhD1zHTQJq2LO8QsVnEackfqA@mail.gmail.com>
	<6F8A57A8-5294-4968-88BD-DA6F6B55EEA9@redhat.com>
	<1F5A6911-5B6D-418B-83F0-AB44E6A43CC0@redhat.com>
Message-ID: <CAFJm-3GXSn0-2ZM4TqSXP9Kf0TqqTW=y-Rw_Q2b4j4upr9fz2g@mail.gmail.com>

I've tested enabling the developer user and ran into an issue [1]. I can
enable the user and then log into the UPS admin console. But if I simply
logout of the console where I enabled the users (I'm guessing this is the
KC console) I'm not able to and there is no error. Not sure if this is
supposed to work as the developer user probably does not have the rights to
access that admin console but I wanted to bring it up just the same.

[1] https://issues.jboss.org/browse/AGPUSH-1091

On 31 October 2014 16:40, Lucas Holmquist <lholmqui at redhat.com> wrote:

>
> On Oct 31, 2014, at 11:39 AM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>
> So far tested the QuickStarts (Cordova). both work good. JQM works now
> after this fix from sebi ,https://issues.jboss.org/browse/AGPUSH-1090
>
>
> should also note,  i?ve tested just the android cordova versions
>
>
> the only real issue i have is the date picker won?t let me make the
> contact reaaaaaallly old
>
> On Oct 31, 2014, at 10:51 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> Ok I tested various flows with different roles + Quickstarts/HelloWorld
> (Cordova)
> All good, except Quickstart JQM but that is unrelated to UPS release
> +1
>
>
> On Fri, Oct 31, 2014 at 3:45 PM, Lucas Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>> On Oct 31, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>
>>
>> On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>
>>> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>> Hi,
>>>
>>> if you wonder what to test the UPS with, please use the helloword (1.0.x
>>> branch):
>>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x
>>>
>>> and/or the quickstarts (but here the master branch):
>>> https://github.com/aerogear/aerogear-push-quickstarts
>>>
>>>
>>> One thing i noticed starting to test the cordova quick start.  There is
>>> no link to the steps involved in creating a variant for Android/iOS
>>>
>>
>> you mean like
>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services
>>    ?
>> Can you file JIRA for that ?
>>
>> yup and yup
>>
>>
>>
>>
>>>
>>>
>>> Here it's also important to test with Cordova, since we do have a new
>>> version (1.0.2) out there:
>>> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push
>>>
>>> Please also give the native apps a test-drive, even we had no new
>>> release on the Push SDKs for Android and iOS since our 1.0.0 release in
>>> August :-)
>>>
>>> If you want to test the new role, you will find some details here:
>>> https://github.com/aerogear/aerogear.org/pull/411
>>>
>>> Thanks!
>>> Matthias
>>>
>>>
>>> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> Hello folks!
>>>>
>>>> here is another release, containing some fixes since the last 1.0.1
>>>> release! Thanks to the team for all the hard work it put into this 1.0.2
>>>> release!
>>>>
>>>> Here are a few highlights of this release:
>>>> * Keycloak 1.0.4 usage
>>>> * new developer role
>>>> * documentation updates
>>>> * SSLv3 version removed from docs
>>>> * UI fixes and improvements
>>>> * Polish UI to look nice(r) on mobile devices
>>>>
>>>> You'll find details on all the JIRAs can be found here:
>>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/
>>>>
>>>> The staging repository is located here:
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/
>>>>
>>>>
>>>> NOTE: Once this release has been approved the matching tag will be used
>>>> to get the OpenShift online bits updated!
>>>>
>>>> Let me know the results of your testing!
>>>> If I hear nothing bad by Tuesday evening, the release to maven central
>>>> will happen on Wednesday morning;
>>>>
>>>> Greetings,
>>>> Matthias
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141031/846833ed/attachment.html 

From matzew at apache.org  Fri Oct 31 11:54:21 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 31 Oct 2014 16:54:21 +0100
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <CAFJm-3GXSn0-2ZM4TqSXP9Kf0TqqTW=y-Rw_Q2b4j4upr9fz2g@mail.gmail.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
	<CAAg5f2RSzqqdYWgYurzh8v-941B2VEv3Ut44+6nyVU8z=6m5Lg@mail.gmail.com>
	<6AFED6A9-FA43-4342-ACB3-95A7D9521526@redhat.com>
	<CAAg5f2Rwgq=6n3CA-CD_wb4aN39nJ5uyC+0NGrOuqv=yOQ5sgA@mail.gmail.com>
	<1AD2A295-FD2D-4776-8D66-ED1E6A787F1C@redhat.com>
	<CAD_dpu2hbGN_=_T4_hJR+dUMUGhD1zHTQJq2LO8QsVnEackfqA@mail.gmail.com>
	<6F8A57A8-5294-4968-88BD-DA6F6B55EEA9@redhat.com>
	<1F5A6911-5B6D-418B-83F0-AB44E6A43CC0@redhat.com>
	<CAFJm-3GXSn0-2ZM4TqSXP9Kf0TqqTW=y-Rw_Q2b4j4upr9fz2g@mail.gmail.com>
Message-ID: <CAAg5f2RO+pb8656UmokH3LVsJnrUZ1q5vz_6URqbckfwP4xGGw@mail.gmail.com>

that's right, the developer is not an admin:
https://gist.github.com/matzew/ed0055000a8347488a37#roles--permissions

On Fri, Oct 31, 2014 at 4:48 PM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> I've tested enabling the developer user and ran into an issue [1]. I can
> enable the user and then log into the UPS admin console. But if I simply
> logout of the console where I enabled the users (I'm guessing this is the
> KC console) I'm not able to and there is no error. Not sure if this is
> supposed to work as the developer user probably does not have the rights to
> access that admin console but I wanted to bring it up just the same.
>
> [1] https://issues.jboss.org/browse/AGPUSH-1091
>
> On 31 October 2014 16:40, Lucas Holmquist <lholmqui at redhat.com> wrote:
>
>>
>> On Oct 31, 2014, at 11:39 AM, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>> So far tested the QuickStarts (Cordova). both work good. JQM works now
>> after this fix from sebi ,https://issues.jboss.org/browse/AGPUSH-1090
>>
>>
>> should also note,  i?ve tested just the android cordova versions
>>
>>
>> the only real issue i have is the date picker won?t let me make the
>> contact reaaaaaallly old
>>
>> On Oct 31, 2014, at 10:51 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>> Ok I tested various flows with different roles + Quickstarts/HelloWorld
>> (Cordova)
>> All good, except Quickstart JQM but that is unrelated to UPS release
>> +1
>>
>>
>> On Fri, Oct 31, 2014 at 3:45 PM, Lucas Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>
>>> On Oct 31, 2014, at 10:43 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>
>>>
>>> On Fri, Oct 31, 2014 at 3:38 PM, Lucas Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>>
>>>> On Oct 31, 2014, at 9:19 AM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> if you wonder what to test the UPS with, please use the helloword
>>>> (1.0.x branch):
>>>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x
>>>>
>>>> and/or the quickstarts (but here the master branch):
>>>> https://github.com/aerogear/aerogear-push-quickstarts
>>>>
>>>>
>>>> One thing i noticed starting to test the cordova quick start.  There is
>>>> no link to the steps involved in creating a variant for Android/iOS
>>>>
>>>
>>> you mean like
>>> https://github.com/aerogear/aerogear-push-helloworld/tree/1.0.x/android#2-register-application-with-push-services
>>>    ?
>>> Can you file JIRA for that ?
>>>
>>> yup and yup
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>> Here it's also important to test with Cordova, since we do have a new
>>>> version (1.0.2) out there:
>>>> http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.push
>>>>
>>>> Please also give the native apps a test-drive, even we had no new
>>>> release on the Push SDKs for Android and iOS since our 1.0.0 release in
>>>> August :-)
>>>>
>>>> If you want to test the new role, you will find some details here:
>>>> https://github.com/aerogear/aerogear.org/pull/411
>>>>
>>>> Thanks!
>>>> Matthias
>>>>
>>>>
>>>> On Fri, Oct 31, 2014 at 12:29 PM, Matthias Wessendorf <
>>>> matzew at apache.org> wrote:
>>>>
>>>>> Hello folks!
>>>>>
>>>>> here is another release, containing some fixes since the last 1.0.1
>>>>> release! Thanks to the team for all the hard work it put into this 1.0.2
>>>>> release!
>>>>>
>>>>> Here are a few highlights of this release:
>>>>> * Keycloak 1.0.4 usage
>>>>> * new developer role
>>>>> * documentation updates
>>>>> * SSLv3 version removed from docs
>>>>> * UI fixes and improvements
>>>>> * Polish UI to look nice(r) on mobile devices
>>>>>
>>>>> You'll find details on all the JIRAs can be found here:
>>>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/
>>>>>
>>>>> The staging repository is located here:
>>>>>
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/
>>>>>
>>>>>
>>>>> NOTE: Once this release has been approved the matching tag will be
>>>>> used to get the OpenShift online bits updated!
>>>>>
>>>>> Let me know the results of your testing!
>>>>> If I hear nothing bad by Tuesday evening, the release to maven central
>>>>> will happen on Wednesday morning;
>>>>>
>>>>> Greetings,
>>>>> Matthias
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20141031/03c9314b/attachment-0001.html 

From cvasilak at gmail.com  Fri Oct 31 14:18:31 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Fri, 31 Oct 2014 20:18:31 +0200
Subject: [aerogear-dev] [Vote] Release of UPS 1.0.2
In-Reply-To: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
References: <CAAg5f2SRPFY5VLgq4j3Ntx2NEJSatV8uoOom9gUBi2dcNG8EsQ@mail.gmail.com>
Message-ID: <53BFE455-96EE-4551-A9AF-E7C5A8210CBD@gmail.com>

Hi,

done the following:

- deployed on both 'jboss-eap-6.3' and 'wildfly-8.1.0.Final? servers using the provided instructions and worked fluently.
- tested iOS HelloWorld and Contacts Quickstart on both servers and worked fluently.
- enabled the ?developer? user plus added a new user with the ?developer' role, created applications and variants and the isolation works as expected. Only the admin user can see application from all users.

+1 for the release.

-
Christos




On Oct 31, 2014, at 1:29 PM, Matthias Wessendorf <matzew at apache.org> wrote:

> Hello folks!
> 
> here is another release, containing some fixes since the last 1.0.1 release! Thanks to the team for all the hard work it put into this 1.0.2 release!
> 
> Here are a few highlights of this release:
> * Keycloak 1.0.4 usage
> * new developer role
> * documentation updates
> * SSLv3 version removed from docs
> * UI fixes and improvements
> * Polish UI to look nice(r) on mobile devices
> 
> You'll find details on all the JIRAs can be found here:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/
> 
> The staging repository is located here:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4153/
> 
> 
> NOTE: Once this release has been approved the matching tag will be used to get the OpenShift online bits updated!
> 
> Let me know the results of your testing!
> If I hear nothing bad by Tuesday evening, the release to maven central will happen on Wednesday morning;
> 
> Greetings,
> Matthias
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141031/0d7b74a4/attachment.html