From daniel.bevenius at gmail.com Sun Feb 1 03:16:24 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 1 Feb 2015 09:16:24 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150202 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150201/083f6879/attachment-0001.html From harini.sekar at rntbci.com Sun Feb 1 23:31:48 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Mon, 2 Feb 2015 04:31:48 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C531DB7@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi , I want to know how to implement the REST API available for Aero Gear in application ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 02:08 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini > wrote: That?s great. When will be the new update will be released ? 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel I want to know why sending push notification dint work in that particular time. Whether it problem with the AeroGear server or IOS certificate ? It works now, right ? Not sure what the actual issue was, tbh Yes only 2 IOS devices are there. When I try to register android in aero gear , in some cases it gets registered twice with different device token but they have same alias names(device uuid). Is this a bug ? For your better understanding I have attached the screen shot below that happens after uninstall. if you than reintall, it gets a new token from Google. So you have two tokens, but that is really one device. Not a big deal. AFTER sending the payload to Google, the response from there gives us those tokens that we can remove from the DB. With this being merged soon, we also clean up those tokens in the uninstall case: https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 So, after the send, now, there should be only one. NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", after a send (invalid means the user removed the iOS app or disabled push on the user settings_ HTH, Matthias [cid:image001.png at 01D03ECF.420A7B80] From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 01:10 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error is that from now ? how many devices do you have, for iOS? I guess two ? We had a bug with incorrect numbers. That is fixed in the upcoming 1.0.3 release On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: It works. Then why this error occurred while sending notification to IOS devices Error: Problem occurred during sending push notification(s) Edit Push Network... ________________________________ Variants: IOS APNS Failed 2 installations Android Succeeded 4 installations IOS APNS Failed 2 installations From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of S?bastien Blanc Sent: 29 January 2015 PM 12:18 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Envoy? de mon iPhone Le 29 janv. 2015 ? 07:29, Sekar, Harini > a ?crit : Hi, Thank u so much ? If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? Yes , in the details you will even see it comes from the Java sender. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:37 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: Yes we are having proxy issue. How to set proxy for this APNS ? That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/2cc77442/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: image001.png Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/2cc77442/attachment-0001.png From matzew at apache.org Mon Feb 2 02:06:31 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 2 Feb 2015 08:06:31 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C531DB7@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C531DB7@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: Hi, What do you mean ? How to send a push notification out of your (backend) application ? If so, for Java based apps here is tutorial: https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ In case you are on Node, here are some more details on that: https://github.com/aerogear/aerogear-unifiedpush-nodejs-client HTH, Matthias On Mon, Feb 2, 2015 at 5:31 AM, Sekar, Harini wrote: > Hi , > > > > I want to know how to implement the REST API available for Aero Gear in > application ? > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 02:08 > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini > wrote: > > That?s great. When will be the new update will be released ? > > > > 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: > > > https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel > > > > I want to know why sending push notification dint work in that particular > time. > > Whether it problem with the AeroGear server or IOS certificate ? > > > > It works now, right ? Not sure what the actual issue was, tbh > > > > > > Yes only 2 IOS devices are there. > > When I try to register android in aero gear , in some cases it gets > registered twice with different device token but they have same alias > names(device uuid). Is this a bug ? > > For your better understanding I have attached the screen shot below > > > > that happens after uninstall. if you than reintall, it gets a new token > from Google. > > So you have two tokens, but that is really one device. Not a big deal. > > > > AFTER sending the payload to Google, the response from there gives us > those tokens that we can remove from the DB. With this being merged soon, > we also clean up those tokens in the uninstall case: > > https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 > > > > So, after the send, now, there should be only one. > > > > > > > > NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", > after a send (invalid means the user removed the iOS app or disabled push > on the user settings_ > > > > HTH, > > Matthias > > > > > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 01:10 > > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > is that from now ? > > > > how many devices do you have, for iOS? I guess two ? We had a bug with > incorrect numbers. That is fixed in the upcoming 1.0.3 release > > > > On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: > > It works. > > Then why this error occurred while sending notification to IOS devices > > > > Error: > > *Problem occurred during sending push notification(s)* > > *Edit Push Network... > * > ------------------------------ > > Variants: > > IOS APNS > > > Failed > > *2 installations* > > Android > > > Succeeded > > *4 installations* > > IOS APNS > > > Failed > > *2 installations* > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *S?bastien Blanc > *Sent:* 29 January 2015 PM 12:18 > *To:* AeroGear Developer Mailing List > > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > Envoy? de mon iPhone > > > Le 29 janv. 2015 ? 07:29, Sekar, Harini a > ?crit : > > Hi, > > > > Thank u so much J > > If I use Java sender client to send notification , then those activity > will be listed in the History link in the Aero Gear Admin UI ? > > > > Yes , in the details you will even see it comes from the Java sender. > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:37 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: > > Yes we are having proxy issue. How to set proxy for this APNS ? > > > > That's currently not supported on the Unified Push Server, but we track > the requirement in a ticket: > > https://issues.jboss.org/browse/AGPUSH-306 > > > > We didn't have much users requesting this, since usually they delpoy > the Unified Push Server where they have access to the internet. Otherwise > the device registration would be hard :-) > > > > -Matthias > > > > > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:32 > > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: > > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > > > > > > weird, I just tried this code: > > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > > > > and it works. Wondering, are you behind a firewall or so ? > > > > > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > > > > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/703e8baf/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/703e8baf/attachment-0001.png From matzew at apache.org Mon Feb 2 02:52:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 2 Feb 2015 08:52:15 +0100 Subject: [aerogear-dev] Amazon Device Messaging (ADM) support on UPS In-Reply-To: References: Message-ID: Nice job, Sebi. for the ADM client, I gave some review comments. Can you address them and afterwards let's release the first version to maven central. PS: I ordered FireTV :-) hehe On Thu, Jan 29, 2015 at 10:52 AM, Sebastien Blanc wrote: > Hi Folks, > > I've just submitted a PR to support ADM (Amazon Device Messaging) on > UPS[1] , yay ! > > A few notes : > > - The Java ADM connector is also managed by AeroGear [2], it's not yet > on Maven Central, so you will need to clone it and build it > - The Client SDK (and updated Cordova Plugin) is not yet available but > to make this PR testable, we have adapted a Cordova App that Amazon use as > sample to show ADM, this fork will register with UPS [3], this app contains > also all the instructions to get started > - About the client SDK, FireOS (Amazon's OS) is almost "just" Android, > so we should be able to reuse most of our Android Lib [4], we jsut need to > remove the GCM part and use the ADM library instead. I will start work on > that today and ping our Android gods to see which is the best way to do > that. > > So anyone who has a Amazon Tablet, please give it a shot and report on the > PR ! > > Have fun ! > > Sebi > > [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/480 > > [2] https://github.com/aerogear/java-adm > > [3] https://github.com/sebastienblanc/adm-cordova-sample > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/c7ed5020/attachment.html From matzew at apache.org Mon Feb 2 05:45:13 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 2 Feb 2015 11:45:13 +0100 Subject: [aerogear-dev] JIRA driven roadmaps Message-ID: Hi, on our homepage ([1]) we have some handwritten docs that cover the roadmap for parts of our components. These roadmaps contain a duplication of content that is available in JIRA. Since this content is handwritten, it's often not as up-to-date as it should be. Here are a few examples: * https://aerogear.org/docs/planning/roadmaps/AeroGeariOS/ * https://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ * https://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ Basically the contain incorrect dates and duplicate the list of effected JIRAs. But I wonder why we even do have these handwritten docs? JIRA itself has a roadmap overview, which looks nice and clean: https://issues.jboss.org/browse/AGIOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel https://issues.jboss.org/browse/AGDROID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel https://issues.jboss.org/browse/AGCORDOVA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel Since we track our issues, versions and releases in JIRA the above roadmaps comes for free. Now, when we change a release date in JIRA, using the above links as our roadmaps means we don't need to update the handwritten doc:-) Any thoughts? -Matthias [1] https://aerogear.org/docs/planning/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/160ac685/attachment.html From scm.blanc at gmail.com Mon Feb 2 06:15:49 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 2 Feb 2015 12:15:49 +0100 Subject: [aerogear-dev] JIRA driven roadmaps In-Reply-To: References: Message-ID: Sounds good and less error pone ! On Mon, Feb 2, 2015 at 11:45 AM, Matthias Wessendorf wrote: > Hi, > > on our homepage ([1]) we have some handwritten docs that cover the roadmap > for parts of our components. These roadmaps contain a duplication of > content that is available in JIRA. Since this content is handwritten, it's > often not as up-to-date as it should be. Here are a few examples: > > * https://aerogear.org/docs/planning/roadmaps/AeroGeariOS/ > * https://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ > * https://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ > > Basically the contain incorrect dates and duplicate the list of effected > JIRAs. But I wonder why we even do have these handwritten docs? > > JIRA itself has a roadmap overview, which looks nice and clean: > > > https://issues.jboss.org/browse/AGIOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > https://issues.jboss.org/browse/AGDROID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > https://issues.jboss.org/browse/AGCORDOVA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > Since we track our issues, versions and releases in JIRA the above > roadmaps comes for free. Now, when we change a release date in JIRA, using > the above links as our roadmaps means we don't need to update the > handwritten doc:-) > > Any thoughts? > > -Matthias > > [1] https://aerogear.org/docs/planning/ > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/4a554515/attachment.html From harini.sekar at rntbci.com Mon Feb 2 06:13:17 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Mon, 2 Feb 2015 11:13:17 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C531DB7@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C53219F@UK-EX-MBX-005.NMCorp.Nissan.Biz> Ok. In future do you going to support the phonegap build ? From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 02 February 2015 PM 12:37 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, What do you mean ? How to send a push notification out of your (backend) application ? If so, for Java based apps here is tutorial: https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ In case you are on Node, here are some more details on that: https://github.com/aerogear/aerogear-unifiedpush-nodejs-client HTH, Matthias On Mon, Feb 2, 2015 at 5:31 AM, Sekar, Harini > wrote: Hi , I want to know how to implement the REST API available for Aero Gear in application ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 02:08 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini > wrote: That?s great. When will be the new update will be released ? 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel I want to know why sending push notification dint work in that particular time. Whether it problem with the AeroGear server or IOS certificate ? It works now, right ? Not sure what the actual issue was, tbh Yes only 2 IOS devices are there. When I try to register android in aero gear , in some cases it gets registered twice with different device token but they have same alias names(device uuid). Is this a bug ? For your better understanding I have attached the screen shot below that happens after uninstall. if you than reintall, it gets a new token from Google. So you have two tokens, but that is really one device. Not a big deal. AFTER sending the payload to Google, the response from there gives us those tokens that we can remove from the DB. With this being merged soon, we also clean up those tokens in the uninstall case: https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 So, after the send, now, there should be only one. NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", after a send (invalid means the user removed the iOS app or disabled push on the user settings_ HTH, Matthias [cid:image001.png at 01D03F07.5863A270] From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 01:10 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error is that from now ? how many devices do you have, for iOS? I guess two ? We had a bug with incorrect numbers. That is fixed in the upcoming 1.0.3 release On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: It works. Then why this error occurred while sending notification to IOS devices Error: Problem occurred during sending push notification(s) Edit Push Network... ________________________________ Variants: IOS APNS Failed 2 installations Android Succeeded 4 installations IOS APNS Failed 2 installations From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of S?bastien Blanc Sent: 29 January 2015 PM 12:18 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Envoy? de mon iPhone Le 29 janv. 2015 ? 07:29, Sekar, Harini > a ?crit : Hi, Thank u so much ? If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? Yes , in the details you will even see it comes from the Java sender. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:37 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: Yes we are having proxy issue. How to set proxy for this APNS ? That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/c9935757/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: image001.png Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/c9935757/attachment-0001.png From cvasilak at gmail.com Mon Feb 2 06:41:40 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 2 Feb 2015 13:41:40 +0200 Subject: [aerogear-dev] Announcing iOS "Swift" SDK v2.1 Message-ID: <892E7CEE-2744-41AC-A322-CDDFA0F978A8@gmail.com> Hi AeroGear community, we are happy to announce the next versions of our iOS Swift libraries. Here are few of new features introduced in each respective lib: ? aerogear-ios-jsonsz (new) A newly introduced library which will take care the cumbersome plumbing required when performing JSON serialization back and forth from your Swift object model. Check out the documentation for an overview as well as our Buddies cookbook for example usage. ? aerogear-ios-http We added the ability to perform basic/digest authentication when performing REST requests. Check out the HTTP Basic/Digest authentication support?section in our library documentation as well as our Authentication cookbook for an example usage. Remember to prefer HTTPS over plain HTTP when performing authentication of this type! ? aerogear-ios-oauth2 Continuing the development of our OAuth2 library, OpenID Connect support was added to the library in the form of a login request. Check out the Login using OpenID Connect?section in our library?documentation as well as our SharedShoot cookbook example that logins to KeyCloak server using OpenID connect for an example usage. Further, Corinne blog posts here and here give more information regarding our OAuth2 implementation and is highly recommended if you are interested in the subject. ? aerogear-ios-httpstub Stubbed responses from the local file system can be used instead of coding them in your code. This will make easier to stub responses, especially big ones and be much ?closer? to the reality. Checkout out Stubbed response loaded from a file section in our library documentation for example usage as well as our tests . Last, this release introduces Cocoapod support for our libraries. Although Cocoapod hasn?t yet officially support ?Swift?, that is planned for the next 0.36 release, a branch on the project is working on it and already looks solid enough with many Swift libraries starting to adopt. Just make sure to install the 'pre' release version of cocoapods (Check the Cocoapods blog for more information). What's next? We are currently focusing most of our efforts on providing sync support. Already work has been started so expect more in-this front in the coming months. If you are interested in mobile-sync that is the perfect time to join us, we will be happy to know your thoughts and suggestions. Interesting things ahead of us..! So, give the libraries and demos a spin and let us know what you think! Have fun! AeroGear iOS team -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/b07a8534/attachment.html From matzew at apache.org Mon Feb 2 07:06:46 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 2 Feb 2015 13:06:46 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C53219F@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C531DB7@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C53219F@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: We have Cordova plugins, but I am not sure if that is compatible w/ Phonegab build On Mon, Feb 2, 2015 at 12:13 PM, Sekar, Harini wrote: > Ok. > > > > In future do you going to support the phonegap build ? > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 02 February 2015 PM 12:37 > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > What do you mean ? How to send a push notification out of your (backend) > application ? > > > > If so, for Java based apps here is tutorial: > > https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ > > > > In case you are on Node, here are some more details on that: > > https://github.com/aerogear/aerogear-unifiedpush-nodejs-client > > > > HTH, > > Matthias > > > > On Mon, Feb 2, 2015 at 5:31 AM, Sekar, Harini > wrote: > > Hi , > > > > I want to know how to implement the REST API available for Aero Gear in > application ? > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 02:08 > > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini > wrote: > > That?s great. When will be the new update will be released ? > > > > 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: > > > https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel > > > > I want to know why sending push notification dint work in that particular > time. > > Whether it problem with the AeroGear server or IOS certificate ? > > > > It works now, right ? Not sure what the actual issue was, tbh > > > > > > Yes only 2 IOS devices are there. > > When I try to register android in aero gear , in some cases it gets > registered twice with different device token but they have same alias > names(device uuid). Is this a bug ? > > For your better understanding I have attached the screen shot below > > > > that happens after uninstall. if you than reintall, it gets a new token > from Google. > > So you have two tokens, but that is really one device. Not a big deal. > > > > AFTER sending the payload to Google, the response from there gives us > those tokens that we can remove from the DB. With this being merged soon, > we also clean up those tokens in the uninstall case: > > https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 > > > > So, after the send, now, there should be only one. > > > > > > > > NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", > after a send (invalid means the user removed the iOS app or disabled push > on the user settings_ > > > > HTH, > > Matthias > > > > > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 01:10 > > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > is that from now ? > > > > how many devices do you have, for iOS? I guess two ? We had a bug with > incorrect numbers. That is fixed in the upcoming 1.0.3 release > > > > On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: > > It works. > > Then why this error occurred while sending notification to IOS devices > > > > Error: > > *Problem occurred during sending push notification(s)* > > *Edit Push Network... > * > ------------------------------ > > Variants: > > IOS APNS > > > Failed > > *2 installations* > > Android > > > Succeeded > > *4 installations* > > IOS APNS > > > Failed > > *2 installations* > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *S?bastien Blanc > *Sent:* 29 January 2015 PM 12:18 > *To:* AeroGear Developer Mailing List > > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > Envoy? de mon iPhone > > > Le 29 janv. 2015 ? 07:29, Sekar, Harini a > ?crit : > > Hi, > > > > Thank u so much J > > If I use Java sender client to send notification , then those activity > will be listed in the History link in the Aero Gear Admin UI ? > > > > Yes , in the details you will even see it comes from the Java sender. > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:37 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: > > Yes we are having proxy issue. How to set proxy for this APNS ? > > > > That's currently not supported on the Unified Push Server, but we track > the requirement in a ticket: > > https://issues.jboss.org/browse/AGPUSH-306 > > > > We didn't have much users requesting this, since usually they delpoy > the Unified Push Server where they have access to the internet. Otherwise > the device registration would be hard :-) > > > > -Matthias > > > > > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:32 > > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: > > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > > > > > > weird, I just tried this code: > > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > > > > and it works. Wondering, are you behind a firewall or so ? > > > > > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > > > > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/7bbd499d/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/7bbd499d/attachment-0001.png From matzew at apache.org Mon Feb 2 07:14:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 2 Feb 2015 13:14:37 +0100 Subject: [aerogear-dev] Announcing iOS "Swift" SDK v2.1 In-Reply-To: <892E7CEE-2744-41AC-A322-CDDFA0F978A8@gmail.com> References: <892E7CEE-2744-41AC-A322-CDDFA0F978A8@gmail.com> Message-ID: congrats!!! On Mon, Feb 2, 2015 at 12:41 PM, Christos Vasilakis wrote: > Hi AeroGear community, > > we are happy to announce the next versions of our iOS Swift libraries. > Here are few of new features introduced in each respective lib: > > *? *aerogear-ios-jsonsz > * (new)* > A newly introduced library which will take care the cumbersome plumbing > required when performing JSON serialization back and forth from your Swift > object model. Check out the documentation > for > an overview as well as our Buddies > cookbook for > example usage. > > *? *aerogear-ios-http > We added the ability to perform basic/digest authentication when > performing REST requests. Check out the HTTP Basic/Digest authentication > support section > in > our library documentation > as well as > our Authentication cookbook > for > an example usage. Remember to prefer HTTPS over plain HTTP when performing > authentication of this type! > > *? *aerogear-ios-oauth2 > Continuing the development of our OAuth2 library, OpenID Connect support > was added to the library in the form of a login request. Check out the Login > using OpenID Connect section > in > our library documentation > as > well as our SharedShoot > cookbook example > that logins to KeyCloak server using OpenID connect for an example usage. > Further, Corinne blog posts here > > and here > give > more information regarding our OAuth2 implementation and is highly > recommended if you are interested in the subject. > > ? aerogear-ios-httpstub > > Stubbed responses from the local file system can be used instead of coding > them in your code. This will make easier to stub responses, especially big > ones and be much ?closer? to the reality. Checkout out Stubbed response > loaded from a file > section > in our library documentation > for example > usage as well as our tests > > . > > Last, this release introduces Cocoapod support for our libraries. Although > Cocoapod hasn?t yet officially support ?Swift?, that is planned for the > next 0.36 release, a branch on the project is working on it and > already looks solid enough with many Swift libraries starting to adopt. > Just make sure to install the 'pre' release version of cocoapods (Check the Cocoapods > blog > for > more information). > > *What's next?* > We are currently focusing most of our efforts on providing sync support. > Already work has been started > so expect more in-this > front in the coming months. If you are interested in mobile-sync that is > the perfect time to join us, we will be happy to know your thoughts and > suggestions. Interesting things ahead of us..! > > So, give the libraries and demos a spin and let us know what you think! > > Have fun! > > AeroGear iOS team > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/57839497/attachment.html From corinnekrych at gmail.com Mon Feb 2 07:43:11 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 2 Feb 2015 13:43:11 +0100 Subject: [aerogear-dev] JIRA driven roadmaps In-Reply-To: References: Message-ID: <4239F885-197D-463F-893E-C5CF72B4CF29@gmail.com> I like the roadmap JIRA view +1 to have only JIRA ++ Corinne > On 02 Feb 2015, at 11:45, Matthias Wessendorf wrote: > > Hi, > > on our homepage ([1]) we have some handwritten docs that cover the roadmap for parts of our components. These roadmaps contain a duplication of content that is available in JIRA. Since this content is handwritten, it's often not as up-to-date as it should be. Here are a few examples: > > * https://aerogear.org/docs/planning/roadmaps/AeroGeariOS/ > * https://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ > * https://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ > > Basically the contain incorrect dates and duplicate the list of effected JIRAs. But I wonder why we even do have these handwritten docs? > > JIRA itself has a roadmap overview, which looks nice and clean: > > https://issues.jboss.org/browse/AGIOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > https://issues.jboss.org/browse/AGDROID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > https://issues.jboss.org/browse/AGCORDOVA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > Since we track our issues, versions and releases in JIRA the above roadmaps comes for free. Now, when we change a release date in JIRA, using the above links as our roadmaps means we don't need to update the handwritten doc:-) > > Any thoughts? > > -Matthias > > [1] https://aerogear.org/docs/planning/ > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From daniel at passos.me Mon Feb 2 07:48:17 2015 From: daniel at passos.me (Daniel Passos) Date: Mon, 2 Feb 2015 10:48:17 -0200 Subject: [aerogear-dev] JIRA driven roadmaps In-Reply-To: <4239F885-197D-463F-893E-C5CF72B4CF29@gmail.com> References: <4239F885-197D-463F-893E-C5CF72B4CF29@gmail.com> Message-ID: +1 for JIra -- Passos On Mon, Feb 2, 2015 at 10:43 AM, Corinne Krych wrote: > I like the roadmap JIRA view > +1 to have only JIRA > > ++ > Corinne > > On 02 Feb 2015, at 11:45, Matthias Wessendorf wrote: > > > > Hi, > > > > on our homepage ([1]) we have some handwritten docs that cover the > roadmap for parts of our components. These roadmaps contain a duplication > of content that is available in JIRA. Since this content is handwritten, > it's often not as up-to-date as it should be. Here are a few examples: > > > > * https://aerogear.org/docs/planning/roadmaps/AeroGeariOS/ > > * https://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ > > * https://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ > > > > Basically the contain incorrect dates and duplicate the list of effected > JIRAs. But I wonder why we even do have these handwritten docs? > > > > JIRA itself has a roadmap overview, which looks nice and clean: > > > > > https://issues.jboss.org/browse/AGIOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > > https://issues.jboss.org/browse/AGDROID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > > https://issues.jboss.org/browse/AGCORDOVA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > > > Since we track our issues, versions and releases in JIRA the above > roadmaps comes for free. Now, when we change a release date in JIRA, using > the above links as our roadmaps means we don't need to update the > handwritten doc:-) > > > > Any thoughts? > > > > -Matthias > > > > [1] https://aerogear.org/docs/planning/ > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/a16290a8/attachment.html From matzew at apache.org Mon Feb 2 09:53:38 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 2 Feb 2015 15:53:38 +0100 Subject: [aerogear-dev] Data Sync meeting Message-ID: Hi, we had a little google hangout for our work on SYNC. Here are the meeting minutes: http://oksoclap.com/p/sync_meeting_2ndFebruary_2015 -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/20150202/bade3696/attachment.html From cvasilak at gmail.com Mon Feb 2 10:08:49 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 2 Feb 2015 17:08:49 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Mon Feb 2 15:06:19 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-02-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-02-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-02-15.00.log.html > On Feb 1, 2015, at 10:16 AM, Daniel Bevenius wrote: > > Agenda: > > http://oksoclap.com/p/aerogear-team-mgt-20150202 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/2f1a63cb/attachment-0001.html From scm.blanc at gmail.com Mon Feb 2 10:20:25 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 2 Feb 2015 16:20:25 +0100 Subject: [aerogear-dev] Chrome Push Messages In-Reply-To: References: <60194944-06DE-44BF-AEF4-B729DF9B5E69@redhat.com> Message-ID: Hi, Just bumping up this thread since https://github.com/aerogear/aerogear-unifiedpush-server/pull/483 has been merged . Do we still plan to change also the wording/flow for the now called variant "Android" ? To something like GCM ? (Check this thread) Is this the related jira https://issues.jboss.org/browse/AGPUSH-928 ? Sebi On Fri, Sep 5, 2014 at 12:38 PM, Daniel Passos wrote: > +1 to GCM logo > On Sep 3, 2014 5:28 PM, "S?bastien Blanc" wrote: > >> Looks like there is a gcm logo but it is not really nice and I can not >> find it with a decent resolution >> [image: logo.png] >> >> Envoy? de mon iPhone >> >> Le 3 sept. 2014 ? 21:32, Luk?? Fry? a ?crit : >> >> From the UI perspective, Android/Chrome merge has few options: >> >> 1. merged half-Android / half-Chrome logo (+ "Android / Chrome" as a >> description) >> >> 2. use one radio button, but two rows with two logos (Android, Chrome) >> >> 3. use Google logo ("G"? [1]) (and "Google Cloud Messaging" description) >> >> >> Anyway, in any case it won't be as nice and polished as it is now. :-) >> >> >> [1] >> https://www.google.com/search?q=g+google&source=lnms&tbm=isch&sa=X&ei=kWsHVILKJsn8yQSO9IDoCQ&ved=0CAoQ_AUoAw&biw=1283&bih=861 >> >> >> On Wed, Sep 3, 2014 at 7:48 PM, Lucas Holmquist >> wrote: >> >>> So to follow up on this, >>> >>> >>> Chrome Packaged Applications, no recommend to use the same GCM network >>> for Android when sending push notifications. >>> >>> Currently in the UnifiedPush Server, a user can use the Android variant >>> to use this new API now. >>> >>> I think we should rename the AndroidVariant.class and related stuff to >>> GCMVariant . >>> >>> I created this Task to track the changes, >>> https://issues.jboss.org/browse/AGPUSH-928 since we need to deprecate >>> the current Chrome implementation and update the UI?s for the new way. >>> >>> i?m wondering for the ?Create Variant? dialog, for Android, we would >>> need to change the name to GCM, but for the icon?s i wonder how it would >>> look to put both Android and Chrome icons, side by side >>> >>> >>> On Aug 27, 2014, at 2:19 PM, Lucas Holmquist >>> wrote: >>> >>> >>> On Aug 27, 2014, at 2:15 PM, Luk?? Fry? wrote: >>> >>> Hey Luke, >>> >>> ad) Variants >>> >>> it would be ideal if we could just use the same variant! >>> >>> >>> yea, it?s looking like it will be the same thing, we might just have >>> to make a note of it on the UI >>> >>> >>> >>> ad) Compatibility >>> >>> I would say we should preserve the compatibility with 1.x as long as it >>> does not make much efforts to keep both supported. >>> >>> >>> If it would be too much hassle, let's remove it in 1.1. >>> Chrome is updated pro-actively anyway, so no one will hear about the old >>> API in few months. >>> >>> >>> exactly, so maybe a warning or something >>> >>> >>> >>> Cheers, >>> >>> ~ Lukas >>> >>> >>> On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist >>> wrote: >>> >>>> Hello, >>>> >>>> now that the 1.0.0-final is pretty much out for the UnifiedPush Server, >>>> i?m starting to look at the new API that Chrome apps use for sending push >>>> notifications. >>>> >>>> the TL;DR of it is, it?s basically the same as Android now.( no more >>>> refresh tokens and access tokens and such ) >>>> >>>> So the question is, do we need to have a deprecation period on what is >>>> currently there? >>>> >>>> The v1 of the chrome pushMessaging api has become legacy and it is >>>> recommended to use the new stuff. >>>> https://developer.chrome.com/apps/cloudMessagingV1 >>>> >>>> While i have looked to deeply, it?s possible we can use the same >>>> ?Variant? structure for Chrome Apps, Since they will be using the same >>>> Network >>>> >>>> wdyt? >>>> >>>> -Luke >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150202/f4017293/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 3926 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150202/f4017293/attachment.png From lholmqui at redhat.com Mon Feb 2 10:28:23 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 2 Feb 2015 10:28:23 -0500 Subject: [aerogear-dev] Chrome Push Messages In-Reply-To: References: <60194944-06DE-44BF-AEF4-B729DF9B5E69@redhat.com> Message-ID: <07969DD1-19BD-4A5E-8946-4768B9411D10@redhat.com> > On Feb 2, 2015, at 10:20 AM, Sebastien Blanc wrote: > > Hi, > > Just bumping up this thread since https://github.com/aerogear/aerogear-unifiedpush-server/pull/483 has been merged . > Do we still plan to change also the wording/flow for the now called variant "Android" ? To something like GCM ? (Check this thread) > Is this the related jira https://issues.jboss.org/browse/AGPUSH-928 ? Me and matzew discussed this a bit and i think it no longer makes sense to change it. I think the effort to change this and migrate is not worth it. > > Sebi > > > > On Fri, Sep 5, 2014 at 12:38 PM, Daniel Passos > wrote: > +1 to GCM logo > > On Sep 3, 2014 5:28 PM, "S?bastien Blanc" > wrote: > Looks like there is a gcm logo but it is not really nice and I can not find it with a decent resolution > > > Envoy? de mon iPhone > > Le 3 sept. 2014 ? 21:32, Luk?? Fry? > a ?crit : > >> From the UI perspective, Android/Chrome merge has few options: >> >> 1. merged half-Android / half-Chrome logo (+ "Android / Chrome" as a description) >> >> 2. use one radio button, but two rows with two logos (Android, Chrome) >> >> 3. use Google logo ("G"? [1]) (and "Google Cloud Messaging" description) >> >> >> Anyway, in any case it won't be as nice and polished as it is now. :-) >> >> >> [1] https://www.google.com/search?q=g+google&source=lnms&tbm=isch&sa=X&ei=kWsHVILKJsn8yQSO9IDoCQ&ved=0CAoQ_AUoAw&biw=1283&bih=861 >> >> >> On Wed, Sep 3, 2014 at 7:48 PM, Lucas Holmquist > wrote: >> So to follow up on this, >> >> >> Chrome Packaged Applications, no recommend to use the same GCM network for Android when sending push notifications. >> >> Currently in the UnifiedPush Server, a user can use the Android variant to use this new API now. >> >> I think we should rename the AndroidVariant.class and related stuff to GCMVariant . >> >> I created this Task to track the changes, https://issues.jboss.org/browse/AGPUSH-928 since we need to deprecate the current Chrome implementation and update the UI?s for the new way. >> >> i?m wondering for the ?Create Variant? dialog, for Android, we would need to change the name to GCM, but for the icon?s i wonder how it would look to put both Android and Chrome icons, side by side >> >> >> On Aug 27, 2014, at 2:19 PM, Lucas Holmquist > wrote: >> >>> >>> On Aug 27, 2014, at 2:15 PM, Luk?? Fry? > wrote: >>> >>>> Hey Luke, >>>> >>>> ad) Variants >>>> >>>> it would be ideal if we could just use the same variant! >>> >>> yea, it?s looking like it will be the same thing, we might just have to make a note of it on the UI >>>> >>>> >>>> ad) Compatibility >>>> >>>> I would say we should preserve the compatibility with 1.x as long as it does not make much efforts to keep both supported. >>>> >>>> If it would be too much hassle, let's remove it in 1.1. >>>> Chrome is updated pro-actively anyway, so no one will hear about the old API in few months. >>> >>> exactly, so maybe a warning or something >>>> >>>> >>>> Cheers, >>>> >>>> ~ Lukas >>>> >>>> >>>> On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist > wrote: >>>> Hello, >>>> >>>> now that the 1.0.0-final is pretty much out for the UnifiedPush Server, i?m starting to look at the new API that Chrome apps use for sending push notifications. >>>> >>>> the TL;DR of it is, it?s basically the same as Android now.( no more refresh tokens and access tokens and such ) >>>> >>>> So the question is, do we need to have a deprecation period on what is currently there? >>>> >>>> The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. https://developer.chrome.com/apps/cloudMessagingV1 >>>> >>>> While i have looked to deeply, it?s possible we can use the same ?Variant? structure for Chrome Apps, Since they will be using the same Network >>>> >>>> wdyt? >>>> >>>> -Luke >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150202/6171ea73/attachment-0001.html From scm.blanc at gmail.com Mon Feb 2 12:31:20 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Mon, 2 Feb 2015 18:31:20 +0100 Subject: [aerogear-dev] Chrome Push Messages In-Reply-To: <07969DD1-19BD-4A5E-8946-4768B9411D10@redhat.com> References: <60194944-06DE-44BF-AEF4-B729DF9B5E69@redhat.com> <07969DD1-19BD-4A5E-8946-4768B9411D10@redhat.com> Message-ID: <1175C73A-C927-4CDE-9C85-B3AEAF073461@gmail.com> Envoy? de mon iPhone > Le 2 f?vr. 2015 ? 16:28, Lucas Holmquist a ?crit : > > >> On Feb 2, 2015, at 10:20 AM, Sebastien Blanc wrote: >> >> Hi, >> >> Just bumping up this thread since https://github.com/aerogear/aerogear-unifiedpush-server/pull/483 has been merged . >> Do we still plan to change also the wording/flow for the now called variant "Android" ? To something like GCM ? (Check this thread) >> Is this the related jira https://issues.jboss.org/browse/AGPUSH-928 ? > > Me and matzew discussed this a bit and i think it no longer makes sense to change it. I think the effort to change this and migrate is not worth it. Make sense. Same for APNs with Safari/macOS I presume ? > > > > > >> >> Sebi >> >> >> >>> On Fri, Sep 5, 2014 at 12:38 PM, Daniel Passos wrote: >>> +1 to GCM logo >>> >>>> On Sep 3, 2014 5:28 PM, "S?bastien Blanc" wrote: >>>> Looks like there is a gcm logo but it is not really nice and I can not find it with a decent resolution >>>> >>>> >>>> Envoy? de mon iPhone >>>> >>>>> Le 3 sept. 2014 ? 21:32, Luk?? Fry? a ?crit : >>>>> >>>>> From the UI perspective, Android/Chrome merge has few options: >>>>> >>>>> 1. merged half-Android / half-Chrome logo (+ "Android / Chrome" as a description) >>>>> >>>>> 2. use one radio button, but two rows with two logos (Android, Chrome) >>>>> >>>>> 3. use Google logo ("G"? [1]) (and "Google Cloud Messaging" description) >>>>> >>>>> >>>>> Anyway, in any case it won't be as nice and polished as it is now. :-) >>>>> >>>>> >>>>> [1] https://www.google.com/search?q=g+google&source=lnms&tbm=isch&sa=X&ei=kWsHVILKJsn8yQSO9IDoCQ&ved=0CAoQ_AUoAw&biw=1283&bih=861 >>>>> >>>>> >>>>>> On Wed, Sep 3, 2014 at 7:48 PM, Lucas Holmquist wrote: >>>>>> So to follow up on this, >>>>>> >>>>>> >>>>>> Chrome Packaged Applications, no recommend to use the same GCM network for Android when sending push notifications. >>>>>> >>>>>> Currently in the UnifiedPush Server, a user can use the Android variant to use this new API now. >>>>>> >>>>>> I think we should rename the AndroidVariant.class and related stuff to GCMVariant . >>>>>> >>>>>> I created this Task to track the changes, https://issues.jboss.org/browse/AGPUSH-928 since we need to deprecate the current Chrome implementation and update the UI?s for the new way. >>>>>> >>>>>> i?m wondering for the ?Create Variant? dialog, for Android, we would need to change the name to GCM, but for the icon?s i wonder how it would look to put both Android and Chrome icons, side by side >>>>>> >>>>>> >>>>>>> On Aug 27, 2014, at 2:19 PM, Lucas Holmquist wrote: >>>>>>> >>>>>>> >>>>>>>> On Aug 27, 2014, at 2:15 PM, Luk?? Fry? wrote: >>>>>>>> >>>>>>>> Hey Luke, >>>>>>>> >>>>>>>> ad) Variants >>>>>>>> >>>>>>>> it would be ideal if we could just use the same variant! >>>>>>> >>>>>>> yea, it?s looking like it will be the same thing, we might just have to make a note of it on the UI >>>>>>>> >>>>>>>> >>>>>>>> ad) Compatibility >>>>>>>> >>>>>>>> I would say we should preserve the compatibility with 1.x as long as it does not make much efforts to keep both supported. >>>>>>>> >>>>>>>> If it would be too much hassle, let's remove it in 1.1. >>>>>>>> Chrome is updated pro-actively anyway, so no one will hear about the old API in few months. >>>>>>> >>>>>>> exactly, so maybe a warning or something >>>>>>>> >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> ~ Lukas >>>>>>>> >>>>>>>> >>>>>>>>> On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist wrote: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> now that the 1.0.0-final is pretty much out for the UnifiedPush Server, i?m starting to look at the new API that Chrome apps use for sending push notifications. >>>>>>>>> >>>>>>>>> the TL;DR of it is, it?s basically the same as Android now.( no more refresh tokens and access tokens and such ) >>>>>>>>> >>>>>>>>> So the question is, do we need to have a deprecation period on what is currently there? >>>>>>>>> >>>>>>>>> The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. https://developer.chrome.com/apps/cloudMessagingV1 >>>>>>>>> >>>>>>>>> While i have looked to deeply, it?s possible we can use the same ?Variant? structure for Chrome Apps, Since they will be using the same Network >>>>>>>>> >>>>>>>>> wdyt? >>>>>>>>> >>>>>>>>> -Luke >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150202/5bac29c0/attachment.html From lholmqui at redhat.com Mon Feb 2 12:38:39 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 2 Feb 2015 12:38:39 -0500 Subject: [aerogear-dev] Chrome Push Messages In-Reply-To: <1175C73A-C927-4CDE-9C85-B3AEAF073461@gmail.com> References: <60194944-06DE-44BF-AEF4-B729DF9B5E69@redhat.com> <07969DD1-19BD-4A5E-8946-4768B9411D10@redhat.com> <1175C73A-C927-4CDE-9C85-B3AEAF073461@gmail.com> Message-ID: <16ED6A48-55A8-4229-AC7A-7EA83B7026F5@redhat.com> > On Feb 2, 2015, at 12:31 PM, S?bastien Blanc wrote: > > > > Envoy? de mon iPhone > > Le 2 f?vr. 2015 ? 16:28, Lucas Holmquist > a ?crit : > >> >>> On Feb 2, 2015, at 10:20 AM, Sebastien Blanc > wrote: >>> >>> Hi, >>> >>> Just bumping up this thread since https://github.com/aerogear/aerogear-unifiedpush-server/pull/483 has been merged . >>> Do we still plan to change also the wording/flow for the now called variant "Android" ? To something like GCM ? (Check this thread) >>> Is this the related jira https://issues.jboss.org/browse/AGPUSH-928 ? >> >> Me and matzew discussed this a bit and i think it no longer makes sense to change it. I think the effort to change this and migrate is not worth it. > Make sense. Same for APNs with Safari/macOS I presume ? i think that is probably a fair statement. There are 2 differences, the first is that safari push needs a production cert. the second is the payload is in a slightly different format, but that the library we use for apns supports it(i actually sent the PR for that :)) So i think doc updates are really the only thing, he majority of the work that goes into setting up safari push is not ups related. Let me try it out with the existing iOS variant and then i?ll update JIRA's >> > >> >> >> >> >>> >>> Sebi >>> >>> >>> >>> On Fri, Sep 5, 2014 at 12:38 PM, Daniel Passos > wrote: >>> +1 to GCM logo >>> >>> On Sep 3, 2014 5:28 PM, "S?bastien Blanc" > wrote: >>> Looks like there is a gcm logo but it is not really nice and I can not find it with a decent resolution >>> >>> >>> Envoy? de mon iPhone >>> >>> Le 3 sept. 2014 ? 21:32, Luk?? Fry? > a ?crit : >>> >>>> From the UI perspective, Android/Chrome merge has few options: >>>> >>>> 1. merged half-Android / half-Chrome logo (+ "Android / Chrome" as a description) >>>> >>>> 2. use one radio button, but two rows with two logos (Android, Chrome) >>>> >>>> 3. use Google logo ("G"? [1]) (and "Google Cloud Messaging" description) >>>> >>>> >>>> Anyway, in any case it won't be as nice and polished as it is now. :-) >>>> >>>> >>>> [1] https://www.google.com/search?q=g+google&source=lnms&tbm=isch&sa=X&ei=kWsHVILKJsn8yQSO9IDoCQ&ved=0CAoQ_AUoAw&biw=1283&bih=861 >>>> >>>> >>>> On Wed, Sep 3, 2014 at 7:48 PM, Lucas Holmquist > wrote: >>>> So to follow up on this, >>>> >>>> >>>> Chrome Packaged Applications, no recommend to use the same GCM network for Android when sending push notifications. >>>> >>>> Currently in the UnifiedPush Server, a user can use the Android variant to use this new API now. >>>> >>>> I think we should rename the AndroidVariant.class and related stuff to GCMVariant . >>>> >>>> I created this Task to track the changes, https://issues.jboss.org/browse/AGPUSH-928 since we need to deprecate the current Chrome implementation and update the UI?s for the new way. >>>> >>>> i?m wondering for the ?Create Variant? dialog, for Android, we would need to change the name to GCM, but for the icon?s i wonder how it would look to put both Android and Chrome icons, side by side >>>> >>>> >>>> On Aug 27, 2014, at 2:19 PM, Lucas Holmquist > wrote: >>>> >>>>> >>>>> On Aug 27, 2014, at 2:15 PM, Luk?? Fry? > wrote: >>>>> >>>>>> Hey Luke, >>>>>> >>>>>> ad) Variants >>>>>> >>>>>> it would be ideal if we could just use the same variant! >>>>> >>>>> yea, it?s looking like it will be the same thing, we might just have to make a note of it on the UI >>>>>> >>>>>> >>>>>> ad) Compatibility >>>>>> >>>>>> I would say we should preserve the compatibility with 1.x as long as it does not make much efforts to keep both supported. >>>>>> >>>>>> If it would be too much hassle, let's remove it in 1.1. >>>>>> Chrome is updated pro-actively anyway, so no one will hear about the old API in few months. >>>>> >>>>> exactly, so maybe a warning or something >>>>>> >>>>>> >>>>>> Cheers, >>>>>> >>>>>> ~ Lukas >>>>>> >>>>>> >>>>>> On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist > wrote: >>>>>> Hello, >>>>>> >>>>>> now that the 1.0.0-final is pretty much out for the UnifiedPush Server, i?m starting to look at the new API that Chrome apps use for sending push notifications. >>>>>> >>>>>> the TL;DR of it is, it?s basically the same as Android now.( no more refresh tokens and access tokens and such ) >>>>>> >>>>>> So the question is, do we need to have a deprecation period on what is currently there? >>>>>> >>>>>> The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. https://developer.chrome.com/apps/cloudMessagingV1 >>>>>> >>>>>> While i have looked to deeply, it?s possible we can use the same ?Variant? structure for Chrome Apps, Since they will be using the same Network >>>>>> >>>>>> wdyt? >>>>>> >>>>>> -Luke >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150202/8b46d6b5/attachment-0001.html From bruno at abstractj.org Mon Feb 2 13:00:20 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 2 Feb 2015 16:00:20 -0200 Subject: [aerogear-dev] Easy access to security related documentation Message-ID: <20150202180020.GA1899@abstractj.org> Good morning, I would like to suggest a new structure to all the documents related with security. We have a great content on aerogear.org, at the same time, hard to find. Because some items are located at guides sections, others can be found at specs section. That said I would like to suggest the following section under "guides" section. - Security - Cryptography (Include a documentation revamped and revisited), usage instructions and etc - Authentication and Authorization - Client - Using OAuth2 with Android - Using OAuth2 with iOS - Using OAuth2 with JavaScript - Server - How to setup the server and references to Keycloak I don't want to drop any documentation already done, only to revisit, organize and improve. Thoughts? -- abstractj PGP: 0x84DC9914 From bruno at abstractj.org Mon Feb 2 14:28:33 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 2 Feb 2015 17:28:33 -0200 Subject: [aerogear-dev] iOS SDK for OAuth2 Message-ID: <20150202192833.GA20797@abstractj.org> Good morning, I was reviewing our SDK for iOS and I have few questions: 1. For example at Shoot app. Why our users have to configure to insert the app ID at Shoot-Info.plist and also insert the same app ID at ViewController? I was just wondering that once the app ID is informed, you don't need to inform it again. 2. We have a note: "Because this demo securely stores OAuth2 tokens in your iOS keychain, we chosen to use WhenPasscodeSet policy as a result to run this app you need to have your passcode set" I think that's amazing, but at the same time we instruct our devs, to insert the client secret hard coded into the app. Something like: let facebookConfig = FacebookConfig( clientId: "XXXXXX", clientSecret: "42", scopes:["photo_upload, publish_actions"]) Doing the reverse engineering of the app, would permit me to get the secret and mimic your FB app. So I would like to remove the need to input the same information twice and encrypt the client secret using password based encryption. Let me know what do you think and I will start to file Jiras to myself. Note: This is not an issue specific to iOS. All the projects will get the same love and feedback. -- abstractj PGP: 0x84DC9914 From agalante at redhat.com Mon Feb 2 22:24:03 2015 From: agalante at redhat.com (Andres Galante) Date: Mon, 2 Feb 2015 22:24:03 -0500 (EST) Subject: [aerogear-dev] Post for jboss blog In-Reply-To: <1652965494.3817643.1422933740293.JavaMail.zimbra@redhat.com> Message-ID: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> I wrote this for joboss blog: https://gist.github.com/andresgalante/32485438e2c64f2127ba I wanted to share before I send it in case someone has a few minutes to read it and send feedback. Thanks! Andr?s From jowilson at redhat.com Mon Feb 2 23:44:35 2015 From: jowilson at redhat.com (Joshua Wilson) Date: Mon, 2 Feb 2015 23:44:35 -0500 (EST) Subject: [aerogear-dev] Post for jboss blog In-Reply-To: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> Message-ID: <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> It looks great! Here are my comments. - The following sentence needs to be rewritten. "Currently users count with extensive documentation to set up Unified Push Console." My guess is that the "with" should be "on". - The last word needs an "s". "This might sound exaggerated adulation, truth is I really do enjoy working with developer." Change "developer" to "developers". - Since you use "UPS" later on you need to add it the end of this sentence. "I've been given the challenge to redesign Aerogear Unified Push Console." Add on "(UPS)". - Is this correct? "Install a client code" In English the use of "a" indicates that it is a specific thing instead of programming code. It reads like I need to enter "352245". - Personally I feel that this sentence is demeaning to the user and the innuendo on the end is inappropriate for jboss.org "Yeah, we have high expectations from our users. It isn't an easy job, and we need to hold their hands and head them to a happy ending." But that just may be prudish nature. - Who do you intend to read this? If it is your intended user (of if you think your intended user may ever read it) the overall tone is demeaning to users. You are running the risk of pushing (no pun intended) users away. You start out calling them children, then say they are too dumb to follow your step to create it, then you say they do not enough attention and focus to use the tool. It is one thing for you to think that way, it is another to tell them to their face. To be clear, I am not on the Aerogear team. I'm just providing the perspective of a potential user. I also believe that you do not intend to offend, that is why I am offering this insight. - Consider rewording "We only count with a fraction of a seconds to make a good first impression and just a couple of seconds to grab their attention." to "We only have a fraction of a second to make a good first impression and just a couple of seconds to grab their attention." - Consider rewording "For UPS console" to "For the UPS console" - Please change "an" to "and" in "complete the 5 steps to get push notifications up an running. " - I am not sure but think you need a dash between "on bording" in "A successful on boarding strategy is like". - Consider rewording "As parents we need to encourage to teach themselves and learn their own way." to include a "them" here "to encourage them to teach". - Consider changing "Alan Coopers teach us that main goal of a UX design is to never make the user feel stupid." to "Alan Cooper teaches us that the main goal of a UX design is to never make the user feel stupid" (as a side note, he makes my point for me :P ) I mean not offense by my edits or comments. I think it great that you wrote this up. Keep writing (and coding/designing). Joshua Wilson ----- Original Message ----- From: "Andres Galante [via aerogear-dev]" To: "joshuaw" Sent: Monday, February 2, 2015 10:24:37 PM Subject: [aerogear-dev] Post for jboss blog I wrote this for joboss blog: https://gist.github.com/andresgalante/32485438e2c64f2127ba I wanted to share before I send it in case someone has a few minutes to read it and send feedback. Thanks! Andr?s _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ If you reply to this email, your message will be added to the discussion below: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Post-for-jboss-blog-tp10770.html To start a new topic under aerogear-dev, email ml-node+s1069024n1h46 at n5.nabble.com To unsubscribe from aerogear-dev, visit http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2 From jowilson at redhat.com Mon Feb 2 23:44:43 2015 From: jowilson at redhat.com (joshuaw) Date: Mon, 2 Feb 2015 21:44:43 -0700 (MST) Subject: [aerogear-dev] Post for jboss blog Message-ID: <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> It looks great! Here are my comments. - The following sentence needs to be rewritten. "Currently users count with extensive documentation to set up Unified Push Console." My guess is that the "with" should be "on". - The last word needs an "s". "This might sound exaggerated adulation, truth is I really do enjoy working with developer." Change "developer" to "developers". - Since you use "UPS" later on you need to add it the end of this sentence. "I've been given the challenge to redesign Aerogear Unified Push Console." Add on "(UPS)". - Is this correct? "Install a client code" In English the use of "a" indicates that it is a specific thing instead of programming code. It reads like I need to enter "352245". - Personally I feel that this sentence is demeaning to the user and the innuendo on the end is inappropriate for jboss.org "Yeah, we have high expectations from our users. It isn't an easy job, and we need to hold their hands and head them to a happy ending." But that just may be prudish nature. - Who do you intend to read this? If it is your intended user (of if you think your intended user may ever read it) the overall tone is demeaning to users. You are running the risk of pushing (no pun intended) users away. You start out calling them children, then say they are too dumb to follow your step to create it, then you say they do not enough attention and focus to use the tool. It is one thing for you to think that way, it is another to tell them to their face. To be clear, I am not on the Aerogear team. I'm just providing the perspective of a potential user. I also believe that you do not intend to offend, that is why I am offering this insight. - Consider rewording "We only count with a fraction of a seconds to make a good first impression and just a couple of seconds to grab their attention." to "We only have a fraction of a second to make a good first impression and just a couple of seconds to grab their attention." - Consider rewording "For UPS console" to "For the UPS console" - Please change "an" to "and" in "complete the 5 steps to get push notifications up an running. " - I am not sure but think you need a dash between "on bording" in "A successful on boarding strategy is like". - Consider rewording "As parents we need to encourage to teach themselves and learn their own way." to include a "them" here "to encourage them to teach". - Consider changing "Alan Coopers teach us that main goal of a UX design is to never make the user feel stupid." to "Alan Cooper teaches us that the main goal of a UX design is to never make the user feel stupid" (as a side note, he makes my point for me :P ) I mean not offense by my edits or comments. I think it great that you wrote this up. Keep writing (and coding/designing). Joshua Wilson ----- Original Message ----- From: "Andres Galante [via aerogear-dev]" To: "joshuaw" Sent: Monday, February 2, 2015 10:24:37 PM Subject: [aerogear-dev] Post for jboss blog I wrote this for joboss blog: https://gist.github.com/andresgalante/32485438e2c64f2127ba I wanted to share before I send it in case someone has a few minutes to read it and send feedback. Thanks! Andr?s _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ If you reply to this email, your message will be added to the discussion below: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Post-for-jboss-blog-tp10770.html To start a new topic under aerogear-dev, email ml-node+s1069024n1h46 at n5.nabble.com To unsubscribe from aerogear-dev, visit http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2 -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Re-aerogear-dev-Post-for-jboss-blog-tp10771.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/20150202/8364eabb/attachment.html From matzew at apache.org Tue Feb 3 01:37:55 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 07:37:55 +0100 Subject: [aerogear-dev] Post for jboss blog In-Reply-To: <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Feb 3, 2015 at 5:44 AM, Joshua Wilson wrote: > It looks great! Here are my comments. > > - The following sentence needs to be rewritten. "Currently users count > with extensive documentation to set up Unified Push Console." My guess is > that the "with" should be "on". > - The last word needs an "s". "This might sound exaggerated adulation, > truth is I really do enjoy working with developer." Change "developer" to > "developers". > - Since you use "UPS" later on you need to add it the end of this > sentence. "I've been given the challenge to redesign Aerogear Unified Push > Console." Add on "(UPS)". > - Is this correct? "Install a client code" In English the use of "a" > indicates that it is a specific thing instead of programming code. It reads > like I need to enter "352245". > - Personally I feel that this sentence is demeaning to the user and the > innuendo on the end is inappropriate for jboss.org "Yeah, we have high > expectations from our users. It isn't an easy job, and we need to hold > their hands and head them to a happy ending." But that just may be prudish > nature. > - Who do you intend to read this? If it is your intended user (of if you > think your intended user may ever read it) the overall tone is demeaning to > users. You are running the risk of pushing (no pun intended) users away. > You start out calling them children, then say they are too dumb to follow > your step to create it, then you say they do not enough attention and focus > to use the tool. It is one thing for you to think that way, it is another > to tell them to their face. To be clear, I am not on the Aerogear team. I'm > just providing the perspective of a potential user. I also believe that you > do not intend to offend, that is why I am offering this insight. > Not a native speaker (unlike Joshua), but I also had the same feelings when reading the entry. It feels a little bit speaking from high up down to the users. Overall, I like having an entry about the work being done to redesign the Push Console, and I like the blog post idea, but first reading, I found it a bit harsh. -Matthias > - Consider rewording "We only count with a fraction of a seconds to make a > good first impression and just a couple of seconds to grab their > attention." to "We only have a fraction of a second to make a good first > impression and just a couple of seconds to grab their attention." > - Consider rewording "For UPS console" to "For the UPS console" > - Please change "an" to "and" in "complete the 5 steps to get push > notifications up an running. " > - I am not sure but think you need a dash between "on bording" in "A > successful on boarding strategy is like". > - Consider rewording "As parents we need to encourage to teach themselves > and learn their own way." to include a "them" here "to encourage them to > teach". > - Consider changing "Alan Coopers teach us that main goal of a UX design > is to never make the user feel stupid." to "Alan Cooper teaches us that the > main goal of a UX design is to never make the user feel stupid" (as a side > note, he makes my point for me :P ) > > I mean not offense by my edits or comments. I think it great that you > wrote this up. Keep writing (and coding/designing). > > Joshua Wilson > > > ----- Original Message ----- > From: "Andres Galante [via aerogear-dev]" < > ml-node+s1069024n10770h85 at n5.nabble.com> > To: "joshuaw" > Sent: Monday, February 2, 2015 10:24:37 PM > Subject: [aerogear-dev] Post for jboss blog > > > > I wrote this for joboss blog: > > https://gist.github.com/andresgalante/32485438e2c64f2127ba > > I wanted to share before I send it in case someone has a few minutes to > read it and send feedback. > > Thanks! > > Andr?s > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Post-for-jboss-blog-tp10770.html > To start a new topic under aerogear-dev, email > ml-node+s1069024n1h46 at n5.nabble.com > To unsubscribe from aerogear-dev, visit > http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/490daf46/attachment-0001.html From corinnekrych at gmail.com Tue Feb 3 02:37:50 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 3 Feb 2015 08:37:50 +0100 Subject: [aerogear-dev] iOS SDK for OAuth2 In-Reply-To: <20150202192833.GA20797@abstractj.org> References: <20150202192833.GA20797@abstractj.org> Message-ID: <87FCCCCF-FA1D-4099-8D4C-122BF27D7484@gmail.com> > On 02 Feb 2015, at 20:28, Bruno Oliveira wrote: > > > Good morning, I was reviewing our SDK for iOS and I have few questions: > > 1. For example at Shoot app. Why our users have to configure to insert > the app ID at Shoot-Info.plist and also insert the same app ID at > ViewController? I was just wondering that once the app ID is informed, > you don't need to inform it again. > good point go ahead if you feel like pull requesting, if not create a JIRA for 2.2 release > 2. We have a note: > > "Because this demo securely stores OAuth2 tokens in your iOS keychain, > we chosen to use WhenPasscodeSet policy as a result to run this app you > need to have your passcode set" > > I think that's amazing, but at the same time we instruct our devs, to > insert the client secret hard coded into the app. Something like: > > let facebookConfig = FacebookConfig( > clientId: "XXXXXX", > clientSecret: "42", > scopes:["photo_upload, publish_actions"]) > > Doing the reverse engineering of the app, would permit me to get the > secret and mimic your FB app. > > So I would like to remove the need to input the same information twice > and encrypt the client secret using password based encryption. > Oki where do you want to store the encryption key? Keychain? > Let me know what do you think and I will start to file Jiras to myself. > > Note: This is not an issue specific to iOS. All the projects will get > the same love and feedback. > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From agalante at redhat.com Tue Feb 3 06:26:29 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 3 Feb 2015 06:26:29 -0500 (EST) Subject: [aerogear-dev] Post for jboss blog In-Reply-To: <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> Message-ID: <1089925233.3876498.1422962789255.JavaMail.zimbra@redhat.com> Thanks Joshua, you are right. I wasn't my intention to offend the but now that you meeting it, it does sound like an insult. Thanks for reading it! ----- Original Message ----- From: "Joshua Wilson" To: "Andres Galante [via aerogear-dev]" Cc: "aerogear-dev" Sent: Tuesday, February 3, 2015 1:44:35 AM Subject: Re: [aerogear-dev] Post for jboss blog It looks great! Here are my comments. - The following sentence needs to be rewritten. "Currently users count with extensive documentation to set up Unified Push Console." My guess is that the "with" should be "on". - The last word needs an "s". "This might sound exaggerated adulation, truth is I really do enjoy working with developer." Change "developer" to "developers". - Since you use "UPS" later on you need to add it the end of this sentence. "I've been given the challenge to redesign Aerogear Unified Push Console." Add on "(UPS)". - Is this correct? "Install a client code" In English the use of "a" indicates that it is a specific thing instead of programming code. It reads like I need to enter "352245". - Personally I feel that this sentence is demeaning to the user and the innuendo on the end is inappropriate for jboss.org "Yeah, we have high expectations from our users. It isn't an easy job, and we need to hold their hands and head them to a happy ending." But that just may be prudish nature. - Who do you intend to read this? If it is your intended user (of if you think your intended user may ever read it) the overall tone is demeaning to users. You are running the risk of pushing (no pun intended) users away. You start out calling them children, then say they are too dumb to follow your step to create it, then you say they do not enough attention and focus to use the tool. It is one thing for you to think that way, it is another to tell them to their face. To be clear, I am not on the Aerogear team. I'm just providing the perspective of a potential user. I also believe that you do not intend to offend, that is why I am offering this insight. - Consider rewording "We only count with a fraction of a seconds to make a good first impression and just a couple of seconds to grab their attention." to "We only have a fraction of a second to make a good first impression and just a couple of seconds to grab their attention." - Consider rewording "For UPS console" to "For the UPS console" - Please change "an" to "and" in "complete the 5 steps to get push notifications up an running. " - I am not sure but think you need a dash between "on bording" in "A successful on boarding strategy is like". - Consider rewording "As parents we need to encourage to teach themselves and learn their own way." to include a "them" here "to encourage them to teach". - Consider changing "Alan Coopers teach us that main goal of a UX design is to never make the user feel stupid." to "Alan Cooper teaches us that the main goal of a UX design is to never make the user feel stupid" (as a side note, he makes my point for me :P ) I mean not offense by my edits or comments. I think it great that you wrote this up. Keep writing (and coding/designing). Joshua Wilson ----- Original Message ----- From: "Andres Galante [via aerogear-dev]" To: "joshuaw" Sent: Monday, February 2, 2015 10:24:37 PM Subject: [aerogear-dev] Post for jboss blog I wrote this for joboss blog: https://gist.github.com/andresgalante/32485438e2c64f2127ba I wanted to share before I send it in case someone has a few minutes to read it and send feedback. Thanks! Andr?s _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ If you reply to this email, your message will be added to the discussion below: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Post-for-jboss-blog-tp10770.html To start a new topic under aerogear-dev, email ml-node+s1069024n1h46 at n5.nabble.com To unsubscribe from aerogear-dev, visit http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2 _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Tue Feb 3 07:04:21 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 3 Feb 2015 10:04:21 -0200 Subject: [aerogear-dev] iOS SDK for OAuth2 In-Reply-To: <87FCCCCF-FA1D-4099-8D4C-122BF27D7484@gmail.com> References: <20150202192833.GA20797@abstractj.org> <87FCCCCF-FA1D-4099-8D4C-122BF27D7484@gmail.com> Message-ID: <20150203120421.GA25842@abstractj.org> On 2015-02-03, Corinne Krych wrote: > > > On 02 Feb 2015, at 20:28, Bruno Oliveira wrote: > > > > > > Good morning, I was reviewing our SDK for iOS and I have few questions: > > > > 1. For example at Shoot app. Why our users have to configure to insert > > the app ID at Shoot-Info.plist and also insert the same app ID at > > ViewController? I was just wondering that once the app ID is informed, > > you don't need to inform it again. > > > > > good point go ahead if you feel like pull requesting, if not create a JIRA for 2.2 release Sure will do! > > > 2. We have a note: > > > > "Because this demo securely stores OAuth2 tokens in your iOS keychain, > > we chosen to use WhenPasscodeSet policy as a result to run this app you > > need to have your passcode set" > > > > I think that's amazing, but at the same time we instruct our devs, to > > insert the client secret hard coded into the app. Something like: > > > > let facebookConfig = FacebookConfig( > > clientId: "XXXXXX", > > clientSecret: "42", > > scopes:["photo_upload, publish_actions"]) > > > > Doing the reverse engineering of the app, would permit me to get the > > secret and mimic your FB app. > > > > So I would like to remove the need to input the same information twice > > and encrypt the client secret using password based encryption. > > > > Oki where do you want to store the encryption key? Keychain? I think this is a good scenario for offline. The developer would be able to insert the secret in clear text and based on the private key stored in the Keychain, we encrypt it. I will turn both in Jiras and this will be included for offline. Thanks for the feedback > > > Let me know what do you think and I will start to file Jiras to myself. > > > > Note: This is not an issue specific to iOS. All the projects will get > > the same love and feedback. > > > > > > -- > > > > 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 Tue Feb 3 08:26:55 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 3 Feb 2015 14:26:55 +0100 Subject: [aerogear-dev] Archive & forum for aerogears-users mailing list on Nabble Message-ID: Hey guys, I've setup a new Nabble forum as an archive and forum for aerogears-users, as it may be sometimes more convenient for searching & posting. You will find it here: http://aerogear-users.1116366.n5.nabble.com/ Happy posting! ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/63ee7193/attachment.html From scm.blanc at gmail.com Tue Feb 3 08:31:21 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 3 Feb 2015 14:31:21 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK Message-ID: Good Morning all ! As you might know, we are currently adding Amazon Device Messaging support to the UnifiedPush server. The server side has been PRed and it's now time to work on the client SDK. As you probably know, the amazon devices : the Kindle Fire (2nd and third generation), Fire Phone and FireTV are running FireOS which is basically a fork of Android OS. And since we have an Android Push SDK I start looking if we could reuse it. First good news, is that since AGDroid 2.0, things has been nicely isolated and is open for extension. But there is still some refactoring to do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. That logic should be moved one package level higher in a new Abstract class. In the end we will have a "gcm" package and a "adm" package (or project, see later in my questions) This way the ADM logic would be able to reuse that registration code. I started to play a bit with this refactoring here[2], disclaimer here, I'm not even sure that this code compiles, is just to give an idea. So before I go further, some questions (mainly for our Android Gods ;) ) : - Is this a good idea (reusing your SDK) ? I think yes, even if there is some time and effort needed for refactoring to make it completly generic. - How do we build / package / deliver ? We probably want 2 distinct JAR/aar. We could use profile in Maven to only package one feature but that sounds a bit "messy". What about having sub-projects, this way we would have aerogear-android-push and then : aerogear-android-push-gcm and aerogear-push-gcm. - The registration flow for ADM[3] (so device <-> Amazon's server) is a bit different thant the GCM one , it's the same interface that receive the registration event and the push notification events. We have to check how this fit with the current architecture of android-push. Other challenge will be shipping ADM jar, since this one is on Maven and must be downloaded manually but that is for later ;) Sebi [1] https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java [2] https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring [3] https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/62a85353/attachment.html From lukas.fryc at gmail.com Tue Feb 3 08:47:48 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 3 Feb 2015 14:47:48 +0100 Subject: [aerogear-dev] Post for jboss blog In-Reply-To: <1089925233.3876498.1422962789255.JavaMail.zimbra@redhat.com> References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> <1089925233.3876498.1422962789255.JavaMail.zimbra@redhat.com> Message-ID: Fantastic reading about the intentions of the new UI. Thanks for the insight, Andres. P.S.: I'm not native speaker and I don't mind such mistakes in blogs (especially because I don't see them) ;-) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/47104932/attachment.html From matzew at apache.org Tue Feb 3 08:59:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 14:59:02 +0100 Subject: [aerogear-dev] Post for jboss blog In-Reply-To: References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> <1089925233.3876498.1422962789255.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Feb 3, 2015 at 2:47 PM, Luk?? Fry? wrote: > Fantastic reading about the intentions of the new UI. > > Thanks for the insight, Andres. > > > P.S.: I'm not native speaker and I don't mind such mistakes in blogs > (especially because I don't see them) ;-) > yeah, but there is a difference between corp. blogs (***.jboss.org) and private ones :-) > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/ee976805/attachment-0001.html From agalante at redhat.com Tue Feb 3 09:28:13 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 3 Feb 2015 09:28:13 -0500 (EST) Subject: [aerogear-dev] Post for jboss blog In-Reply-To: References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> <1089925233.3876498.1422962789255.JavaMail.zimbra@redhat.com> Message-ID: <1604353657.3922980.1422973693108.JavaMail.zimbra@redhat.com> Thanks for reading it Lukas. Even if I correct the english mistakes I think that Joshua has a point. The article sounds offensive. I will try to re write it in a way that describes the process without insulting users. ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Cc: "Andres Galante [via aerogear-dev]" Sent: Tuesday, February 3, 2015 10:59:02 AM Subject: Re: [aerogear-dev] Post for jboss blog On Tue, Feb 3, 2015 at 2:47 PM, Luk?? Fry? < lukas.fryc at gmail.com > wrote: Fantastic reading about the intentions of the new UI. Thanks for the insight, Andres. P.S.: I'm not native speaker and I don't mind such mistakes in blogs (especially because I don't see them) ;-) yeah, but there is a difference between corp. blogs (***. jboss.org ) and private ones :-) _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From scm.blanc at gmail.com Tue Feb 3 09:28:45 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 3 Feb 2015 15:28:45 +0100 Subject: [aerogear-dev] Post for jboss blog In-Reply-To: References: <1885674582.3817741.1422933842994.JavaMail.zimbra@redhat.com> <1010327874.5323455.1422938675315.JavaMail.zimbra@redhat.com> <1089925233.3876498.1422962789255.JavaMail.zimbra@redhat.com> Message-ID: +1 I loved your blog post, your introduction is amazing and to be honest I can not really see where it is insulting or harsh. But that is probably my Dutch "direct-to-the-point" spirit mixed with my french blood ;) Sebi On Tue, Feb 3, 2015 at 2:47 PM, Luk?? Fry? wrote: > Fantastic reading about the intentions of the new UI. > > Thanks for the insight, Andres. > > > P.S.: I'm not native speaker and I don't mind such mistakes in blogs > (especially because I don't see them) ;-) > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/80512d8c/attachment.html From supittma at redhat.com Tue Feb 3 09:38:00 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 03 Feb 2015 09:38:00 -0500 Subject: [aerogear-dev] Easy access to security related documentation In-Reply-To: <20150202180020.GA1899@abstractj.org> References: <20150202180020.GA1899@abstractj.org> Message-ID: <54D0DD48.1000703@redhat.com> On 02/02/2015 01:00 PM, Bruno Oliveira wrote: > Good morning, I would like to suggest a new structure to all the > documents related with security. We have a great content on > aerogear.org, at the same time, hard to find. Because some items are > located at guides sections, others can be found at specs section. > > That said I would like to suggest the following section under "guides" > section. > > - Security > - Cryptography (Include a documentation revamped and revisited), usage > instructions and etc > - Authentication and Authorization > - Client > - Using OAuth2 with Android > - Using OAuth2 with iOS > - Using OAuth2 with JavaScript > - Server > - How to setup the server and references to Keycloak I think it might be better to have setting up KeyCloak be the first step then OAuth with the clients be the second item. Hopefully that will let people have a better idea of what is going to be happening between the client and server. > > I don't want to drop any documentation already done, only to revisit, > organize and improve. Thoughts? > > -- > > 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 matzew at apache.org Tue Feb 3 09:45:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 15:45:41 +0100 Subject: [aerogear-dev] Easy access to security related documentation In-Reply-To: <20150202180020.GA1899@abstractj.org> References: <20150202180020.GA1899@abstractj.org> Message-ID: On Mon, Feb 2, 2015 at 7:00 PM, Bruno Oliveira wrote: > Good morning, I would like to suggest a new structure to all the > documents related with security. We have a great content on > aerogear.org, at the same time, hard to find. +1 and that's hopefully changing with the new UI update that Lukas and Andres are working on > Because some items are > located at guides sections, others can be found at specs section. > > That said I would like to suggest the following section under "guides" > section. > > - Security > - Cryptography (Include a documentation revamped and revisited), usage > instructions and etc > - Authentication and Authorization > - Client > - Using OAuth2 with Android > - Using OAuth2 with iOS > - Using OAuth2 with JavaScript > - Server > - How to setup the server and references to Keycloak > +1 Oh, perhaps we should include our OTP bits for Android/iOS? > > I don't want to drop any documentation already done, only to revisit, > organize and improve. Thoughts? > yes, sounds good. Wondering if Andres/Lukas have some comments here, since they are working on the new site :-) > > -- > > 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/20150203/7657839d/attachment.html From lukas.fryc at gmail.com Tue Feb 3 09:48:43 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 3 Feb 2015 15:48:43 +0100 Subject: [aerogear-dev] JIRA driven roadmaps In-Reply-To: References: <4239F885-197D-463F-893E-C5CF72B4CF29@gmail.com> Message-ID: +1 for JIRA I have created following JIRA to cover that: https://issues.jboss.org/browse/AEROGEAR-1610 On Mon, Feb 2, 2015 at 1:48 PM, Daniel Passos wrote: > +1 for JIra > > -- Passos > > On Mon, Feb 2, 2015 at 10:43 AM, Corinne Krych > wrote: > >> I like the roadmap JIRA view >> +1 to have only JIRA >> >> ++ >> Corinne >> > On 02 Feb 2015, at 11:45, Matthias Wessendorf >> wrote: >> > >> > Hi, >> > >> > on our homepage ([1]) we have some handwritten docs that cover the >> roadmap for parts of our components. These roadmaps contain a duplication >> of content that is available in JIRA. Since this content is handwritten, >> it's often not as up-to-date as it should be. Here are a few examples: >> > >> > * https://aerogear.org/docs/planning/roadmaps/AeroGeariOS/ >> > * https://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ >> > * https://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ >> > >> > Basically the contain incorrect dates and duplicate the list of >> effected JIRAs. But I wonder why we even do have these handwritten docs? >> > >> > JIRA itself has a roadmap overview, which looks nice and clean: >> > >> > >> https://issues.jboss.org/browse/AGIOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >> > >> https://issues.jboss.org/browse/AGDROID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >> > >> https://issues.jboss.org/browse/AGCORDOVA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >> > >> > Since we track our issues, versions and releases in JIRA the above >> roadmaps comes for free. Now, when we change a release date in JIRA, using >> the above links as our roadmaps means we don't need to update the >> handwritten doc:-) >> > >> > Any thoughts? >> > >> > -Matthias >> > >> > [1] https://aerogear.org/docs/planning/ >> > >> > >> > -- >> > Matthias Wessendorf >> > >> > blog: http://matthiaswessendorf.wordpress.com/ >> > sessions: http://www.slideshare.net/mwessendorf >> > twitter: http://twitter.com/mwessendorf >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150203/c723af44/attachment.html From daniel.bevenius at gmail.com Tue Feb 3 09:50:19 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Tue, 3 Feb 2015 15:50:19 +0100 Subject: [aerogear-dev] JIRA driven roadmaps In-Reply-To: References: <4239F885-197D-463F-893E-C5CF72B4CF29@gmail.com> Message-ID: +1 for JIRA On 3 February 2015 at 15:48, Luk?? Fry? wrote: > +1 for JIRA > > I have created following JIRA to cover that: > https://issues.jboss.org/browse/AEROGEAR-1610 > > On Mon, Feb 2, 2015 at 1:48 PM, Daniel Passos wrote: > >> +1 for JIra >> >> -- Passos >> >> On Mon, Feb 2, 2015 at 10:43 AM, Corinne Krych >> wrote: >> >>> I like the roadmap JIRA view >>> +1 to have only JIRA >>> >>> ++ >>> Corinne >>> > On 02 Feb 2015, at 11:45, Matthias Wessendorf >>> wrote: >>> > >>> > Hi, >>> > >>> > on our homepage ([1]) we have some handwritten docs that cover the >>> roadmap for parts of our components. These roadmaps contain a duplication >>> of content that is available in JIRA. Since this content is handwritten, >>> it's often not as up-to-date as it should be. Here are a few examples: >>> > >>> > * https://aerogear.org/docs/planning/roadmaps/AeroGeariOS/ >>> > * https://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/ >>> > * https://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ >>> > >>> > Basically the contain incorrect dates and duplicate the list of >>> effected JIRAs. But I wonder why we even do have these handwritten docs? >>> > >>> > JIRA itself has a roadmap overview, which looks nice and clean: >>> > >>> > >>> https://issues.jboss.org/browse/AGIOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >>> > >>> https://issues.jboss.org/browse/AGDROID/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >>> > >>> https://issues.jboss.org/browse/AGCORDOVA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >>> > >>> > Since we track our issues, versions and releases in JIRA the above >>> roadmaps comes for free. Now, when we change a release date in JIRA, using >>> the above links as our roadmaps means we don't need to update the >>> handwritten doc:-) >>> > >>> > Any thoughts? >>> > >>> > -Matthias >>> > >>> > [1] https://aerogear.org/docs/planning/ >>> > >>> > >>> > -- >>> > Matthias Wessendorf >>> > >>> > blog: http://matthiaswessendorf.wordpress.com/ >>> > sessions: http://www.slideshare.net/mwessendorf >>> > twitter: http://twitter.com/mwessendorf >>> > _______________________________________________ >>> > aerogear-dev mailing list >>> > aerogear-dev at lists.jboss.org >>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150203/4ec4d1bf/attachment-0001.html From lukas.fryc at gmail.com Tue Feb 3 09:51:04 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 3 Feb 2015 15:51:04 +0100 Subject: [aerogear-dev] Easy access to security related documentation In-Reply-To: References: <20150202180020.GA1899@abstractj.org> Message-ID: Sure, that sounds good, let's review early what is done in `new-design` branch, and we may discuss early changes. On Tue, Feb 3, 2015 at 3:45 PM, Matthias Wessendorf wrote: > > > On Mon, Feb 2, 2015 at 7:00 PM, Bruno Oliveira > wrote: > >> Good morning, I would like to suggest a new structure to all the >> documents related with security. We have a great content on >> aerogear.org, at the same time, hard to find. > > > +1 and that's hopefully changing with the new UI update that Lukas and > Andres are working on > > >> Because some items are >> located at guides sections, others can be found at specs section. >> >> That said I would like to suggest the following section under "guides" >> section. >> >> - Security >> - Cryptography (Include a documentation revamped and revisited), usage >> instructions and etc >> - Authentication and Authorization >> - Client >> - Using OAuth2 with Android >> - Using OAuth2 with iOS >> - Using OAuth2 with JavaScript >> - Server >> - How to setup the server and references to Keycloak >> > > +1 > > Oh, perhaps we should include our OTP bits for Android/iOS? > > >> >> I don't want to drop any documentation already done, only to revisit, >> organize and improve. Thoughts? >> > > yes, sounds good. Wondering if Andres/Lukas have some comments here, since > they are working on the new site :-) > > >> >> -- >> >> 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/20150203/947ac027/attachment.html From matzew at apache.org Tue Feb 3 09:56:21 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 15:56:21 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: References: Message-ID: On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc wrote: > Good Morning all ! > > As you might know, we are currently adding Amazon Device Messaging support > to the UnifiedPush server. > The server side has been PRed and it's now time to work on the client SDK. > once our java-adm is on maven central, I will take a look at the PR > As you probably know, the amazon devices : the Kindle Fire (2nd and third > generation), Fire Phone and FireTV are running FireOS which is basically a > fork of Android OS. And since we have an Android Push SDK I start looking > if we could reuse it. > > First good news, is that since AGDroid 2.0, things has been nicely > isolated and is open for extension. But there is still some refactoring to > do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. > the package name shouldn't be the smallest concern :-) > That logic should be moved one package level higher in a new Abstract > class. > In the end we will have a "gcm" package and a "adm" package (or project, > see later in my questions) > +1 > > This way the ADM logic would be able to reuse that registration code. I > started to play a bit with this refactoring here[2], disclaimer here, I'm > not even sure that this code compiles, is just to give an idea. > > So before I go further, some questions (mainly for our Android Gods ;) ) > : > > - Is this a good idea (reusing your SDK) ? I think yes, even if there is > some time and effort needed for refactoring to make it completly generic. > sounds reasonable to me, to extend it and apply changes on a separate ADM-PUSH-SDK > > - How do we build / package / deliver ? > gradle? or, what does Amazon do / prefer ? > We probably want 2 distinct JAR/aar. We could use profile in Maven to only > package one feature but that sounds a bit "messy". > What about having sub-projects, this way we would have > aerogear-android-push and then : aerogear-android-push-gcm and > aerogear-push-gcm. > Not sure I get that, but do you mean "aerogear-android-push" - aerogear-android-push-gcm - aerogear-android-push-adm sounds reasonable > > - The registration flow for ADM[3] (so device <-> Amazon's server) is a > bit different thant the GCM one > , it's the same interface that receive the registration event and the push > notification events. We have to check how this fit with the current > architecture of android-push. > > Other challenge will be shipping ADM jar, since this one is on Maven and > must be downloaded manually but that is for later ;) > not sure, why do we need to ship it? what's the license? Why do I need a manual download from maven ? Not following here > > Sebi > > > [1] > https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java > [2] > https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring > [3] > https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/d89eb92d/attachment.html From supittma at redhat.com Tue Feb 3 10:00:46 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 03 Feb 2015 10:00:46 -0500 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: References: Message-ID: <54D0E29E.6090704@redhat.com> On 02/03/2015 08:31 AM, Sebastien Blanc wrote: > Good Morning all ! > > As you might know, we are currently adding Amazon Device Messaging > support to the UnifiedPush server. > The server side has been PRed and it's now time to work on the client SDK. > As you probably know, the amazon devices : the Kindle Fire (2nd and > third generation), Fire Phone and FireTV are running FireOS which is > basically a fork of Android OS. And since we have an Android Push SDK > I start looking if we could reuse it. > > First good news, is that since AGDroid 2.0, things has been nicely > isolated and is open for extension. But there is still some > refactoring to do, the "UPS Registration" flow/logic is still in the > "gcm" package[1]. That logic should be moved one package level higher > in a new Abstract class. > In the end we will have a "gcm" package and a "adm" package (or > project, see later in my questions) > > This way the ADM logic would be able to reuse that registration code. > I started to play a bit with this refactoring here[2], disclaimer > here, I'm not even sure that this code compiles, is just to give an idea. > > So before I go further, some questions (mainly for our Android Gods > ;) ) : > > - Is this a good idea (reusing your SDK) ? I think yes, even if there > is some time and effort needed for refactoring to make it completly > generic. +1 > > - How do we build / package / deliver ? We probably want 2 distinct > JAR/aar. We could use profile in Maven to only package one feature but > that sounds a bit "messy". > What about having sub-projects, this way we would have > aerogear-android-push and then : aerogear-android-push-gcm and > aerogear-push-gcm. Putting gcm in a new artifact will break semver. Both should probably just be in the -push artifact. > > - The registration flow for ADM[3] (so device <-> Amazon's server) is > a bit different thant the GCM one > , it's the same interface that receive the registration event and the > push notification events. We have to check how this fit with the > current architecture of android-push. It looks close enough to the GCM flow that I wouldn't worry. The biggest difference is GCM's service to handle messages and hand to your app is in Google Play Services and here it is explicitly in your app. > > Other challenge will be shipping ADM jar, since this one is on Maven > and must be downloaded manually but that is for later ;) /me sees the old, deprecated ADT and runs. The biggest problem will be supporting Eclipse again. I don't think we can do this. > > Sebi > > > [1]https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java > [2] > https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring > [3] > https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm > > > _______________________________________________ > 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/20150203/73663d45/attachment-0001.html From supittma at redhat.com Tue Feb 3 10:07:29 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 03 Feb 2015 10:07:29 -0500 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: References: Message-ID: <54D0E431.3060709@redhat.com> On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: > > > On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc > wrote: > > Good Morning all ! > > As you might know, we are currently adding Amazon Device Messaging > support to the UnifiedPush server. > The server side has been PRed and it's now time to work on the > client SDK. > > > once our java-adm is on maven central, I will take a look at the PR > > As you probably know, the amazon devices : the Kindle Fire (2nd > and third generation), Fire Phone and FireTV are running FireOS > which is basically a fork of Android OS. And since we have an > Android Push SDK I start looking if we could reuse it. > > First good news, is that since AGDroid 2.0, things has been nicely > isolated and is open for extension. But there is still some > refactoring to do, the "UPS Registration" flow/logic is still in > the "gcm" package[1]. > > > the package name shouldn't be the smallest concern :-) > > That logic should be moved one package level higher in a new > Abstract class. > In the end we will have a "gcm" package and a "adm" package (or > project, see later in my questions) > > > +1 > > > This way the ADM logic would be able to reuse that registration > code. I started to play a bit with this refactoring here[2], > disclaimer here, I'm not even sure that this code compiles, is > just to give an idea. > > So before I go further, some questions (mainly for our Android > Gods ;) ) : > > - Is this a good idea (reusing your SDK) ? I think yes, even if > there is some time and effort needed for refactoring to make it > completly generic. > > > sounds reasonable to me, to extend it and apply changes on a separate > ADM-PUSH-SDK > > > - How do we build / package / deliver ? > > > gradle? or, what does Amazon do / prefer ? > > We probably want 2 distinct JAR/aar. We could use profile in Maven > to only package one feature but that sounds a bit "messy". > What about having sub-projects, this way we would have > aerogear-android-push and then : aerogear-android-push-gcm and > aerogear-push-gcm. > > > Not sure I get that, but do you mean "aerogear-android-push" > - aerogear-android-push-gcm > - aerogear-android-push-adm > > sounds reasonable No it isn't. For starters it will break the 2.0 API and require a 3.0 API release. > > > - The registration flow for ADM[3] (so device <-> Amazon's server) > is a bit different thant the GCM one > , it's the same interface that receive the registration event and > the push notification events. We have to check how this fit with > the current architecture of android-push. > > Other challenge will be shipping ADM jar, since this one is on > Maven and must be downloaded manually but that is for later ;) > > > not sure, why do we need to ship it? what's the license? Why do I need > a manual download from maven ? Not following here Amazon's SDK is a giant zip bundle. We will need to find a way to package it into the local maven repo. They do publish some things to central, but it looks like that is their AWS APIs but not ADM. > > Sebi > > > [1]https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java > [2] > https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring > [3] > https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150203/2a15dc0a/attachment.html From matzew at apache.org Tue Feb 3 10:08:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 16:08:41 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: <54D0E29E.6090704@redhat.com> References: <54D0E29E.6090704@redhat.com> Message-ID: On Tue, Feb 3, 2015 at 4:00 PM, Summers Pittman wrote: > On 02/03/2015 08:31 AM, Sebastien Blanc wrote: > > Good Morning all ! > > As you might know, we are currently adding Amazon Device Messaging > support to the UnifiedPush server. > The server side has been PRed and it's now time to work on the client SDK. > As you probably know, the amazon devices : the Kindle Fire (2nd and third > generation), Fire Phone and FireTV are running FireOS which is basically a > fork of Android OS. And since we have an Android Push SDK I start looking > if we could reuse it. > > First good news, is that since AGDroid 2.0, things has been nicely > isolated and is open for extension. But there is still some refactoring to > do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. > That logic should be moved one package level higher in a new Abstract > class. > In the end we will have a "gcm" package and a "adm" package (or project, > see later in my questions) > > This way the ADM logic would be able to reuse that registration code. I > started to play a bit with this refactoring here[2], disclaimer here, I'm > not even sure that this code compiles, is just to give an idea. > > So before I go further, some questions (mainly for our Android Gods ;) > ) : > > - Is this a good idea (reusing your SDK) ? I think yes, even if there is > some time and effort needed for refactoring to make it completly generic. > > +1 > > > - How do we build / package / deliver ? We probably want 2 distinct > JAR/aar. We could use profile in Maven to only package one feature but that > sounds a bit "messy". > What about having sub-projects, this way we would have > aerogear-android-push and then : aerogear-android-push-gcm and > aerogear-push-gcm. > > Putting gcm in a new artifact will break semver. Both should probably > just be in the -push artifact. > good point! > > > > - The registration flow for ADM[3] (so device <-> Amazon's server) is a > bit different thant the GCM one > , it's the same interface that receive the registration event and the push > notification events. We have to check how this fit with the current > architecture of android-push. > > It looks close enough to the GCM flow that I wouldn't worry. The biggest > difference is GCM's service to handle messages and hand to your app is in > Google Play Services and here it is explicitly in your app. > > > Other challenge will be shipping ADM jar, since this one is on Maven and > must be downloaded manually but that is for later ;) > > /me sees the old, deprecated ADT and runs. > > The biggest problem will be supporting Eclipse again. I don't think we > can do this. > +1 on not going back to that for our current development > > > Sebi > > > [1] > https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java > [2] > https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring > [3] > https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm > > > _______________________________________________ > 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/20150203/9aa15834/attachment-0001.html From matzew at apache.org Tue Feb 3 10:09:28 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 16:09:28 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: On the JIRA I saw this template: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b looks good to me (did a quick read) On Wed, Jan 28, 2015 at 9:08 AM, Luk?? Fry? wrote: > Okay, lets make the example optional. As long as documentation can be > found within 1 or 2 clicks, that should be fine. > On Jan 28, 2015 2:35 AM, "Daniel Passos" wrote: > >> Hey Luk?s, >> >> I really don't like the ideia of add the some code snipped on README. I >> know it's very common and most libraries do this but, it's a lot of code to >> explain in a README and 2 different places to update when we >> change/improve/whatever our libraries. I really prefer link to the ag.org >> doc. >> >> In related news I'd like to add a link to a example app as we did[1] on >> push library >> >> [1] https://github.com/aerogear/aerogear-android-push#demo-apps >> >> -- Passos >> >> >> On Tue, Jan 27, 2015 at 11:47 AM, Luk?? Fry? >> wrote: >> >>> Yea, it would be nice if usage would show the code snippet, so Usage >>> would cover: >>> >>> 1. how to add the library dependency to your project (which is covered >>> in Android Core README) >>> 2. a smallest possible snippet of the code that covers how to use the >>> lib (that is not covered atm) + link to respective feature doc if needed >>> >>> I like what iOS has here [1], do we want to adopt this pattern for >>> Android, Cordova and JS as well? >>> >>> [1] https://github.com/aerogear/aerogear-ios-oauth2 >>> >>> On Tue, Jan 27, 2015 at 11:24 AM, Corinne Krych >>> wrote: >>> >>>> it looks good, I?m just puzzled by the usage section in you gist: >>>> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b#usage >>>> which contains more build instruction than usage of android-core? >>>> >>>> for our ios readme we have the same content, not foramtted the same way >>>> though but it shoudn?t be a pb to reformat. >>>> >>>> ++ >>>> Corinne >>>> >>>> > On 27 Jan 2015, at 11:22, Sebastien Blanc >>>> wrote: >>>> > >>>> > sounds good ! >>>> > >>>> > On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? >>>> wrote: >>>> > Hey guys, >>>> > >>>> > me and passos brainstormed yesterday about the project info in the >>>> README files >>>> > >>>> > as it would be nice to unify them across all repositories (discussed >>>> elsewhere) and mainly allow people navigate from code repositories directly >>>> to locations where they can find more help, etc. >>>> > >>>> > >>>> > As a result, we both liked: >>>> > >>>> > 1. brief Project Info in the header >>>> > 2. more verbose Documentation / Development / Questions? / Found a >>>> bug? section in the footer >>>> > >>>> > Example for Android Core: >>>> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b >>>> > >>>> > >>>> > Let me know what you think. >>>> > >>>> > If I don't get any -1, I will send pull requests with the updates in >>>> all aerogear repositories at the end of this week. >>>> > >>>> > >>>> > Cheers! >>>> > >>>> > ~ Lukas >>>> > >>>> > >>>> > P.S.: aerogear-users has just a ordinary mailman archive while >>>> aerogear-dev uses nabble, which is far better for navigation / search, etc. >>>> (the request to add that feature to aerogear-users is tracked in >>>> https://issues.jboss.org/browse/AEROGEAR-1590 ) >>>> > >>>> > _______________________________________________ >>>> > aerogear-dev mailing list >>>> > aerogear-dev at lists.jboss.org >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> > >>>> > _______________________________________________ >>>> > aerogear-dev mailing list >>>> > aerogear-dev at lists.jboss.org >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/d2f93c1f/attachment.html From supittma at redhat.com Tue Feb 3 10:13:09 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 03 Feb 2015 10:13:09 -0500 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: <54D0E431.3060709@redhat.com> References: <54D0E431.3060709@redhat.com> Message-ID: <54D0E585.5090901@redhat.com> On 02/03/2015 10:07 AM, Summers Pittman wrote: > On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: >> >> >> On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc > > wrote: >> >> Good Morning all ! >> >> As you might know, we are currently adding Amazon Device >> Messaging support to the UnifiedPush server. >> The server side has been PRed and it's now time to work on the >> client SDK. >> >> >> once our java-adm is on maven central, I will take a look at the PR >> >> As you probably know, the amazon devices : the Kindle Fire (2nd >> and third generation), Fire Phone and FireTV are running FireOS >> which is basically a fork of Android OS. And since we have an >> Android Push SDK I start looking if we could reuse it. >> >> First good news, is that since AGDroid 2.0, things has been >> nicely isolated and is open for extension. But there is still >> some refactoring to do, the "UPS Registration" flow/logic is >> still in the "gcm" package[1]. >> >> >> the package name shouldn't be the smallest concern :-) >> >> That logic should be moved one package level higher in a new >> Abstract class. >> In the end we will have a "gcm" package and a "adm" package (or >> project, see later in my questions) >> >> >> +1 >> >> >> This way the ADM logic would be able to reuse that registration >> code. I started to play a bit with this refactoring here[2], >> disclaimer here, I'm not even sure that this code compiles, is >> just to give an idea. >> >> So before I go further, some questions (mainly for our Android >> Gods ;) ) : >> >> - Is this a good idea (reusing your SDK) ? I think yes, even if >> there is some time and effort needed for refactoring to make it >> completly generic. >> >> >> sounds reasonable to me, to extend it and apply changes on a separate >> ADM-PUSH-SDK >> >> >> - How do we build / package / deliver ? >> >> >> gradle? or, what does Amazon do / prefer ? >> >> We probably want 2 distinct JAR/aar. We could use profile in >> Maven to only package one feature but that sounds a bit "messy". >> What about having sub-projects, this way we would have >> aerogear-android-push and then : aerogear-android-push-gcm and >> aerogear-push-gcm. >> >> >> Not sure I get that, but do you mean "aerogear-android-push" >> - aerogear-android-push-gcm >> - aerogear-android-push-adm >> >> sounds reasonable > No it isn't. For starters it will break the 2.0 API and require a 3.0 > API release. >> >> >> - The registration flow for ADM[3] (so device <-> Amazon's >> server) is a bit different thant the GCM one >> , it's the same interface that receive the registration event and >> the push notification events. We have to check how this fit with >> the current architecture of android-push. >> >> Other challenge will be shipping ADM jar, since this one is on >> Maven and must be downloaded manually but that is for later ;) >> >> >> not sure, why do we need to ship it? what's the license? Why do I >> need a manual download from maven ? Not following here > Amazon's SDK is a giant zip bundle. We will need to find a way to > package it into the local maven repo. > > They do publish some things to central, but it looks like that is > their AWS APIs but not ADM. Sorry to self reply, but does anyone know anyone inside of Amazon that we could possibly work with to get ADM in a more sane distribution mechanism? > >> >> Sebi >> >> >> [1]https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >> [2] >> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >> [3] >> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- 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/20150203/f78b28b0/attachment-0001.html From qmx at qmx.me Tue Feb 3 10:16:41 2015 From: qmx at qmx.me (Douglas Campos) Date: Tue, 3 Feb 2015 13:16:41 -0200 Subject: [aerogear-dev] JIRA driven roadmaps In-Reply-To: References: Message-ID: <20150203151641.GJ48382@darkstar.local> +1 to JIRA -- qmx From matzew at apache.org Tue Feb 3 10:26:59 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 16:26:59 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: <54D0E431.3060709@redhat.com> References: <54D0E431.3060709@redhat.com> Message-ID: On Tue, Feb 3, 2015 at 4:07 PM, Summers Pittman wrote: > On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: > > > > On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc > wrote: > >> Good Morning all ! >> >> As you might know, we are currently adding Amazon Device Messaging >> support to the UnifiedPush server. >> The server side has been PRed and it's now time to work on the client SDK. >> > > once our java-adm is on maven central, I will take a look at the PR > > >> As you probably know, the amazon devices : the Kindle Fire (2nd and >> third generation), Fire Phone and FireTV are running FireOS which is >> basically a fork of Android OS. And since we have an Android Push SDK I >> start looking if we could reuse it. >> >> First good news, is that since AGDroid 2.0, things has been nicely >> isolated and is open for extension. But there is still some refactoring to >> do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. >> > > the package name shouldn't be the smallest concern :-) > > > >> That logic should be moved one package level higher in a new Abstract >> class. >> In the end we will have a "gcm" package and a "adm" package (or project, >> see later in my questions) >> > > +1 > > >> >> This way the ADM logic would be able to reuse that registration code. I >> started to play a bit with this refactoring here[2], disclaimer here, I'm >> not even sure that this code compiles, is just to give an idea. >> >> So before I go further, some questions (mainly for our Android Gods ;) >> ) : >> >> - Is this a good idea (reusing your SDK) ? I think yes, even if there >> is some time and effort needed for refactoring to make it completly generic. >> > > sounds reasonable to me, to extend it and apply changes on a separate > ADM-PUSH-SDK > > >> >> - How do we build / package / deliver ? >> > > gradle? or, what does Amazon do / prefer ? > > >> We probably want 2 distinct JAR/aar. We could use profile in Maven to >> only package one feature but that sounds a bit "messy". >> What about having sub-projects, this way we would have >> aerogear-android-push and then : aerogear-android-push-gcm and >> aerogear-push-gcm. >> > > Not sure I get that, but do you mean "aerogear-android-push" > - aerogear-android-push-gcm > - aerogear-android-push-adm > > sounds reasonable > > No it isn't. For starters it will break the 2.0 API and require a 3.0 API > release. > yeah - fair point :-) I smell a future JIRA :-) hehe > > >> >> - The registration flow for ADM[3] (so device <-> Amazon's server) is a >> bit different thant the GCM one >> , it's the same interface that receive the registration event and the >> push notification events. We have to check how this fit with the current >> architecture of android-push. >> >> Other challenge will be shipping ADM jar, since this one is on Maven >> and must be downloaded manually but that is for later ;) >> > > not sure, why do we need to ship it? what's the license? Why do I need a > manual download from maven ? Not following here > > Amazon's SDK is a giant zip bundle. We will need to find a way to package > it into the local maven repo. > > They do publish some things to central, but it looks like that is their > AWS APIs but not ADM. > > > >> >> Sebi >> >> >> [1] >> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >> [2] >> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >> [3] >> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/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/20150203/f92fff5e/attachment.html From supittma at redhat.com Tue Feb 3 10:31:27 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 03 Feb 2015 10:31:27 -0500 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: References: <54D0E431.3060709@redhat.com> Message-ID: <54D0E9CF.2050207@redhat.com> On 02/03/2015 10:26 AM, Matthias Wessendorf wrote: > > > On Tue, Feb 3, 2015 at 4:07 PM, Summers Pittman > wrote: > > On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: >> >> >> On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc >> > wrote: >> >> Good Morning all ! >> >> As you might know, we are currently adding Amazon Device >> Messaging support to the UnifiedPush server. >> The server side has been PRed and it's now time to work on >> the client SDK. >> >> >> once our java-adm is on maven central, I will take a look at the PR >> >> As you probably know, the amazon devices : the Kindle Fire >> (2nd and third generation), Fire Phone and FireTV are running >> FireOS which is basically a fork of Android OS. And since we >> have an Android Push SDK I start looking if we could reuse it. >> >> First good news, is that since AGDroid 2.0, things has been >> nicely isolated and is open for extension. But there is still >> some refactoring to do, the "UPS Registration" flow/logic is >> still in the "gcm" package[1]. >> >> >> the package name shouldn't be the smallest concern :-) >> >> That logic should be moved one package level higher in a new >> Abstract class. >> In the end we will have a "gcm" package and a "adm" package >> (or project, see later in my questions) >> >> >> +1 >> >> >> This way the ADM logic would be able to reuse that >> registration code. I started to play a bit with this >> refactoring here[2], disclaimer here, I'm not even sure that >> this code compiles, is just to give an idea. >> >> So before I go further, some questions (mainly for our >> Android Gods ;) ) : >> >> - Is this a good idea (reusing your SDK) ? I think yes, even >> if there is some time and effort needed for refactoring to >> make it completly generic. >> >> >> sounds reasonable to me, to extend it and apply changes on a >> separate ADM-PUSH-SDK >> >> >> - How do we build / package / deliver ? >> >> >> gradle? or, what does Amazon do / prefer ? >> >> We probably want 2 distinct JAR/aar. We could use profile in >> Maven to only package one feature but that sounds a bit "messy". >> What about having sub-projects, this way we would have >> aerogear-android-push and then : aerogear-android-push-gcm >> and aerogear-push-gcm. >> >> >> Not sure I get that, but do you mean "aerogear-android-push" >> - aerogear-android-push-gcm >> - aerogear-android-push-adm >> >> sounds reasonable > No it isn't. For starters it will break the 2.0 API and require a > 3.0 API release. > > > yeah - fair point :-) I smell a future JIRA :-) hehe That usually means I need to take a shower ;) > >> >> - The registration flow for ADM[3] (so device <-> Amazon's >> server) is a bit different thant the GCM one >> , it's the same interface that receive the registration event >> and the push notification events. We have to check how this >> fit with the current architecture of android-push. >> >> Other challenge will be shipping ADM jar, since this one is >> on Maven and must be downloaded manually but that is for later ;) >> >> >> not sure, why do we need to ship it? what's the license? Why do I >> need a manual download from maven ? Not following here > Amazon's SDK is a giant zip bundle. We will need to find a way to > package it into the local maven repo. > > They do publish some things to central, but it looks like that is > their AWS APIs but not ADM. > >> >> Sebi >> >> >> [1]https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >> [2] >> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >> [3] >> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/6bc4fef0/attachment-0001.html From scm.blanc at gmail.com Tue Feb 3 10:35:03 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 3 Feb 2015 16:35:03 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: <54D0E431.3060709@redhat.com> References: <54D0E431.3060709@redhat.com> Message-ID: On Tue, Feb 3, 2015 at 4:07 PM, Summers Pittman wrote: > On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: > > > > On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc > wrote: > >> Good Morning all ! >> >> As you might know, we are currently adding Amazon Device Messaging >> support to the UnifiedPush server. >> The server side has been PRed and it's now time to work on the client SDK. >> > > once our java-adm is on maven central, I will take a look at the PR > > >> As you probably know, the amazon devices : the Kindle Fire (2nd and >> third generation), Fire Phone and FireTV are running FireOS which is >> basically a fork of Android OS. And since we have an Android Push SDK I >> start looking if we could reuse it. >> >> First good news, is that since AGDroid 2.0, things has been nicely >> isolated and is open for extension. But there is still some refactoring to >> do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. >> > > the package name shouldn't be the smallest concern :-) > > > >> That logic should be moved one package level higher in a new Abstract >> class. >> In the end we will have a "gcm" package and a "adm" package (or project, >> see later in my questions) >> > > +1 > > >> >> This way the ADM logic would be able to reuse that registration code. I >> started to play a bit with this refactoring here[2], disclaimer here, I'm >> not even sure that this code compiles, is just to give an idea. >> >> So before I go further, some questions (mainly for our Android Gods ;) >> ) : >> >> - Is this a good idea (reusing your SDK) ? I think yes, even if there >> is some time and effort needed for refactoring to make it completly generic. >> > > sounds reasonable to me, to extend it and apply changes on a separate > ADM-PUSH-SDK > > >> >> - How do we build / package / deliver ? >> > > gradle? or, what does Amazon do / prefer ? > > >> We probably want 2 distinct JAR/aar. We could use profile in Maven to >> only package one feature but that sounds a bit "messy". >> What about having sub-projects, this way we would have >> aerogear-android-push and then : aerogear-android-push-gcm and >> aerogear-push-gcm. >> > > Not sure I get that, but do you mean "aerogear-android-push" > - aerogear-android-push-gcm > - aerogear-android-push-adm > > sounds reasonable > > No it isn't. For starters it will break the 2.0 API and require a 3.0 API > release. > > > >> >> - The registration flow for ADM[3] (so device <-> Amazon's server) is a >> bit different thant the GCM one >> , it's the same interface that receive the registration event and the >> push notification events. We have to check how this fit with the current >> architecture of android-push. >> >> Other challenge will be shipping ADM jar, since this one is on Maven >> and must be downloaded manually but that is for later ;) >> > > not sure, why do we need to ship it? what's the license? Why do I need a > manual download from maven ? Not following here > > Amazon's SDK is a giant zip bundle. We will need to find a way to package > it into the local maven repo. > Yeah it's a nightmare. You can get this ZIP only from their developer's portal. Once unzipped, you have to dig some folder before finding the ADM jar (the only one that we need) > > They do publish some things to central, but it looks like that is their > AWS APIs but not ADM. > Yep, I checked as well and it's only for AWS stuff :( > > > > >> >> Sebi >> >> >> [1] >> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >> [2] >> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >> [3] >> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/c4b10859/attachment.html From scm.blanc at gmail.com Tue Feb 3 10:45:41 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 3 Feb 2015 16:45:41 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: References: <54D0E431.3060709@redhat.com> Message-ID: About Licence of their SDK : https://developer.amazon.com/appsandservices/support/pml.html " you will not (a) incorporate or compile any portion of the Program Materials into your own programs or any other software, (b) distribute, sub-license or otherwise provide any portion of the Program Materials to any third party, or (c) modify or create derivative works of the Program Materials." ... On Tue, Feb 3, 2015 at 4:35 PM, Sebastien Blanc wrote: > > > On Tue, Feb 3, 2015 at 4:07 PM, Summers Pittman > wrote: > >> On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: >> >> >> >> On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc >> wrote: >> >>> Good Morning all ! >>> >>> As you might know, we are currently adding Amazon Device Messaging >>> support to the UnifiedPush server. >>> The server side has been PRed and it's now time to work on the client >>> SDK. >>> >> >> once our java-adm is on maven central, I will take a look at the PR >> >> >>> As you probably know, the amazon devices : the Kindle Fire (2nd and >>> third generation), Fire Phone and FireTV are running FireOS which is >>> basically a fork of Android OS. And since we have an Android Push SDK I >>> start looking if we could reuse it. >>> >>> First good news, is that since AGDroid 2.0, things has been nicely >>> isolated and is open for extension. But there is still some refactoring to >>> do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. >>> >> >> the package name shouldn't be the smallest concern :-) >> >> >> >>> That logic should be moved one package level higher in a new Abstract >>> class. >>> In the end we will have a "gcm" package and a "adm" package (or project, >>> see later in my questions) >>> >> >> +1 >> >> >>> >>> This way the ADM logic would be able to reuse that registration code. >>> I started to play a bit with this refactoring here[2], disclaimer here, I'm >>> not even sure that this code compiles, is just to give an idea. >>> >>> So before I go further, some questions (mainly for our Android Gods >>> ;) ) : >>> >>> - Is this a good idea (reusing your SDK) ? I think yes, even if there >>> is some time and effort needed for refactoring to make it completly generic. >>> >> >> sounds reasonable to me, to extend it and apply changes on a separate >> ADM-PUSH-SDK >> >> >>> >>> - How do we build / package / deliver ? >>> >> >> gradle? or, what does Amazon do / prefer ? >> >> >>> We probably want 2 distinct JAR/aar. We could use profile in Maven to >>> only package one feature but that sounds a bit "messy". >>> What about having sub-projects, this way we would have >>> aerogear-android-push and then : aerogear-android-push-gcm and >>> aerogear-push-gcm. >>> >> >> Not sure I get that, but do you mean "aerogear-android-push" >> - aerogear-android-push-gcm >> - aerogear-android-push-adm >> >> sounds reasonable >> >> No it isn't. For starters it will break the 2.0 API and require a 3.0 >> API release. >> >> >> >>> >>> - The registration flow for ADM[3] (so device <-> Amazon's server) is >>> a bit different thant the GCM one >>> , it's the same interface that receive the registration event and the >>> push notification events. We have to check how this fit with the current >>> architecture of android-push. >>> >>> Other challenge will be shipping ADM jar, since this one is on Maven >>> and must be downloaded manually but that is for later ;) >>> >> >> not sure, why do we need to ship it? what's the license? Why do I need >> a manual download from maven ? Not following here >> >> Amazon's SDK is a giant zip bundle. We will need to find a way to >> package it into the local maven repo. >> > Yeah it's a nightmare. You can get this ZIP only from their developer's > portal. Once unzipped, you have to dig some folder before finding the ADM > jar (the only one that we need) > >> >> They do publish some things to central, but it looks like that is their >> AWS APIs but not ADM. >> > Yep, I checked as well and it's only for AWS stuff :( > >> >> >> >> >>> >>> Sebi >>> >>> >>> [1] >>> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >>> [2] >>> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >>> [3] >>> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/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 >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/06fa832a/attachment-0001.html From cvasilak at gmail.com Tue Feb 3 10:49:52 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Tue, 3 Feb 2015 17:49:52 +0200 Subject: [aerogear-dev] iOS team meeting In-Reply-To: <7F1871C2-CEA2-4DE6-81F6-9762071650BE@gmail.com> References: <7F1871C2-CEA2-4DE6-81F6-9762071650BE@gmail.com> Message-ID: fyi, meeting minutes: Meeting ended Tue Feb 3 15:47:01 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-03-15.30.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-03-15.30.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-03-15.30.log.html > On Jan 28, 2015, at 10:23 AM, Corinne Krych wrote: > > Hello All > > Out next iOS meeting will be on Thursday 29th January 4pm (GMT+1), here is the agenda: > http://oksoclap.com/p/iOS-meeting-29thJanuary2015 > > Feel free to add topics, see you all there > > ++ > Corinne > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/f42fa44f/attachment.html From lukas.fryc at gmail.com Tue Feb 3 11:15:52 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 3 Feb 2015 17:15:52 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Great, I will proceed to the actual updates... -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/7261cb72/attachment.html From supittma at redhat.com Tue Feb 3 12:28:29 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 03 Feb 2015 12:28:29 -0500 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: References: <54D0E431.3060709@redhat.com> Message-ID: <54D1053D.5020501@redhat.com> On 02/03/2015 10:45 AM, Sebastien Blanc wrote: > About Licence of their SDK : > https://developer.amazon.com/appsandservices/support/pml.html > "you will not (a) incorporate or compile any portion of the Program > Materials into your own programs or any other software, (b) > distribute, sub-license or otherwise provide any portion of the > Program Materials to any third party, or (c) modify or create > derivative works of the Program Materials." > ... May actually be a good point. Their license also explicitly calls out that software made with the SDK should be intended for distribution in Amazon's App Store. " You may use Program Materials only in connection with Your Products intended for distribution through the Distribution Program, unless the documentation for the applicable Program Materials authorizes broader use. " I think we might need to summon a lawyer on this one. > > > On Tue, Feb 3, 2015 at 4:35 PM, Sebastien Blanc > wrote: > > > > On Tue, Feb 3, 2015 at 4:07 PM, Summers Pittman > > wrote: > > On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: >> >> >> On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc >> > wrote: >> >> Good Morning all ! >> >> As you might know, we are currently adding Amazon Device >> Messaging support to the UnifiedPush server. >> The server side has been PRed and it's now time to work >> on the client SDK. >> >> >> once our java-adm is on maven central, I will take a look at >> the PR >> >> As you probably know, the amazon devices : the Kindle >> Fire (2nd and third generation), Fire Phone and FireTV >> are running FireOS which is basically a fork of Android >> OS. And since we have an Android Push SDK I start looking >> if we could reuse it. >> >> First good news, is that since AGDroid 2.0, things has >> been nicely isolated and is open for extension. But there >> is still some refactoring to do, the "UPS Registration" >> flow/logic is still in the "gcm" package[1]. >> >> >> the package name shouldn't be the smallest concern :-) >> >> That logic should be moved one package level higher in a >> new Abstract class. >> In the end we will have a "gcm" package and a "adm" >> package (or project, see later in my questions) >> >> >> +1 >> >> >> This way the ADM logic would be able to reuse that >> registration code. I started to play a bit with this >> refactoring here[2], disclaimer here, I'm not even sure >> that this code compiles, is just to give an idea. >> >> So before I go further, some questions (mainly for our >> Android Gods ;) ) : >> >> - Is this a good idea (reusing your SDK) ? I think yes, >> even if there is some time and effort needed for >> refactoring to make it completly generic. >> >> >> sounds reasonable to me, to extend it and apply changes on a >> separate ADM-PUSH-SDK >> >> >> - How do we build / package / deliver ? >> >> >> gradle? or, what does Amazon do / prefer ? >> >> We probably want 2 distinct JAR/aar. We could use profile >> in Maven to only package one feature but that sounds a >> bit "messy". >> What about having sub-projects, this way we would have >> aerogear-android-push and then : >> aerogear-android-push-gcm and aerogear-push-gcm. >> >> >> Not sure I get that, but do you mean "aerogear-android-push" >> - aerogear-android-push-gcm >> - aerogear-android-push-adm >> >> sounds reasonable > No it isn't. For starters it will break the 2.0 API and > require a 3.0 API release. >> >> >> - The registration flow for ADM[3] (so device <-> >> Amazon's server) is a bit different thant the GCM one >> , it's the same interface that receive the registration >> event and the push notification events. We have to check >> how this fit with the current architecture of android-push. >> >> Other challenge will be shipping ADM jar, since this one >> is on Maven and must be downloaded manually but that is >> for later ;) >> >> >> not sure, why do we need to ship it? what's the license? Why >> do I need a manual download from maven ? Not following here > Amazon's SDK is a giant zip bundle. We will need to find a way > to package it into the local maven repo. > > Yeah it's a nightmare. You can get this ZIP only from their > developer's portal. Once unzipped, you have to dig some folder > before finding the ADM jar (the only one that we need) > > > They do publish some things to central, but it looks like that > is their AWS APIs but not ADM. > > Yep, I checked as well and it's only for AWS stuff :( > > > >> >> Sebi >> >> >> [1]https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >> [2] >> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >> [3] >> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > 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/20150203/34c4e36b/attachment-0001.html From bruno at abstractj.org Tue Feb 3 14:10:55 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 3 Feb 2015 17:10:55 -0200 Subject: [aerogear-dev] Cookbook backend Message-ID: <20150203191055.GA31478@abstractj.org> Good morning, I'm struggling to understand why we have submodules here: https://github.com/aerogear/aerogear-backend-cookbook. Do we have a good reason for it? To give you some context, I already tagged the cookbook backend as 0.0.1 ("stable") and would like to generate the binaries from this tag. To be it doesn't make any sense on having submodules there and we have 2 alternatives: 1. Move the repositories to the aerogear-backend-cookbook 2. Remove the submodules Thoughts? -- abstractj PGP: 0x84DC9914 From lholmqui at redhat.com Tue Feb 3 14:17:28 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 3 Feb 2015 14:17:28 -0500 Subject: [aerogear-dev] AeroGear.Ajax Message-ID: <7F000619-B90E-42CA-BE27-6C4D2DCC7CCF@redhat.com> While i was looking through the JS lib, i realized that AeroGear.ajax is really only used by the UnifiedPush client sdk. Yes, it?s used by the OAuth2 adapter for Authz, but that is getting deprecated. I plan on sending a PR that will basically take AeroGear.ajax and merge it with the UnifiedPush client sdk. I think the original thought i had with this part of the library is that it would be used internally for other parts, such as pipeline and auth but those have been removed so i don?t think it makes sense to keep AeroGear.ajax around. I?ll be creating a JIRA with this info -Luke From scm.blanc at gmail.com Tue Feb 3 14:22:33 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 3 Feb 2015 20:22:33 +0100 Subject: [aerogear-dev] AeroGear.Ajax In-Reply-To: <7F000619-B90E-42CA-BE27-6C4D2DCC7CCF@redhat.com> References: <7F000619-B90E-42CA-BE27-6C4D2DCC7CCF@redhat.com> Message-ID: +1 On Tue, Feb 3, 2015 at 8:17 PM, Lucas Holmquist wrote: > While i was looking through the JS lib, i realized that AeroGear.ajax is > really only used by the UnifiedPush client sdk. Yes, it?s used by the > OAuth2 adapter for Authz, but that is getting deprecated. > > I plan on sending a PR that will basically take AeroGear.ajax and merge it > with the UnifiedPush client sdk. > > I think the original thought i had with this part of the library is that > it would be used internally for other parts, such as pipeline and auth but > those have been removed so i don?t think it makes sense to keep > AeroGear.ajax around. > > I?ll be creating a JIRA with this info > > -Luke > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/6ffcf6d2/attachment.html From bruno at abstractj.org Tue Feb 3 14:29:01 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 3 Feb 2015 17:29:01 -0200 Subject: [aerogear-dev] Shoot backend broken layout Message-ID: <20150203192901.GA31862@abstractj.org> Good morning, we would like to announce the deliverables for OAuth2 this week, although the backend layout seems broken http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg. This is not a deal breaker, but I would love some help. -- abstractj PGP: 0x84DC9914 From agalante at redhat.com Tue Feb 3 14:38:53 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 3 Feb 2015 14:38:53 -0500 (EST) Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: <20150203192901.GA31862@abstractj.org> References: <20150203192901.GA31862@abstractj.org> Message-ID: <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> there must be an unclosed html tag or unclear floats. Can I see the source code? ----- Original Message ----- From: "Bruno Oliveira" To: "AeroGear Dev" Sent: Tuesday, February 3, 2015 4:29:01 PM Subject: [aerogear-dev] Shoot backend broken layout Good morning, we would like to announce the deliverables for OAuth2 this week, although the backend layout seems broken http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg. This is not a deal breaker, but I would love some help. -- 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 Feb 3 14:41:56 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 3 Feb 2015 20:41:56 +0100 Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> Message-ID: If I'm correct it's here https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html On Tue, Feb 3, 2015 at 8:38 PM, Andres Galante wrote: > there must be an unclosed html tag or unclear floats. Can I see the source > code? > > ----- Original Message ----- > From: "Bruno Oliveira" > To: "AeroGear Dev" > Sent: Tuesday, February 3, 2015 4:29:01 PM > Subject: [aerogear-dev] Shoot backend broken layout > > Good morning, we would like to announce the deliverables for OAuth2 this > week, although the backend layout seems broken > http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg. > > This is not a deal breaker, but I would love some 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/4b7a873d/attachment.html From matzew at apache.org Tue Feb 3 14:43:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 20:43:07 +0100 Subject: [aerogear-dev] AeroGear.Ajax In-Reply-To: References: <7F000619-B90E-42CA-BE27-6C4D2DCC7CCF@redhat.com> Message-ID: +1 On Tuesday, February 3, 2015, Sebastien Blanc wrote: > +1 > > On Tue, Feb 3, 2015 at 8:17 PM, Lucas Holmquist > wrote: > >> While i was looking through the JS lib, i realized that AeroGear.ajax is >> really only used by the UnifiedPush client sdk. Yes, it?s used by the >> OAuth2 adapter for Authz, but that is getting deprecated. >> >> I plan on sending a PR that will basically take AeroGear.ajax and merge >> it with the UnifiedPush client sdk. >> >> I think the original thought i had with this part of the library is that >> it would be used internally for other parts, such as pipeline and auth but >> those have been removed so i don?t think it makes sense to keep >> AeroGear.ajax around. >> >> I?ll be creating a JIRA with this info >> >> -Luke >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/532f818a/attachment.html From bruno at abstractj.org Tue Feb 3 14:43:16 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 3 Feb 2015 17:43:16 -0200 Subject: [aerogear-dev] Buddies at cookbooks Message-ID: <20150203194316.GA32364@abstractj.org> Morning buddies, I'm definitely exceeding my quota of e-mails today, but this is necessary. At the cookbooks we have the backend "Buddies", looking at the sources and after a chat with Passos, I was struggling to understand why this project exists. If I need to start WildFly + run Maven only to see a list of developers. I would totally give up on try our SDK, because it defeats the purpose of simplicity. I'm not saying that this doesn't help, but we should try to make it simple with the usage of public endpoints, like Passos has been doing on https://github.com/aerogear/aerogear-android-cookbook/tree/master/ChuckNorrisJokes. If the goal is to display the list of developers, maybe we should stick to the public GitHub API? -- abstractj PGP: 0x84DC9914 From matzew at apache.org Tue Feb 3 14:43:42 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 20:43:42 +0100 Subject: [aerogear-dev] Amazon Push SDK and Android Push SDK In-Reply-To: <54D1053D.5020501@redhat.com> References: <54D0E431.3060709@redhat.com> <54D1053D.5020501@redhat.com> Message-ID: Good catch, Summers! Let me follow up on that! On Tuesday, February 3, 2015, Summers Pittman wrote: > On 02/03/2015 10:45 AM, Sebastien Blanc wrote: > > About Licence of their SDK : > https://developer.amazon.com/appsandservices/support/pml.html > " you will not (a) incorporate or compile any portion of the Program > Materials into your own programs or any other software, (b) distribute, > sub-license or otherwise provide any portion of the Program Materials to > any third party, or (c) modify or create derivative works of the Program > Materials." > ... > > May actually be a good point. Their license also explicitly calls out > that software made with the SDK should be intended for distribution in > Amazon's App Store. > > " You may use Program Materials only in connection with Your Products > intended for distribution through the Distribution Program, unless the > documentation for the applicable Program Materials authorizes broader use. " > > I think we might need to summon a lawyer on this one. > > > > > > On Tue, Feb 3, 2015 at 4:35 PM, Sebastien Blanc > wrote: > >> >> >> On Tue, Feb 3, 2015 at 4:07 PM, Summers Pittman > > wrote: >> >>> On 02/03/2015 09:56 AM, Matthias Wessendorf wrote: >>> >>> >>> >>> On Tue, Feb 3, 2015 at 2:31 PM, Sebastien Blanc >> > wrote: >>> >>>> Good Morning all ! >>>> >>>> As you might know, we are currently adding Amazon Device Messaging >>>> support to the UnifiedPush server. >>>> The server side has been PRed and it's now time to work on the client >>>> SDK. >>>> >>> >>> once our java-adm is on maven central, I will take a look at the PR >>> >>> >>>> As you probably know, the amazon devices : the Kindle Fire (2nd and >>>> third generation), Fire Phone and FireTV are running FireOS which is >>>> basically a fork of Android OS. And since we have an Android Push SDK I >>>> start looking if we could reuse it. >>>> >>>> First good news, is that since AGDroid 2.0, things has been nicely >>>> isolated and is open for extension. But there is still some refactoring to >>>> do, the "UPS Registration" flow/logic is still in the "gcm" package[1]. >>>> >>> >>> the package name shouldn't be the smallest concern :-) >>> >>> >>> >>>> That logic should be moved one package level higher in a new Abstract >>>> class. >>>> In the end we will have a "gcm" package and a "adm" package (or >>>> project, see later in my questions) >>>> >>> >>> +1 >>> >>> >>>> >>>> This way the ADM logic would be able to reuse that registration code. >>>> I started to play a bit with this refactoring here[2], disclaimer here, I'm >>>> not even sure that this code compiles, is just to give an idea. >>>> >>>> So before I go further, some questions (mainly for our Android Gods >>>> ;) ) : >>>> >>>> - Is this a good idea (reusing your SDK) ? I think yes, even if there >>>> is some time and effort needed for refactoring to make it completly generic. >>>> >>> >>> sounds reasonable to me, to extend it and apply changes on a separate >>> ADM-PUSH-SDK >>> >>> >>>> >>>> - How do we build / package / deliver ? >>>> >>> >>> gradle? or, what does Amazon do / prefer ? >>> >>> >>>> We probably want 2 distinct JAR/aar. We could use profile in Maven to >>>> only package one feature but that sounds a bit "messy". >>>> What about having sub-projects, this way we would have >>>> aerogear-android-push and then : aerogear-android-push-gcm and >>>> aerogear-push-gcm. >>>> >>> >>> Not sure I get that, but do you mean "aerogear-android-push" >>> - aerogear-android-push-gcm >>> - aerogear-android-push-adm >>> >>> sounds reasonable >>> >>> No it isn't. For starters it will break the 2.0 API and require a 3.0 >>> API release. >>> >>> >>> >>>> >>>> - The registration flow for ADM[3] (so device <-> Amazon's server) is >>>> a bit different thant the GCM one >>>> , it's the same interface that receive the registration event and the >>>> push notification events. We have to check how this fit with the current >>>> architecture of android-push. >>>> >>>> Other challenge will be shipping ADM jar, since this one is on Maven >>>> and must be downloaded manually but that is for later ;) >>>> >>> >>> not sure, why do we need to ship it? what's the license? Why do I need >>> a manual download from maven ? Not following here >>> >>> Amazon's SDK is a giant zip bundle. We will need to find a way to >>> package it into the local maven repo. >>> >> Yeah it's a nightmare. You can get this ZIP only from their >> developer's portal. Once unzipped, you have to dig some folder before >> finding the ADM jar (the only one that we need) >> >>> >>> They do publish some things to central, but it looks like that is their >>> AWS APIs but not ADM. >>> >> Yep, I checked as well and it's only for AWS stuff :( >> >>> >>> >>> >>> >>>> >>>> Sebi >>>> >>>> >>>> [1] >>>> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java >>>> [2] >>>> https://github.com/sebastienblanc/aerogear-android-push/tree/refactoring >>>> [3] >>>> https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> >>>> https://lists.jboss.org/mailman/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.org https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Summers Pittman >>> >>Phone:404 941 4698 >>> >>Java is my crack. >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/ebd9f6c9/attachment-0001.html From matzew at apache.org Tue Feb 3 14:47:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 20:47:16 +0100 Subject: [aerogear-dev] Cookbook backend In-Reply-To: <20150203191055.GA31478@abstractj.org> References: <20150203191055.GA31478@abstractj.org> Message-ID: Yeah, submodules suck! :-) Tomorrow I will also file me a JIRA to move AeroDoc in here, instead of its own repo. On Tuesday, February 3, 2015, Bruno Oliveira wrote: > Good morning, I'm struggling to understand why we have submodules here: > https://github.com/aerogear/aerogear-backend-cookbook. Do we have a good > reason for it? > > To give you some context, I already tagged the cookbook backend as 0.0.1 > ("stable") and would like to generate the binaries from this tag. > > To be it doesn't make any sense on having submodules there and we have 2 > alternatives: > > 1. Move the repositories to the aerogear-backend-cookbook > 2. Remove the submodules > > Thoughts? > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/660b9cad/attachment.html From corinnekrych at gmail.com Tue Feb 3 14:48:26 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 3 Feb 2015 20:48:26 +0100 Subject: [aerogear-dev] Cookbook backend In-Reply-To: <20150203191055.GA31478@abstractj.org> References: <20150203191055.GA31478@abstractj.org> Message-ID: <4F542450-7F2A-4DE9-9FC2-813E948E23C6@gmail.com> The iea behind submodules was to group all demo from a central repos. aerogear-ios-cookbook is doing the same. I initially borrow the idea from Luke :P Some submodules can not be moved to cookbook like PushQuickstart so I?d go for solution 2 ++ Corinne > On 03 Feb 2015, at 20:10, Bruno Oliveira wrote: > > Good morning, I'm struggling to understand why we have submodules here: > https://github.com/aerogear/aerogear-backend-cookbook. Do we have a good > reason for it? > > To give you some context, I already tagged the cookbook backend as 0.0.1 > ("stable") and would like to generate the binaries from this tag. > > To be it doesn't make any sense on having submodules there and we have 2 > alternatives: > > 1. Move the repositories to the aerogear-backend-cookbook > 2. Remove the submodules > > Thoughts? > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Tue Feb 3 14:49:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 20:49:07 +0100 Subject: [aerogear-dev] Buddies at cookbooks In-Reply-To: <20150203194316.GA32364@abstractj.org> References: <20150203194316.GA32364@abstractj.org> Message-ID: On Tuesday, February 3, 2015, Bruno Oliveira wrote: > Morning buddies, > > I'm definitely exceeding my quota of e-mails today, but this is > necessary. At the cookbooks we have the backend "Buddies", looking at > the sources and after a chat with Passos, I was struggling to understand > why this project exists. > > If I need to start WildFly + run Maven only to see a list of developers. I > would totally give up on try > our SDK, because it defeats the purpose of simplicity. Agree! > > I'm not saying that this doesn't help, but we should try to make it > simple with the usage of public endpoints, like Passos has been doing on > > https://github.com/aerogear/aerogear-android-cookbook/tree/master/ChuckNorrisJokes > . > If the goal is to display the list of developers, maybe we should stick > to the public GitHub API? +9001 Lets do that! I can create a JIRA for this! > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/8f4800d7/attachment.html From matzew at apache.org Tue Feb 3 14:55:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 20:55:02 +0100 Subject: [aerogear-dev] Cookbook backend In-Reply-To: <4F542450-7F2A-4DE9-9FC2-813E948E23C6@gmail.com> References: <20150203191055.GA31478@abstractj.org> <4F542450-7F2A-4DE9-9FC2-813E948E23C6@gmail.com> Message-ID: On Tuesday, February 3, 2015, Corinne Krych wrote: > The iea behind submodules was to group all demo from a central repos. > aerogear-ios-cookbook is doing the same. I initially borrow the idea from > Luke :P > Some submodules can not be moved to cookbook like PushQuickstart hrm, not sure :-) Perhaps we should move that. I will create a ticket to trsck this > so I?d go for solution 2 > > ++ > Corinne > > > On 03 Feb 2015, at 20:10, Bruno Oliveira > wrote: > > > > Good morning, I'm struggling to understand why we have submodules here: > > https://github.com/aerogear/aerogear-backend-cookbook. Do we have a good > > reason for it? > > > > To give you some context, I already tagged the cookbook backend as 0.0.1 > > ("stable") and would like to generate the binaries from this tag. > > > > To be it doesn't make any sense on having submodules there and we have 2 > > alternatives: > > > > 1. Move the repositories to the aerogear-backend-cookbook > > 2. Remove the submodules > > > > Thoughts? > > > > -- > > > > 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 -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/247eb046/attachment.html From agalante at redhat.com Tue Feb 3 15:00:47 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 3 Feb 2015 15:00:47 -0500 (EST) Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> Message-ID: <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> I suspect it has something to do with either the "<3" here: https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html#L70 Try escaping it as <. OR the negative margin here: https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/css/style.css#L49 Is there any way I can preview this? Should I install it? Thanks ----- Original Message ----- From: "Sebastien Blanc" To: "AeroGear Developer Mailing List" Sent: Tuesday, February 3, 2015 4:41:56 PM Subject: Re: [aerogear-dev] Shoot backend broken layout If I'm correct it's here https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html On Tue, Feb 3, 2015 at 8:38 PM, Andres Galante < agalante at redhat.com > wrote: there must be an unclosed html tag or unclear floats. Can I see the source code? ----- Original Message ----- From: "Bruno Oliveira" < bruno at abstractj.org > To: "AeroGear Dev" < aerogear-dev at lists.jboss.org > Sent: Tuesday, February 3, 2015 4:29:01 PM Subject: [aerogear-dev] Shoot backend broken layout Good morning, we would like to announce the deliverables for OAuth2 this week, although the backend layout seems broken http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg . This is not a deal breaker, but I would love some 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 _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From daniel at passos.me Tue Feb 3 15:05:52 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 3 Feb 2015 18:05:52 -0200 Subject: [aerogear-dev] Cookbook backend In-Reply-To: References: <20150203191055.GA31478@abstractj.org> <4F542450-7F2A-4DE9-9FC2-813E948E23C6@gmail.com> Message-ID: \o/ -- Passos On Tue, Feb 3, 2015 at 5:55 PM, Matthias Wessendorf wrote: > > > On Tuesday, February 3, 2015, Corinne Krych > wrote: > >> The iea behind submodules was to group all demo from a central repos. >> aerogear-ios-cookbook is doing the same. I initially borrow the idea from >> Luke :P >> Some submodules can not be moved to cookbook like PushQuickstart > > > hrm, not sure :-) Perhaps we should move that. I will create a ticket to > trsck this > > >> so I?d go for solution 2 >> >> ++ >> Corinne >> >> > On 03 Feb 2015, at 20:10, Bruno Oliveira wrote: >> > >> > Good morning, I'm struggling to understand why we have submodules here: >> > https://github.com/aerogear/aerogear-backend-cookbook. Do we have a >> good >> > reason for it? >> > >> > To give you some context, I already tagged the cookbook backend as 0.0.1 >> > ("stable") and would like to generate the binaries from this tag. >> > >> > To be it doesn't make any sense on having submodules there and we have 2 >> > alternatives: >> > >> > 1. Move the repositories to the aerogear-backend-cookbook >> > 2. Remove the submodules >> > >> > Thoughts? >> > >> > -- >> > >> > 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 > > > > -- > 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/20150203/c8399fb3/attachment-0001.html From daniel at passos.me Tue Feb 3 15:08:49 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 3 Feb 2015 18:08:49 -0200 Subject: [aerogear-dev] AeroGear.Ajax In-Reply-To: References: <7F000619-B90E-42CA-BE27-6C4D2DCC7CCF@redhat.com> Message-ID: +1 -- Passos On Tue, Feb 3, 2015 at 5:43 PM, Matthias Wessendorf wrote: > +1 > > > On Tuesday, February 3, 2015, Sebastien Blanc wrote: > >> +1 >> >> On Tue, Feb 3, 2015 at 8:17 PM, Lucas Holmquist >> wrote: >> >>> While i was looking through the JS lib, i realized that AeroGear.ajax >>> is really only used by the UnifiedPush client sdk. Yes, it?s used by the >>> OAuth2 adapter for Authz, but that is getting deprecated. >>> >>> I plan on sending a PR that will basically take AeroGear.ajax and merge >>> it with the UnifiedPush client sdk. >>> >>> I think the original thought i had with this part of the library is that >>> it would be used internally for other parts, such as pipeline and auth but >>> those have been removed so i don?t think it makes sense to keep >>> AeroGear.ajax around. >>> >>> I?ll be creating a JIRA with this info >>> >>> -Luke >>> _______________________________________________ >>> 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/20150203/2de14034/attachment.html From daniel at passos.me Tue Feb 3 15:12:47 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 3 Feb 2015 18:12:47 -0200 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Luk??, Let me do it on Android land. -- Passos On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? wrote: > Great, I will proceed to the actual updates... > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150203/19f01197/attachment.html From corinnekrych at gmail.com Tue Feb 3 15:27:44 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 3 Feb 2015 21:27:44 +0100 Subject: [aerogear-dev] Cookbook backend In-Reply-To: References: <20150203191055.GA31478@abstractj.org> <4F542450-7F2A-4DE9-9FC2-813E948E23C6@gmail.com> Message-ID: <6C13EF10-3959-48B3-AD60-F5800F298C5E@gmail.com> Perfect! ++ Corinne > On 03 Feb 2015, at 21:05, Daniel Passos wrote: > > \o/ > > -- Passos > > On Tue, Feb 3, 2015 at 5:55 PM, Matthias Wessendorf wrote: > > > On Tuesday, February 3, 2015, Corinne Krych wrote: > The iea behind submodules was to group all demo from a central repos. aerogear-ios-cookbook is doing the same. I initially borrow the idea from Luke :P > Some submodules can not be moved to cookbook like PushQuickstart > > hrm, not sure :-) Perhaps we should move that. I will create a ticket to trsck this > > so I?d go for solution 2 > > ++ > Corinne > > > On 03 Feb 2015, at 20:10, Bruno Oliveira wrote: > > > > Good morning, I'm struggling to understand why we have submodules here: > > https://github.com/aerogear/aerogear-backend-cookbook. Do we have a good > > reason for it? > > > > To give you some context, I already tagged the cookbook backend as 0.0.1 > > ("stable") and would like to generate the binaries from this tag. > > > > To be it doesn't make any sense on having submodules there and we have 2 > > alternatives: > > > > 1. Move the repositories to the aerogear-backend-cookbook > > 2. Remove the submodules > > > > Thoughts? > > > > -- > > > > 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 > > > -- > 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 Tue Feb 3 16:13:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 22:13:16 +0100 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint Message-ID: Hi, I recently noticed that we are (IMO) incorrectly returning 200 (OK): https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 Since we really do submit an async job here, and its processing may not have been started when we do return the 200 (OK), I'd like to propose a slight change here to instead use 202 (Accepted): http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 If the team is OK (ha ha) with this, I will track this in JIRA -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/20150203/b6de2a79/attachment.html From scm.blanc at gmail.com Tue Feb 3 16:57:37 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Tue, 3 Feb 2015 22:57:37 +0100 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: References: Message-ID: <5B95E98E-6F55-49F9-ACBD-C363B3BE3BBC@gmail.com> Agreed but we should make that clear in the clients (Java and Node) when receiving the response (I'm thinking about the callbacks) , that said, an javadoc/comment should de enough. Envoy? de mon iPhone > Le 3 f?vr. 2015 ? 22:13, Matthias Wessendorf a ?crit : > > Hi, > > I recently noticed that we are (IMO) incorrectly returning 200 (OK): > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 > > Since we really do submit an async job here, and its processing may not have been started when we do return the 200 (OK), I'd like to propose a slight change here to instead use 202 (Accepted): > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 > > If the team is OK (ha ha) with this, I will track this in JIRA > > -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/20150203/5d49b37a/attachment.html From matzew at apache.org Tue Feb 3 17:27:11 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 3 Feb 2015 23:27:11 +0100 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: <5B95E98E-6F55-49F9-ACBD-C363B3BE3BBC@gmail.com> References: <5B95E98E-6F55-49F9-ACBD-C363B3BE3BBC@gmail.com> Message-ID: On Tue, Feb 3, 2015 at 10:57 PM, S?bastien Blanc wrote: > Agreed but we should make that clear in the clients (Java and Node) when > receiving the response (I'm thinking about the callbacks) , that said, an > javadoc/comment should de enough. > Luckily they say nothing about the actual status code: * https://aerogear.org/docs/specs/aerogear-unifiedpush-java-client/org/jboss/aerogear/unifiedpush/message/MessageResponseCallback.html#onComplete(int) * https://aerogear.org/docs/specs/aerogear-unifiedpush-nodejs-client/ On JavaDoc, it just says "statusCode - the status code as returned by the server." => Nothing to change. More important is to update this: https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST But that's covered with the JavaDoc update, required for the change from 200 -> 202 -Matthias > > Envoy? de mon iPhone > > Le 3 f?vr. 2015 ? 22:13, Matthias Wessendorf a ?crit : > > Hi, > > I recently noticed that we are (IMO) incorrectly returning 200 (OK): > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 > > Since we really do submit an async job here, and its processing may not > have been started when we do return the 200 (OK), I'd like to propose a > slight change here to instead use 202 (Accepted): > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 > > If the team is OK (ha ha) with this, I will track this in JIRA > > -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/20150203/4523cef7/attachment-0001.html From corinnekrych at gmail.com Wed Feb 4 03:40:35 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 4 Feb 2015 09:40:35 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: <26198599-49E7-4FE5-BB26-E9A29A65ED8A@gmail.com> PR welcome for iOS repo :) ++ Corinne > On 03 Feb 2015, at 17:15, Luk?? Fry? wrote: > > Great, I will proceed to the actual updates... > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Wed Feb 4 03:50:30 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 4 Feb 2015 09:50:30 +0100 Subject: [aerogear-dev] Cookbook backend In-Reply-To: <6C13EF10-3959-48B3-AD60-F5800F298C5E@gmail.com> References: <20150203191055.GA31478@abstractj.org> <4F542450-7F2A-4DE9-9FC2-813E948E23C6@gmail.com> <6C13EF10-3959-48B3-AD60-F5800F298C5E@gmail.com> Message-ID: Ok, I have created two JIRAs for me, to actually perform the moves: * https://issues.jboss.org/browse/AEROGEAR-1613 * https://issues.jboss.org/browse/AEROGEAR-1614 On Tue, Feb 3, 2015 at 9:27 PM, Corinne Krych wrote: > Perfect! > > ++ > Corinne > > On 03 Feb 2015, at 21:05, Daniel Passos wrote: > > > > \o/ > > > > -- Passos > > > > On Tue, Feb 3, 2015 at 5:55 PM, Matthias Wessendorf > wrote: > > > > > > On Tuesday, February 3, 2015, Corinne Krych > wrote: > > The iea behind submodules was to group all demo from a central repos. > aerogear-ios-cookbook is doing the same. I initially borrow the idea from > Luke :P > > Some submodules can not be moved to cookbook like PushQuickstart > > > > hrm, not sure :-) Perhaps we should move that. I will create a ticket to > trsck this > > > > so I?d go for solution 2 > > > > ++ > > Corinne > > > > > On 03 Feb 2015, at 20:10, Bruno Oliveira wrote: > > > > > > Good morning, I'm struggling to understand why we have submodules here: > > > https://github.com/aerogear/aerogear-backend-cookbook. Do we have a > good > > > reason for it? > > > > > > To give you some context, I already tagged the cookbook backend as > 0.0.1 > > > ("stable") and would like to generate the binaries from this tag. > > > > > > To be it doesn't make any sense on having submodules there and we have > 2 > > > alternatives: > > > > > > 1. Move the repositories to the aerogear-backend-cookbook > > > 2. Remove the submodules > > > > > > Thoughts? > > > > > > -- > > > > > > 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 > > > > > > -- > > Sent from Gmail Mobile > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/ef8e3dfb/attachment.html From matzew at apache.org Wed Feb 4 04:00:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 4 Feb 2015 10:00:18 +0100 Subject: [aerogear-dev] Buddies at cookbooks In-Reply-To: References: <20150203194316.GA32364@abstractj.org> Message-ID: On Tue, Feb 3, 2015 at 8:49 PM, Matthias Wessendorf wrote: > > > On Tuesday, February 3, 2015, Bruno Oliveira wrote: > >> Morning buddies, >> >> I'm definitely exceeding my quota of e-mails today, but this is >> necessary. At the cookbooks we have the backend "Buddies", looking at >> the sources and after a chat with Passos, I was struggling to understand >> why this project exists. >> >> If I need to start WildFly + run Maven only to see a list of developers. >> I would totally give up on try >> our SDK, because it defeats the purpose of simplicity. > > > > Agree! > > >> >> I'm not saying that this doesn't help, but we should try to make it >> simple with the usage of public endpoints, like Passos has been doing on >> >> https://github.com/aerogear/aerogear-android-cookbook/tree/master/ChuckNorrisJokes >> . >> If the goal is to display the list of developers, maybe we should stick >> to the public GitHub API? > > > +9001 > > Lets do that! I can create a JIRA for this! > https://issues.jboss.org/browse/AGIOS-377 Not sure if that's a topic for next iOS release (clean up the Buddies demo), but the ticket helps us to track it > > >> >> -- >> >> abstractj >> PGP: 0x84DC9914 >> _______________________________________________ >> 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/20150204/2c8fe81e/attachment.html From scm.blanc at gmail.com Wed Feb 4 04:14:40 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 4 Feb 2015 10:14:40 +0100 Subject: [aerogear-dev] [RELEASE] java-adm 0.1.0 has been staged Message-ID: Good morning, I'm pleased to announce that java-adm 0.1.0 has been staged : https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4780/ This is the first release ! The java-adm library is a connector to the Amazon Device Messaging Network. For instance, this library will be used by the UnifiedPush server for ADM support but it can be used anywhere else. If I heard nothing , I will push the button this Friday. Sebi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/b845fcd7/attachment.html From matzew at apache.org Wed Feb 4 04:19:22 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 4 Feb 2015 10:19:22 +0100 Subject: [aerogear-dev] [RELEASE] java-adm 0.1.0 has been staged In-Reply-To: References: Message-ID: I have reviewed and refactored some code for the 0.1.0 release, therefore I am +1 -M On Wed, Feb 4, 2015 at 10:14 AM, Sebastien Blanc wrote: > Good morning, > > I'm pleased to announce that java-adm 0.1.0 has been staged : > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4780/ > > This is the first release ! The java-adm library is a connector to the > Amazon Device Messaging Network. For instance, this library will be used by > the UnifiedPush server for ADM support but it can be used anywhere else. > > If I heard nothing , I will push the button this Friday. > > 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/20150204/d2ab40e3/attachment.html From bruno at abstractj.org Wed Feb 4 07:32:27 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 4 Feb 2015 10:32:27 -0200 Subject: [aerogear-dev] Buddies at cookbooks In-Reply-To: References: <20150203194316.GA32364@abstractj.org> Message-ID: <20150204123227.GA35538@abstractj.org> Thank you On 2015-02-04, Matthias Wessendorf wrote: > On Tue, Feb 3, 2015 at 8:49 PM, Matthias Wessendorf > wrote: > > > > > > > On Tuesday, February 3, 2015, Bruno Oliveira wrote: > > > >> Morning buddies, > >> > >> I'm definitely exceeding my quota of e-mails today, but this is > >> necessary. At the cookbooks we have the backend "Buddies", looking at > >> the sources and after a chat with Passos, I was struggling to understand > >> why this project exists. > >> > >> If I need to start WildFly + run Maven only to see a list of developers. > >> I would totally give up on try > >> our SDK, because it defeats the purpose of simplicity. > > > > > > > > Agree! > > > > > >> > >> I'm not saying that this doesn't help, but we should try to make it > >> simple with the usage of public endpoints, like Passos has been doing on > >> > >> https://github.com/aerogear/aerogear-android-cookbook/tree/master/ChuckNorrisJokes > >> . > >> If the goal is to display the list of developers, maybe we should stick > >> to the public GitHub API? > > > > > > +9001 > > > > Lets do that! I can create a JIRA for this! > > > > https://issues.jboss.org/browse/AGIOS-377 > > Not sure if that's a topic for next iOS release (clean up the Buddies > demo), but the ticket helps us to track it > > > > > > > > >> > >> -- > >> > >> abstractj > >> PGP: 0x84DC9914 > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > > > > > > -- > > Sent from Gmail Mobile > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From lholmqui at redhat.com Wed Feb 4 08:15:58 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Wed, 4 Feb 2015 08:15:58 -0500 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: References: <5B95E98E-6F55-49F9-ACBD-C363B3BE3BBC@gmail.com> Message-ID: <02D51EBF-884F-4F78-B808-B6EC1CFF9D31@redhat.com> > On Feb 3, 2015, at 5:27 PM, Matthias Wessendorf wrote: > > > > On Tue, Feb 3, 2015 at 10:57 PM, S?bastien Blanc > wrote: > Agreed but we should make that clear in the clients (Java and Node) when receiving the response (I'm thinking about the callbacks) , that said, an javadoc/comment should de enough. > > Luckily they say nothing about the actual status code: > * https://aerogear.org/docs/specs/aerogear-unifiedpush-java-client/org/jboss/aerogear/unifiedpush/message/MessageResponseCallback.html#onComplete(int) > * https://aerogear.org/docs/specs/aerogear-unifiedpush-nodejs-client/ yea, i always thought this was a fire and forget thing anyway > > On JavaDoc, it just says "statusCode - the status code as returned by the server." > > => Nothing to change. > > More important is to update this: > https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST > > But that's covered with the JavaDoc update, required for the change from 200 -> 202 > > -Matthias > > > > Envoy? de mon iPhone > > Le 3 f?vr. 2015 ? 22:13, Matthias Wessendorf > a ?crit : > >> Hi, >> >> I recently noticed that we are (IMO) incorrectly returning 200 (OK): >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 >> >> Since we really do submit an async job here, and its processing may not have been started when we do return the 200 (OK), I'd like to propose a slight change here to instead use 202 (Accepted): >> >> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 >> >> If the team is OK (ha ha) with this, I will track this in JIRA >> >> -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/20150204/28b53dff/attachment.html From bruno at abstractj.org Wed Feb 4 08:48:57 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 4 Feb 2015 11:48:57 -0200 Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> Message-ID: <20150204134857.GA36431@abstractj.org> Hi my friend, not sure if it's helpful, but I deployed the latest changes on OpenShift: https://shoot-aerogear.rhcloud.com/shoot/photos/ username: user password: password On 2015-02-03, Andres Galante wrote: > I suspect it has something to do with either the "<3" here: > > https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html#L70 > > Try escaping it as <. > > OR the negative margin here: > > https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/css/style.css#L49 > > Is there any way I can preview this? Should I install it? > > Thanks > > ----- Original Message ----- > From: "Sebastien Blanc" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, February 3, 2015 4:41:56 PM > Subject: Re: [aerogear-dev] Shoot backend broken layout > > If I'm correct it's here https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html > > On Tue, Feb 3, 2015 at 8:38 PM, Andres Galante < agalante at redhat.com > wrote: > > > there must be an unclosed html tag or unclear floats. Can I see the source code? > > ----- Original Message ----- > From: "Bruno Oliveira" < bruno at abstractj.org > > To: "AeroGear Dev" < aerogear-dev at lists.jboss.org > > Sent: Tuesday, February 3, 2015 4:29:01 PM > Subject: [aerogear-dev] Shoot backend broken layout > > Good morning, we would like to announce the deliverables for OAuth2 this > week, although the backend layout seems broken > http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg . > > This is not a deal breaker, but I would love some 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 Wed Feb 4 08:53:12 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 4 Feb 2015 14:53:12 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: Message-ID: I have created AGPUSH-1257 and AGPUSH-1258 On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf wrote: > Hi, > > earlier this week there was some discussion about storing the payload of > the push notifications ([1]). > > Right now, we store some metrics (e.g. client that send the push, number > of devices, deliveryStatus etc) *and* the entire content of push > notification. This includes custom key/value pairs, the name of the sound > file or even the size of the badge. > > Is all of that, storing the entire push notification payload really > needed? *No!* > > What do we need, and why? > > For counting the number of sent pushes (over time), the metrics are good > enough. We do *NOT* need any of the push content for that, that's correct! > > But we want to do more on the 1.1.0 release. We want to introduce some > analytic features, to give our app developers (our users) a better > understanding of their push usage (see [2]). > > In order to see details on how successful a push was (or not), we need to > only store the value of the alert key: > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > > Ok, let's change that (see [3])! > > For our app developers, using the UPS to reach out to their mobile app > users ("user engagement"), it's important to understand which push was more > successful: > > - "Get 10% discount today" (sent on a Monday) > - "Our shop got new site, check it out and get 5% discount" (sent on a > Friday) > > With the upcoming analytics we can help them to improve usage of their > app. User interaction is very important to a successful mobile application > and push is a key driver here! Our app developers want an app that is > actively used by their users (Nobody wants his app sitting on the last page > of the device or, even worse, in a folder together with Apple-Maps). > Therefore it's critical for our app developers to understand the relevance > of their push messages sent and how it impacts the usage of their app. > That's why we do the analytics described in [2]. And, yes - only the alert, > not the entire payload is needed for that. > Privacy > > On the mentioned PR there was also some discussion about privacy > violations and stuff, when we store the content of the notification. An > example where *sensitive* data was sent over push was given. Something > like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 > p.m" > > 1. This is not how push notifications are used for mobile apps. Push > is to signal, not carry actual (sensitive) data around. > 2. In a lot of countries, at least almost all European countries, you > are not even allowed, by EU law, to give "data" to 3rd party providers > (like the push-networks of Microsoft, Apple or Google). > > How does the actual (sensitive) data come to an app? > > As said above a push is used to signal/ping an app, to indicate that there > is real data for the mobile app user. In the background the mobile app > tries to connect to the backend of the company, running/maintaining the > mobile app. After the real data was fetched, "local notifcations" are used > to give the user a visible notification, like "Dear Mr. Joe, your blood > donation appointment was scheduled for 3 p.m", or simply "New appointment > scheduled". > > If the app was a chat system (and not a blood donation app from the Red > Cross), it would be the same: After a signal, the app connects to "chat > server" and receives the actual chat message from there. A reply would go > over the same "chat server" connection. None of this would go over a 3rd > party push network provider like Google, Microsoft or Apple. > > What would we store from these silent notifications? > > Nothing, since there is no alert, we would just store the metrics (e.g. > client that send the push, number of devices, deliveryStatus etc). If the > signaling is actually done with an alert (e.g. alert:"you got a new Chat > text" or "New appointment scheduled"), we would store that. > > I hope this helps a bit to understand what is stored and also why we do > need a little bit of information. > > BTW. our documentation already says that push is used for signaling, not > carrying actual data around, but based on this email I will update it to > have explicit information on best practices. Also, the documentation will > be clear about what (the alert only) is stored by the UPS, and why. (see > [4]) > > Greetings, > > Matthias > > - [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > - [2] https://issues.jboss.org/browse/AGPUSH-971 > - [3] JIRA TO CREATE: to only store ALERT and not the full payload > - [4] JIRA TO CREATE: update doc regarding push message storage and > best practices > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/b440fe37/attachment-0001.html From agalante at redhat.com Wed Feb 4 09:24:11 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 4 Feb 2015 09:24:11 -0500 (EST) Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: <20150204134857.GA36431@abstractj.org> References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> <20150204134857.GA36431@abstractj.org> Message-ID: <1744266824.4198530.1423059851357.JavaMail.zimbra@redhat.com> Thanks Bruno, I'll fix it. ----- Original Message ----- From: "Bruno Oliveira" To: "AeroGear Developer Mailing List" Sent: Wednesday, February 4, 2015 10:48:57 AM Subject: Re: [aerogear-dev] Shoot backend broken layout Hi my friend, not sure if it's helpful, but I deployed the latest changes on OpenShift: https://shoot-aerogear.rhcloud.com/shoot/photos/ username: user password: password On 2015-02-03, Andres Galante wrote: > I suspect it has something to do with either the "<3" here: > > https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html#L70 > > Try escaping it as <. > > OR the negative margin here: > > https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/css/style.css#L49 > > Is there any way I can preview this? Should I install it? > > Thanks > > ----- Original Message ----- > From: "Sebastien Blanc" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, February 3, 2015 4:41:56 PM > Subject: Re: [aerogear-dev] Shoot backend broken layout > > If I'm correct it's here https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html > > On Tue, Feb 3, 2015 at 8:38 PM, Andres Galante < agalante at redhat.com > wrote: > > > there must be an unclosed html tag or unclear floats. Can I see the source code? > > ----- Original Message ----- > From: "Bruno Oliveira" < bruno at abstractj.org > > To: "AeroGear Dev" < aerogear-dev at lists.jboss.org > > Sent: Tuesday, February 3, 2015 4:29:01 PM > Subject: [aerogear-dev] Shoot backend broken layout > > Good morning, we would like to announce the deliverables for OAuth2 this > week, although the backend layout seems broken > http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg . > > This is not a deal breaker, but I would love some 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 From supittma at redhat.com Wed Feb 4 09:56:51 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 04 Feb 2015 09:56:51 -0500 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: References: Message-ID: <54D23333.3010804@redhat.com> On 02/03/2015 04:13 PM, Matthias Wessendorf wrote: > Hi, > > I recently noticed that we are (IMO) incorrectly returning 200 (OK): > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 > > Since we really do submit an async job here, and its processing may > not have been started when we do return the 200 (OK), I'd like to > propose a slight change here to instead use 202 (Accepted): > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 > > If the team is OK (ha ha) with this, I will track this in JIRA This should be OK, I will need to review the Android code. Is there any downside to accepting results on the client side? (As opposed to configuring the library comply with a certain version of UPS) > > -Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/8b636f79/attachment.html From matzew at apache.org Wed Feb 4 10:04:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 4 Feb 2015 16:04:18 +0100 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: <54D23333.3010804@redhat.com> References: <54D23333.3010804@redhat.com> Message-ID: On Wed, Feb 4, 2015 at 3:56 PM, Summers Pittman wrote: > On 02/03/2015 04:13 PM, Matthias Wessendorf wrote: > > Hi, > > I recently noticed that we are (IMO) incorrectly returning 200 (OK): > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 > > Since we really do submit an async job here, and its processing may not > have been started when we do return the 200 (OK), I'd like to propose a > slight change here to instead use 202 (Accepted): > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 > > If the team is OK (ha ha) with this, I will track this in JIRA > > This should be OK, I will need to review the Android code. > I hope no Android code is actually using the SENDER api :-) > > Is there any downside to accepting results on the client side? (As opposed > to configuring the library comply with a certain version of UPS) > Not sure what you are asking here > > > -Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/ae6169c6/attachment.html From agalante at redhat.com Wed Feb 4 10:11:25 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 4 Feb 2015 10:11:25 -0500 (EST) Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: <1744266824.4198530.1423059851357.JavaMail.zimbra@redhat.com> References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> <20150204134857.GA36431@abstractj.org> <1744266824.4198530.1423059851357.JavaMail.zimbra@redhat.com> Message-ID: <208803115.4214954.1423062685677.JavaMail.zimbra@redhat.com> This is the solution: https://github.com/andresgalante/aerogear-backend-cookbook/tree/webapp-html-issues Should I make a pull request to master? ----- Original Message ----- From: "Andres Galante" To: "AeroGear Developer Mailing List" Sent: Wednesday, February 4, 2015 11:24:11 AM Subject: Re: [aerogear-dev] Shoot backend broken layout Thanks Bruno, I'll fix it. ----- Original Message ----- From: "Bruno Oliveira" To: "AeroGear Developer Mailing List" Sent: Wednesday, February 4, 2015 10:48:57 AM Subject: Re: [aerogear-dev] Shoot backend broken layout Hi my friend, not sure if it's helpful, but I deployed the latest changes on OpenShift: https://shoot-aerogear.rhcloud.com/shoot/photos/ username: user password: password On 2015-02-03, Andres Galante wrote: > I suspect it has something to do with either the "<3" here: > > https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html#L70 > > Try escaping it as <. > > OR the negative margin here: > > https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/css/style.css#L49 > > Is there any way I can preview this? Should I install it? > > Thanks > > ----- Original Message ----- > From: "Sebastien Blanc" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, February 3, 2015 4:41:56 PM > Subject: Re: [aerogear-dev] Shoot backend broken layout > > If I'm correct it's here https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/src/main/webapp/photos/index.html > > On Tue, Feb 3, 2015 at 8:38 PM, Andres Galante < agalante at redhat.com > wrote: > > > there must be an unclosed html tag or unclear floats. Can I see the source code? > > ----- Original Message ----- > From: "Bruno Oliveira" < bruno at abstractj.org > > To: "AeroGear Dev" < aerogear-dev at lists.jboss.org > > Sent: Tuesday, February 3, 2015 4:29:01 PM > Subject: [aerogear-dev] Shoot backend broken layout > > Good morning, we would like to announce the deliverables for OAuth2 this > week, although the backend layout seems broken > http://photon.abstractj.org/Shoot_Snapshot_2015-02-03_17-27-05.jpg . > > This is not a deal breaker, but I would love some 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From supittma at redhat.com Wed Feb 4 10:12:52 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 04 Feb 2015 10:12:52 -0500 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: References: <54D23333.3010804@redhat.com> Message-ID: <54D236F4.8090701@redhat.com> On 02/04/2015 10:04 AM, Matthias Wessendorf wrote: > > > On Wed, Feb 4, 2015 at 3:56 PM, Summers Pittman > wrote: > > On 02/03/2015 04:13 PM, Matthias Wessendorf wrote: >> Hi, >> >> I recently noticed that we are (IMO) incorrectly returning 200 (OK): >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 >> >> Since we really do submit an async job here, and its processing >> may not have been started when we do return the 200 (OK), I'd >> like to propose a slight change here to instead use 202 (Accepted): >> >> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 >> >> If the team is OK (ha ha) with this, I will track this in JIRA > This should be OK, I will need to review the Android code. > > > I hope no Android code is actually using the SENDER api :-) Sorry pre coffee reading comprehension. I thought you were talking about for registration flavored things for some reason. > > > Is there any downside to accepting results on the client side? (As > opposed to configuring the library comply with a certain version > of UPS) > > > Not sure what you are asking here > > >> >> -Matthias >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150204/fafd2ce3/attachment-0001.html From daniel at passos.me Wed Feb 4 11:00:46 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 4 Feb 2015 14:00:46 -0200 Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: <208803115.4214954.1423062685677.JavaMail.zimbra@redhat.com> References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> <20150204134857.GA36431@abstractj.org> <1744266824.4198530.1423059851357.JavaMail.zimbra@redhat.com> <208803115.4214954.1423062685677.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Feb 4, 2015 at 1:11 PM, Andres Galante wrote: > This is the solution: > > https://github.com/andresgalante/aerogear-backend-cookbook/tree/webapp-html-issues > > Should I make a pull request to master? > > Yes -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/cfe9a0ee/attachment.html From agalante at redhat.com Wed Feb 4 11:08:33 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 4 Feb 2015 11:08:33 -0500 (EST) Subject: [aerogear-dev] Shoot backend broken layout In-Reply-To: References: <20150203192901.GA31862@abstractj.org> <133439864.4025393.1422992333236.JavaMail.zimbra@redhat.com> <980712353.4030337.1422993647861.JavaMail.zimbra@redhat.com> <20150204134857.GA36431@abstractj.org> <1744266824.4198530.1423059851357.JavaMail.zimbra@redhat.com> <208803115.4214954.1423062685677.JavaMail.zimbra@redhat.com> Message-ID: <1190734757.4237282.1423066113857.JavaMail.zimbra@redhat.com> There you go: https://github.com/aerogear/aerogear-backend-cookbook/pull/13 ----- Original Message ----- From: "Daniel Passos" To: "AeroGear Developer Mailing List" Sent: Wednesday, February 4, 2015 1:00:46 PM Subject: Re: [aerogear-dev] Shoot backend broken layout On Wed, Feb 4, 2015 at 1:11 PM, Andres Galante < agalante at redhat.com > wrote: This is the solution: https://github.com/andresgalante/aerogear-backend-cookbook/tree/webapp-html-issues Should I make a pull request to master? Yes -- Passos _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From lukas.fryc at gmail.com Wed Feb 4 13:09:21 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 4 Feb 2015 19:09:21 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Sure, go ahead! Thanks passos :-) On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos wrote: > Luk??, > > Let me do it on Android land. > > -- Passos > > On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? wrote: > >> Great, I will proceed to the actual updates... >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150204/84355b0b/attachment.html From lukas.fryc at gmail.com Wed Feb 4 13:09:47 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 4 Feb 2015 19:09:47 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Here is a small list of repos that needs updates: https://gist.github.com/lfryc/60199eaa989811f076f9 I'm tracking there a progress. ~ Lukas On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? wrote: > Sure, go ahead! Thanks passos :-) > > On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos wrote: > >> Luk??, >> >> Let me do it on Android land. >> >> -- Passos >> >> On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? wrote: >> >>> Great, I will proceed to the actual updates... >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20150204/53dcba2f/attachment.html From daniel at passos.me Wed Feb 4 14:54:54 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 4 Feb 2015 17:54:54 -0200 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: I've sent a PR for all our Android repos. https://github.com/aerogear/aerogear-android-core/pull/18 https://github.com/aerogear/aerogear-android-security/pull/25 https://github.com/aerogear/aerogear-android-store/pull/27 https://github.com/aerogear/aerogear-android-pipe/pull/31 https://github.com/aerogear/aerogear-android-auth/pull/27 https://github.com/aerogear/aerogear-android-authz/pull/27/files https://github.com/aerogear/aerogear-android-push/pull/29 https://github.com/aerogear/aerogear-android-cookbook/pull/44 https://github.com/aerogear/aerogear-android/pull/159 https://github.com/aerogear/aerogear-android-integration-tests/pull/30 -- Passos On Wed, Feb 4, 2015 at 4:09 PM, Luk?? Fry? wrote: > Here is a small list of repos that needs updates: > https://gist.github.com/lfryc/60199eaa989811f076f9 > > I'm tracking there a progress. > > ~ Lukas > > On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? wrote: > >> Sure, go ahead! Thanks passos :-) >> >> On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos wrote: >> >>> Luk??, >>> >>> Let me do it on Android land. >>> >>> -- Passos >>> >>> On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? wrote: >>> >>>> Great, I will proceed to the actual updates... >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20150204/5388896a/attachment.html From matzew at apache.org Wed Feb 4 16:19:58 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 4 Feb 2015 22:19:58 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Hey Lukas, thanks for all the work - for all the Push bits (I saw your PR), I will take care of it - no need that you send PRs against all of the repos. On Wed, Feb 4, 2015 at 8:54 PM, Daniel Passos wrote: > I've sent a PR for all our Android repos. > > https://github.com/aerogear/aerogear-android-core/pull/18 > https://github.com/aerogear/aerogear-android-security/pull/25 > https://github.com/aerogear/aerogear-android-store/pull/27 > https://github.com/aerogear/aerogear-android-pipe/pull/31 > https://github.com/aerogear/aerogear-android-auth/pull/27 > https://github.com/aerogear/aerogear-android-authz/pull/27/files > https://github.com/aerogear/aerogear-android-push/pull/29 > https://github.com/aerogear/aerogear-android-cookbook/pull/44 > > https://github.com/aerogear/aerogear-android/pull/159 > https://github.com/aerogear/aerogear-android-integration-tests/pull/30 > > -- Passos > > On Wed, Feb 4, 2015 at 4:09 PM, Luk?? Fry? wrote: > >> Here is a small list of repos that needs updates: >> https://gist.github.com/lfryc/60199eaa989811f076f9 >> >> I'm tracking there a progress. >> >> ~ Lukas >> >> On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? wrote: >> >>> Sure, go ahead! Thanks passos :-) >>> >>> On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos wrote: >>> >>>> Luk??, >>>> >>>> Let me do it on Android land. >>>> >>>> -- Passos >>>> >>>> On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? >>>> wrote: >>>> >>>>> Great, I will proceed to the actual updates... >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150204/07fd49bf/attachment-0001.html From cvasilak at gmail.com Thu Feb 5 02:31:02 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 5 Feb 2015 09:31:02 +0200 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: <6C17A8A2-27C2-4465-9160-DB0B56BE2A30@gmail.com> Hey Lucas, thanks for doing it, saw your PR in ios-http, let me propagate this change to our other iOS repos too. - Christos > On Feb 4, 2015, at 8:09 PM, Luk?? Fry? wrote: > > Here is a small list of repos that needs updates: > https://gist.github.com/lfryc/60199eaa989811f076f9 > > I'm tracking there a progress. > > ~ Lukas > > On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? > wrote: > Sure, go ahead! Thanks passos :-) > > On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos > wrote: > Luk??, > > Let me do it on Android land. > > -- Passos > > On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? > wrote: > Great, I will proceed to the actual updates... > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150205/0d0761bb/attachment.html From lukas.fryc at gmail.com Thu Feb 5 04:44:02 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 5 Feb 2015 10:44:02 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: <6C17A8A2-27C2-4465-9160-DB0B56BE2A30@gmail.com> References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> <6C17A8A2-27C2-4465-9160-DB0B56BE2A30@gmail.com> Message-ID: Thanks guys, I will keep tracking progress of changes in this gist: https://gist.github.com/lfryc/60199eaa989811f076f9 On Thu, Feb 5, 2015 at 8:31 AM, Christos Vasilakis wrote: > Hey Lucas, > > thanks for doing it, saw your PR in ios-http, let me propagate this change > to our other iOS repos too. > > > - > Christos > > On Feb 4, 2015, at 8:09 PM, Luk?? Fry? wrote: > > Here is a small list of repos that needs updates: > https://gist.github.com/lfryc/60199eaa989811f076f9 > > I'm tracking there a progress. > > ~ Lukas > > On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? wrote: > >> Sure, go ahead! Thanks passos :-) >> >> On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos wrote: >> >>> Luk??, >>> >>> Let me do it on Android land. >>> >>> -- Passos >>> >>> On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? wrote: >>> >>>> Great, I will proceed to the actual updates... >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150205/9cb9aaa5/attachment.html From matzew at apache.org Thu Feb 5 06:24:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 12:24:19 +0100 Subject: [aerogear-dev] USP 1.1.0 - API change: Status code change for Sender Endpoint In-Reply-To: References: Message-ID: here we go: https://issues.jboss.org/browse/AGPUSH-1265 -M On Tue, Feb 3, 2015 at 10:13 PM, Matthias Wessendorf wrote: > Hi, > > I recently noticed that we are (IMO) incorrectly returning 200 (OK): > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L112-L113 > > Since we really do submit an async job here, and its processing may not > have been started when we do return the 200 (OK), I'd like to propose a > slight change here to instead use 202 (Accepted): > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 > > If the team is OK (ha ha) with this, I will track this in JIRA > > -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/20150205/bce12827/attachment.html From matzew at apache.org Thu Feb 5 06:53:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 12:53:51 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Here are my PRs agains some push related repos: https://github.com/aerogear/aerogear-push-helloworld/pull/83 https://github.com/aerogear/aerogear-push-quickstarts/pull/124 https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/65 https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/14 https://github.com/aerogear/aerogear-unifiedpush-dotnet-client/pull/1 https://github.com/tmccarthy9/aerogear-unified-push-php-client/pull/4 https://github.com/aerogear/aerogear-simplepush-java-client/pull/6 https://github.com/aerogear/aerogear-simplepush-node-client/pull/1 https://github.com/aerogear/aerogear-simplepush-server/pull/89 https://github.com/aerogear/aerogear-webpush-server/pull/2/files https://github.com/aerogear/java-adm/pull/2 https://github.com/aerogear/java-mpns/pull/5 On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? wrote: > Here is a small list of repos that needs updates: > https://gist.github.com/lfryc/60199eaa989811f076f9 > > I'm tracking there a progress. > > ~ Lukas > > On Wed, Feb 4, 2015 at 7:09 PM, Luk?? Fry? wrote: > >> Sure, go ahead! Thanks passos :-) >> >> On Tue, Feb 3, 2015 at 9:12 PM, Daniel Passos wrote: >> >>> Luk??, >>> >>> Let me do it on Android land. >>> >>> -- Passos >>> >>> On Tue, Feb 3, 2015 at 2:15 PM, Luk?? Fry? wrote: >>> >>>> Great, I will proceed to the actual updates... >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150205/69fc49b3/attachment-0001.html From corinnekrych at gmail.com Thu Feb 5 08:34:07 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 5 Feb 2015 14:34:07 +0100 Subject: [aerogear-dev] Data Sync meeting In-Reply-To: References: Message-ID: Hello Guys As promised in our last sync meeting, here is quick email to give you more information on iOS JsonPatch integration of aerogear-ios-sync and its usage in the Jedi demo app. Integration has started, some unit tests passed (Yay!!) [1]. But we hit some cocoapod issue with diffmatchpatch (obj-c library for google diffmatchpatch) clashing with JSONTools (obj-c implementation of JsonPatch protocol), the idea is to use pod subspec to use either one or the other, Christos is investigating the issue [2] and looking at sync-client and demo integration. With some tweaks and tricks, we?re more confident to get a demo out for alpha1. But we?ll keep you posted on how it goes. ++ Corinne and Christos [1] https://github.com/corinnekrych/aerogear-ios-sync/blob/json.synchronizer/AeroGearSyncTests/JsonPatchSynchronizerTests.swift [2] https://issues.jboss.org/browse/AGIOS-376 > On 02 Feb 2015, at 15:53, Matthias Wessendorf wrote: > > Hi, > > we had a little google hangout for our work on SYNC. Here are the meeting minutes: > http://oksoclap.com/p/sync_meeting_2ndFebruary_2015 > > -Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Thu Feb 5 10:48:36 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 16:48:36 +0100 Subject: [aerogear-dev] Data Sync meeting In-Reply-To: References: Message-ID: On Thu, Feb 5, 2015 at 2:34 PM, Corinne Krych wrote: > Hello Guys > > As promised in our last sync meeting, here is quick email to give you more > information on iOS JsonPatch integration of aerogear-ios-sync and its usage > in the Jedi demo app. > > Integration has started, some unit tests passed (Yay!!) [1]. But we hit > some cocoapod issue with diffmatchpatch (obj-c library for google > diffmatchpatch) clashing with JSONTools (obj-c implementation of JsonPatch > protocol), the idea is to use pod subspec to use either one or the other, > Christos is investigating the issue [2] and looking at sync-client and demo > integration. > > With some tweaks and tricks, we?re more confident to get a demo out for > alpha1. But we?ll keep you posted on how it goes. > sounds good! thanks for the heads-up > > ++ > Corinne and Christos > > [1] > https://github.com/corinnekrych/aerogear-ios-sync/blob/json.synchronizer/AeroGearSyncTests/JsonPatchSynchronizerTests.swift > [2] https://issues.jboss.org/browse/AGIOS-376 > > > On 02 Feb 2015, at 15:53, Matthias Wessendorf wrote: > > > > Hi, > > > > we had a little google hangout for our work on SYNC. Here are the > meeting minutes: > > http://oksoclap.com/p/sync_meeting_2ndFebruary_2015 > > > > -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/20150205/36428885/attachment.html From matzew at apache.org Thu Feb 5 14:24:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 20:24:54 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: Message-ID: While working on the doc for AGPUSH-1258, I found this in Apple's "iOS Developer Program License Agreement": ... Further, as a condition to using the APN, You agree not to transmit sensitive personal or confidential information belonging to an individual (e.g. a social security number, financial account or transactional information, or any information where the individual may have a reasonable expectation of secure transmission) as part of any Push Notification, and You agree to comply with any applicable notice or consent requirements with respect to any collection, transmission, maintenance, processing or use of an end user?s personal information. ... That means, if an app-developer sends something like "Your blood donation appointment is tomorrow" to a user of his mobile app, the app-developer is breaking the Apple terms _and_ the law in a lot of countries (at least in all EU countries) :-) BTW. for Google I don't seem to find a similar paragraph, but IMO they are not that thoughtful on privacy terms (compared to Apple). Now, for our UPS guide (or documentation), I will add a few sentences to make it clear that our app-developers should NEVER submit sensitive personal or confidential information with a push. Regarding a "Privacy Policy", I will also make clear what data of the push we store, for analytic reasons. You'll see a PR during my Friday. Greetings, Matthias On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf wrote: > I have created AGPUSH-1257 and AGPUSH-1258 > > On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> earlier this week there was some discussion about storing the payload of >> the push notifications ([1]). >> >> Right now, we store some metrics (e.g. client that send the push, number >> of devices, deliveryStatus etc) *and* the entire content of push >> notification. This includes custom key/value pairs, the name of the sound >> file or even the size of the badge. >> >> Is all of that, storing the entire push notification payload really >> needed? *No!* >> >> What do we need, and why? >> >> For counting the number of sent pushes (over time), the metrics are good >> enough. We do *NOT* need any of the push content for that, that's >> correct! >> >> But we want to do more on the 1.1.0 release. We want to introduce some >> analytic features, to give our app developers (our users) a better >> understanding of their push usage (see [2]). >> >> In order to see details on how successful a push was (or not), we need to >> only store the value of the alert key: >> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png >> >> Ok, let's change that (see [3])! >> >> For our app developers, using the UPS to reach out to their mobile app >> users ("user engagement"), it's important to understand which push was more >> successful: >> >> - "Get 10% discount today" (sent on a Monday) >> - "Our shop got new site, check it out and get 5% discount" (sent on >> a Friday) >> >> With the upcoming analytics we can help them to improve usage of their >> app. User interaction is very important to a successful mobile application >> and push is a key driver here! Our app developers want an app that is >> actively used by their users (Nobody wants his app sitting on the last page >> of the device or, even worse, in a folder together with Apple-Maps). >> Therefore it's critical for our app developers to understand the relevance >> of their push messages sent and how it impacts the usage of their app. >> That's why we do the analytics described in [2]. And, yes - only the alert, >> not the entire payload is needed for that. >> Privacy >> >> On the mentioned PR there was also some discussion about privacy >> violations and stuff, when we store the content of the notification. An >> example where *sensitive* data was sent over push was given. Something >> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 >> p.m" >> >> 1. This is not how push notifications are used for mobile apps. Push >> is to signal, not carry actual (sensitive) data around. >> 2. In a lot of countries, at least almost all European countries, you >> are not even allowed, by EU law, to give "data" to 3rd party providers >> (like the push-networks of Microsoft, Apple or Google). >> >> How does the actual (sensitive) data come to an app? >> >> As said above a push is used to signal/ping an app, to indicate that >> there is real data for the mobile app user. In the background the mobile >> app tries to connect to the backend of the company, running/maintaining the >> mobile app. After the real data was fetched, "local notifcations" are used >> to give the user a visible notification, like "Dear Mr. Joe, your blood >> donation appointment was scheduled for 3 p.m", or simply "New appointment >> scheduled". >> >> If the app was a chat system (and not a blood donation app from the Red >> Cross), it would be the same: After a signal, the app connects to "chat >> server" and receives the actual chat message from there. A reply would go >> over the same "chat server" connection. None of this would go over a 3rd >> party push network provider like Google, Microsoft or Apple. >> >> What would we store from these silent notifications? >> >> Nothing, since there is no alert, we would just store the metrics (e.g. >> client that send the push, number of devices, deliveryStatus etc). If the >> signaling is actually done with an alert (e.g. alert:"you got a new Chat >> text" or "New appointment scheduled"), we would store that. >> >> I hope this helps a bit to understand what is stored and also why we do >> need a little bit of information. >> >> BTW. our documentation already says that push is used for signaling, not >> carrying actual data around, but based on this email I will update it to >> have explicit information on best practices. Also, the documentation will >> be clear about what (the alert only) is stored by the UPS, and why. (see >> [4]) >> >> Greetings, >> >> Matthias >> >> - [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 >> - [2] https://issues.jboss.org/browse/AGPUSH-971 >> - [3] JIRA TO CREATE: to only store ALERT and not the full payload >> - [4] JIRA TO CREATE: update doc regarding push message storage and >> best practices >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > 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/20150205/ab456a1b/attachment-0001.html From scm.blanc at gmail.com Thu Feb 5 14:44:59 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 5 Feb 2015 20:44:59 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: Message-ID: On Thu, Feb 5, 2015 at 8:24 PM, Matthias Wessendorf wrote: > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > Developer Program License Agreement": > > ... > Further, as a condition to using the APN, You agree not to transmit > sensitive personal or confidential information belonging to an individual > (e.g. a social security number, financial account or transactional > information, or any information where the individual may have a reasonable > expectation of secure transmission) as part of any Push Notification, and > You agree to comply with any applicable notice or consent requirements with > respect to any collection, transmission, maintenance, processing or use of > an end user?s personal information. > ... > > That means, if an app-developer sends something like "Your blood donation > appointment is tomorrow" to a user of his mobile app, the app-developer is > breaking the Apple terms _and_ the law in a lot of countries (at least in > all EU countries) :-) > > BTW. for Google I don't seem to find a similar paragraph, but IMO they are > not that thoughtful on privacy terms (compared to Apple). > Yeah but as you said just above, privacy will be protected by EU Laws and in many cases by national laws, like in France with have the CNIL ( http://www.cnil.fr/english/) which is very powerful on this area (Google has even lost a trial against them :) ) > > > Now, for our UPS guide (or documentation), I will add a few sentences to > make it clear that our app-developers should NEVER submit sensitive > personal or confidential information with a push. > > Regarding a "Privacy Policy", I will also make clear what data of the push > we store, for analytic reasons. > good point > > You'll see a PR during my Friday. > > > Greetings, > Matthias > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > wrote: > >> I have created AGPUSH-1257 and AGPUSH-1258 >> >> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> earlier this week there was some discussion about storing the payload of >>> the push notifications ([1]). >>> >>> Right now, we store some metrics (e.g. client that send the push, number >>> of devices, deliveryStatus etc) *and* the entire content of push >>> notification. This includes custom key/value pairs, the name of the sound >>> file or even the size of the badge. >>> >>> Is all of that, storing the entire push notification payload really >>> needed? *No!* >>> >>> What do we need, and why? >>> >>> For counting the number of sent pushes (over time), the metrics are good >>> enough. We do *NOT* need any of the push content for that, that's >>> correct! >>> >>> But we want to do more on the 1.1.0 release. We want to introduce some >>> analytic features, to give our app developers (our users) a better >>> understanding of their push usage (see [2]). >>> >>> In order to see details on how successful a push was (or not), we need >>> to only store the value of the alert key: >>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png >>> >>> Ok, let's change that (see [3])! >>> >>> For our app developers, using the UPS to reach out to their mobile app >>> users ("user engagement"), it's important to understand which push was more >>> successful: >>> >>> - "Get 10% discount today" (sent on a Monday) >>> - "Our shop got new site, check it out and get 5% discount" (sent on >>> a Friday) >>> >>> With the upcoming analytics we can help them to improve usage of their >>> app. User interaction is very important to a successful mobile application >>> and push is a key driver here! Our app developers want an app that is >>> actively used by their users (Nobody wants his app sitting on the last page >>> of the device or, even worse, in a folder together with Apple-Maps). >>> Therefore it's critical for our app developers to understand the relevance >>> of their push messages sent and how it impacts the usage of their app. >>> That's why we do the analytics described in [2]. And, yes - only the alert, >>> not the entire payload is needed for that. >>> Privacy >>> >>> On the mentioned PR there was also some discussion about privacy >>> violations and stuff, when we store the content of the notification. An >>> example where *sensitive* data was sent over push was given. Something >>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 >>> p.m" >>> >>> 1. This is not how push notifications are used for mobile apps. Push >>> is to signal, not carry actual (sensitive) data around. >>> 2. In a lot of countries, at least almost all European countries, >>> you are not even allowed, by EU law, to give "data" to 3rd party providers >>> (like the push-networks of Microsoft, Apple or Google). >>> >>> How does the actual (sensitive) data come to an app? >>> >>> As said above a push is used to signal/ping an app, to indicate that >>> there is real data for the mobile app user. In the background the mobile >>> app tries to connect to the backend of the company, running/maintaining the >>> mobile app. After the real data was fetched, "local notifcations" are used >>> to give the user a visible notification, like "Dear Mr. Joe, your blood >>> donation appointment was scheduled for 3 p.m", or simply "New appointment >>> scheduled". >>> >>> If the app was a chat system (and not a blood donation app from the Red >>> Cross), it would be the same: After a signal, the app connects to "chat >>> server" and receives the actual chat message from there. A reply would go >>> over the same "chat server" connection. None of this would go over a 3rd >>> party push network provider like Google, Microsoft or Apple. >>> >>> What would we store from these silent notifications? >>> >>> Nothing, since there is no alert, we would just store the metrics (e.g. >>> client that send the push, number of devices, deliveryStatus etc). If the >>> signaling is actually done with an alert (e.g. alert:"you got a new Chat >>> text" or "New appointment scheduled"), we would store that. >>> >>> I hope this helps a bit to understand what is stored and also why we do >>> need a little bit of information. >>> >>> BTW. our documentation already says that push is used for signaling, not >>> carrying actual data around, but based on this email I will update it to >>> have explicit information on best practices. Also, the documentation will >>> be clear about what (the alert only) is stored by the UPS, and why. (see >>> [4]) >>> >>> Greetings, >>> >>> Matthias >>> >>> - [1] >>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 >>> - [2] https://issues.jboss.org/browse/AGPUSH-971 >>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload >>> - [4] JIRA TO CREATE: update doc regarding push message storage and >>> best practices >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> 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/20150205/e9422ac1/attachment.html From bruno at abstractj.org Thu Feb 5 15:24:50 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 5 Feb 2015 18:24:50 -0200 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: Message-ID: <20150205202450.GA58032@abstractj.org> On 2015-01-30, Matthias Wessendorf wrote: > Hi, > > earlier this week there was some discussion about storing the payload of > the push notifications ([1]). Hi Matthias, I think the usage of UPS and how it works is clear to everyone here. The focus of the discussion last week was pretty much about storing the content of the message. > > Right now, we store some metrics (e.g. client that send the push, number of > devices, deliveryStatus etc) *and* the entire content of push notification. > This includes custom key/value pairs, the name of the sound file or even > the size of the badge. > > Is all of that, storing the entire push notification payload really needed? > *No!* > > What do we need, and why? > > For counting the number of sent pushes (over time), the metrics are good > enough. We do *NOT* need any of the push content for that, that's correct! > > But we want to do more on the 1.1.0 release. We want to introduce some > analytic features, to give our app developers (our users) a better > understanding of their push usage (see [2]). You don't need the content of the message unless we're planning a recommendation system or crunching data for some good reason. But we already discussed about it. > > In order to see details on how successful a push was (or not), we need to > only store the value of the alert key: > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > > Ok, let's change that (see [3])! > > For our app developers, using the UPS to reach out to their mobile app > users ("user engagement"), it's important to understand which push was more > successful: > > - "Get 10% discount today" (sent on a Monday) > - "Our shop got new site, check it out and get 5% discount" (sent on a > Friday) > > With the upcoming analytics we can help them to improve usage of their app. > User interaction is very important to a successful mobile application and > push is a key driver here! Our app developers want an app that is actively > used by their users (Nobody wants his app sitting on the last page of the > device or, even worse, in a folder together with Apple-Maps). Therefore > it's critical for our app developers to understand the relevance of their > push messages sent and how it impacts the usage of their app. That's why we > do the analytics described in [2]. And, yes - only the alert, not the > entire payload is needed for that. Yes, only the alert, not the entire payload. > Privacy > > On the mentioned PR there was also some discussion about privacy violations > and stuff, when we store the content of the notification. An example where > *sensitive* data was sent over push was given. Something like: "Dear Mr. > Joe, your blood donation appointment was scheduled for 3 p.m" > > 1. This is not how push notifications are used for mobile apps. Push is > to signal, not carry actual (sensitive) data around. > 2. In a lot of countries, at least almost all European countries, you > are not even allowed, by EU law, to give "data" to 3rd party providers > (like the push-networks of Microsoft, Apple or Google). Yes my friend, a knife for me is to cut tomatoes, for other people outside is to hurt. What you gonna do with data pretty much depends. > > How does the actual (sensitive) data come to an app? > > As said above a push is used to signal/ping an app, to indicate that there > is real data for the mobile app user. In the background the mobile app > tries to connect to the backend of the company, running/maintaining the > mobile app. After the real data was fetched, "local notifcations" are used > to give the user a visible notification, like "Dear Mr. Joe, your blood > donation appointment was scheduled for 3 p.m", or simply "New appointment > scheduled". > > If the app was a chat system (and not a blood donation app from the Red > Cross), it would be the same: After a signal, the app connects to "chat > server" and receives the actual chat message from there. A reply would go > over the same "chat server" connection. None of this would go over a 3rd > party push network provider like Google, Microsoft or Apple. > > What would we store from these silent notifications? > > Nothing, since there is no alert, we would just store the metrics (e.g. > client that send the push, number of devices, deliveryStatus etc). If the > signaling is actually done with an alert (e.g. alert:"you got a new Chat > text" or "New appointment scheduled"), we would store that. > > I hope this helps a bit to understand what is stored and also why we do > need a little bit of information. Is not clear for me if you still need the content of the message and why. > > BTW. our documentation already says that push is used for signaling, not > carrying actual data around, but based on this email I will update it to > have explicit information on best practices. Also, the documentation will > be clear about what (the alert only) is stored by the UPS, and why. (see > [4]) If we provide a clear and solid policy explaining why we need such kind of data. I think is totally acceptable. > > Greetings, > > Matthias > > - [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > - [2] https://issues.jboss.org/browse/AGPUSH-971 > - [3] JIRA TO CREATE: to only store ALERT and not the full payload > - [4] JIRA TO CREATE: update doc regarding push message storage and best > practices > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > 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 Feb 5 15:29:42 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 5 Feb 2015 18:29:42 -0200 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: Message-ID: <20150205202942.GB58032@abstractj.org> If we provide a rock solid privacy policy like I already mentioned, we're good to go. On 2015-02-05, Matthias Wessendorf wrote: > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > Developer Program License Agreement": > > ... > Further, as a condition to using the APN, You agree not to transmit > sensitive personal or confidential information belonging to an individual > (e.g. a social security number, financial account or transactional > information, or any information where the individual may have a reasonable > expectation of secure transmission) as part of any Push Notification, and > You agree to comply with any applicable notice or consent requirements with > respect to any collection, transmission, maintenance, processing or use of > an end user?s personal information. > ... > > That means, if an app-developer sends something like "Your blood donation > appointment is tomorrow" to a user of his mobile app, the app-developer is > breaking the Apple terms _and_ the law in a lot of countries (at least in > all EU countries) :-) Which means that if Apples knows that you are violating the terms, they read our message :) Joy! > > BTW. for Google I don't seem to find a similar paragraph, but IMO they are > not that thoughtful on privacy terms (compared to Apple). > > > Now, for our UPS guide (or documentation), I will add a few sentences to > make it clear that our app-developers should NEVER submit sensitive > personal or confidential information with a push. > > Regarding a "Privacy Policy", I will also make clear what data of the push > we store, for analytic reasons. > > You'll see a PR during my Friday. > > > Greetings, > Matthias > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > wrote: > > > I have created AGPUSH-1257 and AGPUSH-1258 > > > > On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf > > wrote: > > > >> Hi, > >> > >> earlier this week there was some discussion about storing the payload of > >> the push notifications ([1]). > >> > >> Right now, we store some metrics (e.g. client that send the push, number > >> of devices, deliveryStatus etc) *and* the entire content of push > >> notification. This includes custom key/value pairs, the name of the sound > >> file or even the size of the badge. > >> > >> Is all of that, storing the entire push notification payload really > >> needed? *No!* > >> > >> What do we need, and why? > >> > >> For counting the number of sent pushes (over time), the metrics are good > >> enough. We do *NOT* need any of the push content for that, that's > >> correct! > >> > >> But we want to do more on the 1.1.0 release. We want to introduce some > >> analytic features, to give our app developers (our users) a better > >> understanding of their push usage (see [2]). > >> > >> In order to see details on how successful a push was (or not), we need to > >> only store the value of the alert key: > >> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > >> > >> Ok, let's change that (see [3])! > >> > >> For our app developers, using the UPS to reach out to their mobile app > >> users ("user engagement"), it's important to understand which push was more > >> successful: > >> > >> - "Get 10% discount today" (sent on a Monday) > >> - "Our shop got new site, check it out and get 5% discount" (sent on > >> a Friday) > >> > >> With the upcoming analytics we can help them to improve usage of their > >> app. User interaction is very important to a successful mobile application > >> and push is a key driver here! Our app developers want an app that is > >> actively used by their users (Nobody wants his app sitting on the last page > >> of the device or, even worse, in a folder together with Apple-Maps). > >> Therefore it's critical for our app developers to understand the relevance > >> of their push messages sent and how it impacts the usage of their app. > >> That's why we do the analytics described in [2]. And, yes - only the alert, > >> not the entire payload is needed for that. > >> Privacy > >> > >> On the mentioned PR there was also some discussion about privacy > >> violations and stuff, when we store the content of the notification. An > >> example where *sensitive* data was sent over push was given. Something > >> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 > >> p.m" > >> > >> 1. This is not how push notifications are used for mobile apps. Push > >> is to signal, not carry actual (sensitive) data around. > >> 2. In a lot of countries, at least almost all European countries, you > >> are not even allowed, by EU law, to give "data" to 3rd party providers > >> (like the push-networks of Microsoft, Apple or Google). > >> > >> How does the actual (sensitive) data come to an app? > >> > >> As said above a push is used to signal/ping an app, to indicate that > >> there is real data for the mobile app user. In the background the mobile > >> app tries to connect to the backend of the company, running/maintaining the > >> mobile app. After the real data was fetched, "local notifcations" are used > >> to give the user a visible notification, like "Dear Mr. Joe, your blood > >> donation appointment was scheduled for 3 p.m", or simply "New appointment > >> scheduled". > >> > >> If the app was a chat system (and not a blood donation app from the Red > >> Cross), it would be the same: After a signal, the app connects to "chat > >> server" and receives the actual chat message from there. A reply would go > >> over the same "chat server" connection. None of this would go over a 3rd > >> party push network provider like Google, Microsoft or Apple. > >> > >> What would we store from these silent notifications? > >> > >> Nothing, since there is no alert, we would just store the metrics (e.g. > >> client that send the push, number of devices, deliveryStatus etc). If the > >> signaling is actually done with an alert (e.g. alert:"you got a new Chat > >> text" or "New appointment scheduled"), we would store that. > >> > >> I hope this helps a bit to understand what is stored and also why we do > >> need a little bit of information. > >> > >> BTW. our documentation already says that push is used for signaling, not > >> carrying actual data around, but based on this email I will update it to > >> have explicit information on best practices. Also, the documentation will > >> be clear about what (the alert only) is stored by the UPS, and why. (see > >> [4]) > >> > >> Greetings, > >> > >> Matthias > >> > >> - [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > >> - [2] https://issues.jboss.org/browse/AGPUSH-971 > >> - [3] JIRA TO CREATE: to only store ALERT and not the full payload > >> - [4] JIRA TO CREATE: update doc regarding push message storage and > >> best practices > >> > >> > >> -- > >> Matthias Wessendorf > >> > >> blog: http://matthiaswessendorf.wordpress.com/ > >> sessions: http://www.slideshare.net/mwessendorf > >> twitter: http://twitter.com/mwessendorf > >> > > > > > > > > -- > > 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 supittma at redhat.com Thu Feb 5 15:57:02 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 05 Feb 2015 15:57:02 -0500 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: Message-ID: <54D3D91E.4000209@redhat.com> On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > Developer Program License Agreement": > > ... > Further, as a condition to using the APN, You agree not to transmit > sensitive personal or confidential information belonging to an > individual (e.g. a social security number, financial account or > transactional information, or any information where the individual may > have a reasonable expectation of secure transmission) as part of any > Push Notification, and You agree to comply with any applicable notice > or consent requirements with respect to any collection, transmission, > maintenance, processing or use of an end user?s personal information. > ... > > That means, if an app-developer sends something like "Your blood > donation appointment is tomorrow" to a user of his mobile app, the > app-developer is breaking the Apple terms _and_ the law in a lot of > countries (at least in all EU countries) :-) What we have to remember is that large amounts of information in aggregate can become personally identifying even if any individual message is not. So the law in this case doesn't help since it is only the data in context which becomes personally identifying or protected. I don't think anyone is advocating for sending sensitive information via push, but what we are advocating is not putting a big target on our (or our user's) backs out of the gate by storing all of the messages by default. > > BTW. for Google I don't seem to find a similar paragraph, but IMO they > are not that thoughtful on privacy terms (compared to Apple). > > > Now, for our UPS guide (or documentation), I will add a few sentences > to make it clear that our app-developers should NEVER submit sensitive > personal or confidential information with a push. > > Regarding a "Privacy Policy", I will also make clear what data of the > push we store, for analytic reasons. > > You'll see a PR during my Friday. > > > Greetings, > Matthias > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > wrote: > > I have created AGPUSH-1257 and AGPUSH-1258 > > On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf > > wrote: > > Hi, > > earlier this week there was some discussion about storing the > payload of the push notifications ([1]). > > Right now, we store some metrics (e.g. client that send the > push, number of devices, deliveryStatus etc) /and/ the entire > content of push notification. This includes custom key/value > pairs, the name of the sound file or even the size of the badge. > > Is all of that, storing the entire push notification payload > really needed? /No!/ > > What do we need, and why? > > For counting the number of sent pushes (over time), the > metrics are good enough. We do /NOT/ need any of the push > content for that, that's correct! > > But we want to do more on the 1.1.0 release. We want to > introduce some analytic features, to give our app developers > (our users) a better understanding of their push usage (see [2]). > > In order to see details on how successful a push was (or not), > we need to only store the value of the alert key: > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > > Ok, let's change that (see [3])! > > For our app developers, using the UPS to reach out to their > mobile app users ("user engagement"), it's important to > understand which push was more successful: > > * "Get 10% discount today" (sent on a Monday) > * "Our shop got new site, check it out and get 5% discount" > (sent on a Friday) > > With the upcoming analytics we can help them to improve usage > of their app. User interaction is very important to a > successful mobile application and push is a key driver here! > Our app developers want an app that is actively used by their > users (Nobody wants his app sitting on the last page of the > device or, even worse, in a folder together with Apple-Maps). > Therefore it's critical for our app developers to understand > the relevance of their push messages sent and how it impacts > the usage of their app. That's why we do the analytics > described in [2]. And, yes - only the alert, not the entire > payload is needed for that. > > > Privacy > > On the mentioned PR there was also some discussion about > privacy violations and stuff, when we store the content of the > notification. An example where /sensitive/ data was sent over > push was given. Something like: "Dear Mr. Joe, your blood > donation appointment was scheduled for 3 p.m" > > 1. This is not how push notifications are used for mobile > apps. Push is to signal, not carry actual (sensitive) data > around. > 2. In a lot of countries, at least almost all European > countries, you are not even allowed, by EU law, to give > "data" to 3rd party providers (like the push-networks of > Microsoft, Apple or Google). > > How does the actual (sensitive) data come to an app? > > As said above a push is used to signal/ping an app, to > indicate that there is real data for the mobile app user. In > the background the mobile app tries to connect to the backend > of the company, running/maintaining the mobile app. After the > real data was fetched, "local notifcations" are used to give > the user a visible notification, like "Dear Mr. Joe, your > blood donation appointment was scheduled for 3 p.m", or simply > "New appointment scheduled". > > If the app was a chat system (and not a blood donation app > from the Red Cross), it would be the same: After a signal, the > app connects to "chat server" and receives the actual chat > message from there. A reply would go over the same "chat > server" connection. None of this would go over a 3rd party > push network provider like Google, Microsoft or Apple. > > What would we store from these silent notifications? > > Nothing, since there is no alert, we would just store the > metrics (e.g. client that send the push, number of devices, > deliveryStatus etc). If the signaling is actually done with an > alert (e.g. alert:"you got a new Chat text" or "New > appointment scheduled"), we would store that. > > I hope this helps a bit to understand what is stored and also > why we do need a little bit of information. > > BTW. our documentation already says that push is used for > signaling, not carrying actual data around, but based on this > email I will update it to have explicit information on best > practices. Also, the documentation will be clear about what > (the alert only) is stored by the UPS, and why. (see [4]) > > Greetings, > > Matthias > > * [1] > https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > * [2] https://issues.jboss.org/browse/AGPUSH-971 > * [3] JIRA TO CREATE: to only store ALERT and not the full > payload > * [4] JIRA TO CREATE: update doc regarding push message > storage and best practices > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > > > -- > 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 -- 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/20150205/4be4fd35/attachment-0001.html From scm.blanc at gmail.com Thu Feb 5 16:51:59 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 5 Feb 2015 22:51:59 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: <54D3D91E.4000209@redhat.com> References: <54D3D91E.4000209@redhat.com> Message-ID: On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman wrote: > On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > Developer Program License Agreement": > > ... > Further, as a condition to using the APN, You agree not to transmit > sensitive personal or confidential information belonging to an individual > (e.g. a social security number, financial account or transactional > information, or any information where the individual may have a reasonable > expectation of secure transmission) as part of any Push Notification, and > You agree to comply with any applicable notice or consent requirements with > respect to any collection, transmission, maintenance, processing or use of > an end user?s personal information. > ... > > That means, if an app-developer sends something like "Your blood > donation appointment is tomorrow" to a user of his mobile app, the > app-developer is breaking the Apple terms _and_ the law in a lot of > countries (at least in all EU countries) :-) > > What we have to remember is that large amounts of information in aggregate > can become personally identifying even if any individual message is not. > So the law in this case doesn't help since it is only the data in context > which becomes personally identifying or protected. > Good point. > > I don't think anyone is advocating for sending sensitive information via > push, but what we are advocating is not putting a big target on our (or our > user's) backs out of the gate by storing all of the messages by default. > Only the alert is stored (PR has been merged) . But, and this is just an idea that just popped out, couldn't we encrypt the value of the alert that is stored? It could be by default or a config thingy ... > > > BTW. for Google I don't seem to find a similar paragraph, but IMO they > are not that thoughtful on privacy terms (compared to Apple). > > > Now, for our UPS guide (or documentation), I will add a few sentences to > make it clear that our app-developers should NEVER submit sensitive > personal or confidential information with a push. > > Regarding a "Privacy Policy", I will also make clear what data of the > push we store, for analytic reasons. > > You'll see a PR during my Friday. > > > > > Greetings, > Matthias > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > wrote: > >> I have created AGPUSH-1257 and AGPUSH-1258 >> >> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> earlier this week there was some discussion about storing the payload of >>> the push notifications ([1]). >>> >>> Right now, we store some metrics (e.g. client that send the push, number >>> of devices, deliveryStatus etc) *and* the entire content of push >>> notification. This includes custom key/value pairs, the name of the sound >>> file or even the size of the badge. >>> >>> Is all of that, storing the entire push notification payload really >>> needed? *No!* >>> >>> What do we need, and why? >>> >>> For counting the number of sent pushes (over time), the metrics are good >>> enough. We do *NOT* need any of the push content for that, that's >>> correct! >>> >>> But we want to do more on the 1.1.0 release. We want to introduce some >>> analytic features, to give our app developers (our users) a better >>> understanding of their push usage (see [2]). >>> >>> In order to see details on how successful a push was (or not), we need >>> to only store the value of the alert key: >>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png >>> >>> Ok, let's change that (see [3])! >>> >>> For our app developers, using the UPS to reach out to their mobile app >>> users ("user engagement"), it's important to understand which push was more >>> successful: >>> >>> - "Get 10% discount today" (sent on a Monday) >>> - "Our shop got new site, check it out and get 5% discount" (sent on >>> a Friday) >>> >>> With the upcoming analytics we can help them to improve usage of their >>> app. User interaction is very important to a successful mobile application >>> and push is a key driver here! Our app developers want an app that is >>> actively used by their users (Nobody wants his app sitting on the last page >>> of the device or, even worse, in a folder together with Apple-Maps). >>> Therefore it's critical for our app developers to understand the relevance >>> of their push messages sent and how it impacts the usage of their app. >>> That's why we do the analytics described in [2]. And, yes - only the alert, >>> not the entire payload is needed for that. >>> Privacy >>> >>> On the mentioned PR there was also some discussion about privacy >>> violations and stuff, when we store the content of the notification. An >>> example where *sensitive* data was sent over push was given. Something >>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 >>> p.m" >>> >>> 1. This is not how push notifications are used for mobile apps. Push >>> is to signal, not carry actual (sensitive) data around. >>> 2. In a lot of countries, at least almost all European countries, >>> you are not even allowed, by EU law, to give "data" to 3rd party providers >>> (like the push-networks of Microsoft, Apple or Google). >>> >>> How does the actual (sensitive) data come to an app? >>> >>> As said above a push is used to signal/ping an app, to indicate that >>> there is real data for the mobile app user. In the background the mobile >>> app tries to connect to the backend of the company, running/maintaining the >>> mobile app. After the real data was fetched, "local notifcations" are used >>> to give the user a visible notification, like "Dear Mr. Joe, your blood >>> donation appointment was scheduled for 3 p.m", or simply "New appointment >>> scheduled". >>> >>> If the app was a chat system (and not a blood donation app from the Red >>> Cross), it would be the same: After a signal, the app connects to "chat >>> server" and receives the actual chat message from there. A reply would go >>> over the same "chat server" connection. None of this would go over a 3rd >>> party push network provider like Google, Microsoft or Apple. >>> >>> What would we store from these silent notifications? >>> >>> Nothing, since there is no alert, we would just store the metrics (e.g. >>> client that send the push, number of devices, deliveryStatus etc). If the >>> signaling is actually done with an alert (e.g. alert:"you got a new Chat >>> text" or "New appointment scheduled"), we would store that. >>> >>> I hope this helps a bit to understand what is stored and also why we do >>> need a little bit of information. >>> >>> BTW. our documentation already says that push is used for signaling, not >>> carrying actual data around, but based on this email I will update it to >>> have explicit information on best practices. Also, the documentation will >>> be clear about what (the alert only) is stored by the UPS, and why. (see >>> [4]) >>> >>> Greetings, >>> >>> Matthias >>> >>> - [1] >>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 >>> - [2] https://issues.jboss.org/browse/AGPUSH-971 >>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload >>> - [4] JIRA TO CREATE: update doc regarding push message storage and >>> best practices >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> 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 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150205/36629053/attachment.html From matzew at apache.org Thu Feb 5 17:25:33 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 23:25:33 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: <20150205202450.GA58032@abstractj.org> References: <20150205202450.GA58032@abstractj.org> Message-ID: On Thu, Feb 5, 2015 at 9:24 PM, Bruno Oliveira wrote: > On 2015-01-30, Matthias Wessendorf wrote: > > Hi, > > > > earlier this week there was some discussion about storing the payload of > > the push notifications ([1]). > > Hi Matthias, I think the usage of UPS and how it works is clear to > everyone here. The focus of the discussion last week was pretty much > about storing the content of the message. > > > > > Right now, we store some metrics (e.g. client that send the push, number > of > > devices, deliveryStatus etc) *and* the entire content of push > notification. > > This includes custom key/value pairs, the name of the sound file or even > > the size of the badge. > > > > Is all of that, storing the entire push notification payload really > needed? > > *No!* > > > > What do we need, and why? > > > > For counting the number of sent pushes (over time), the metrics are good > > enough. We do *NOT* need any of the push content for that, that's > correct! > > > > But we want to do more on the 1.1.0 release. We want to introduce some > > analytic features, to give our app developers (our users) a better > > understanding of their push usage (see [2]). > > You don't need the content of the message unless we're planning a > recommendation system or crunching data for some good reason. But we > already discussed about it. > yes, one reason is the planed feature to see how successful a push was. Perhaps later A/B testing. Another reason to store the alert is also a convenience for the app-developer. He can simply see what he sent already out. > > > > > In order to see details on how successful a push was (or not), we need to > > only store the value of the alert key: > > > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > > > > Ok, let's change that (see [3])! > > > > For our app developers, using the UPS to reach out to their mobile app > > users ("user engagement"), it's important to understand which push was > more > > successful: > > > > - "Get 10% discount today" (sent on a Monday) > > - "Our shop got new site, check it out and get 5% discount" (sent on a > > Friday) > > > > With the upcoming analytics we can help them to improve usage of their > app. > > User interaction is very important to a successful mobile application and > > push is a key driver here! Our app developers want an app that is > actively > > used by their users (Nobody wants his app sitting on the last page of the > > device or, even worse, in a folder together with Apple-Maps). Therefore > > it's critical for our app developers to understand the relevance of their > > push messages sent and how it impacts the usage of their app. That's why > we > > do the analytics described in [2]. And, yes - only the alert, not the > > entire payload is needed for that. > > Yes, only the alert, not the entire payload. > > > Privacy > > > > On the mentioned PR there was also some discussion about privacy > violations > > and stuff, when we store the content of the notification. An example > where > > *sensitive* data was sent over push was given. Something like: "Dear Mr. > > Joe, your blood donation appointment was scheduled for 3 p.m" > > > > 1. This is not how push notifications are used for mobile apps. Push > is > > to signal, not carry actual (sensitive) data around. > > 2. In a lot of countries, at least almost all European countries, you > > are not even allowed, by EU law, to give "data" to 3rd party providers > > (like the push-networks of Microsoft, Apple or Google). > > Yes my friend, a knife for me is to cut tomatoes, for other people > outside is to hurt. What you gonna do with data pretty much depends. > right, the same is generally true. The app-developer can store the alert (or even the entire payload) directly from his backend, including other 'sensitive' data. He does not need the UnifiedPush Server for that. Storing the alert gives the app-developer options to learn more about user engagement and if a (marketing) push was successful. > > > > > How does the actual (sensitive) data come to an app? > > > > As said above a push is used to signal/ping an app, to indicate that > there > > is real data for the mobile app user. In the background the mobile app > > tries to connect to the backend of the company, running/maintaining the > > mobile app. After the real data was fetched, "local notifcations" are > used > > to give the user a visible notification, like "Dear Mr. Joe, your blood > > donation appointment was scheduled for 3 p.m", or simply "New appointment > > scheduled". > > > > If the app was a chat system (and not a blood donation app from the Red > > Cross), it would be the same: After a signal, the app connects to "chat > > server" and receives the actual chat message from there. A reply would go > > over the same "chat server" connection. None of this would go over a 3rd > > party push network provider like Google, Microsoft or Apple. > > > > What would we store from these silent notifications? > > > > Nothing, since there is no alert, we would just store the metrics (e.g. > > client that send the push, number of devices, deliveryStatus etc). If the > > signaling is actually done with an alert (e.g. alert:"you got a new Chat > > text" or "New appointment scheduled"), we would store that. > > > > I hope this helps a bit to understand what is stored and also why we do > > need a little bit of information. > > Is not clear for me if you still need the content of the message and why. > As said above for the planed analytic feature (AGPUSH-971), where the app-developer can see if his push ("Alert 1") was useful or not. > > > > > BTW. our documentation already says that push is used for signaling, not > > carrying actual data around, but based on this email I will update it to > > have explicit information on best practices. Also, the documentation will > > be clear about what (the alert only) is stored by the UPS, and why. (see > > [4]) > > If we provide a clear and solid policy explaining why we need such kind > of data. I think is totally acceptable. > yup, agree > > > > Greetings, > > > > Matthias > > > > - [1] > https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > > - [2] https://issues.jboss.org/browse/AGPUSH-971 > > - [3] JIRA TO CREATE: to only store ALERT and not the full payload > > - [4] JIRA TO CREATE: update doc regarding push message storage and > best > > practices > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > > 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/20150205/cc05a17f/attachment-0001.html From matzew at apache.org Thu Feb 5 17:30:56 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 23:30:56 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: <54D3D91E.4000209@redhat.com> References: <54D3D91E.4000209@redhat.com> Message-ID: On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman wrote: > On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > Developer Program License Agreement": > > ... > Further, as a condition to using the APN, You agree not to transmit > sensitive personal or confidential information belonging to an individual > (e.g. a social security number, financial account or transactional > information, or any information where the individual may have a reasonable > expectation of secure transmission) as part of any Push Notification, and > You agree to comply with any applicable notice or consent requirements with > respect to any collection, transmission, maintenance, processing or use of > an end user?s personal information. > ... > > That means, if an app-developer sends something like "Your blood > donation appointment is tomorrow" to a user of his mobile app, the > app-developer is breaking the Apple terms _and_ the law in a lot of > countries (at least in all EU countries) :-) > > What we have to remember is that large amounts of information in aggregate > can become personally identifying even if any individual message is not. > So the law in this case doesn't help since it is only the data in context > which becomes personally identifying or protected. > > I don't think anyone is advocating for sending sensitive information via > push, but what we are advocating is not putting a big target on our (or our > user's) backs out of the gate by storing all of the messages by default. > Let's make storing the 'alert' an option, which needs to be enabled, and is turned off by default. This allows those that want to use the UPS for marekting reasons, to explicitly enable it. The enabling should be done with a proper* dialog/step inside of the setup-wizard that is planed for 1.1.x proper=> make it explicit that the UPS stores data, and link to privacy policy etc. the entire thing :-) Thoughts? > BTW. for Google I don't seem to find a similar paragraph, but IMO they > are not that thoughtful on privacy terms (compared to Apple). > > > Now, for our UPS guide (or documentation), I will add a few sentences to > make it clear that our app-developers should NEVER submit sensitive > personal or confidential information with a push. > > Regarding a "Privacy Policy", I will also make clear what data of the > push we store, for analytic reasons. > > You'll see a PR during my Friday. > > > > > Greetings, > Matthias > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > wrote: > >> I have created AGPUSH-1257 and AGPUSH-1258 >> >> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> earlier this week there was some discussion about storing the payload of >>> the push notifications ([1]). >>> >>> Right now, we store some metrics (e.g. client that send the push, number >>> of devices, deliveryStatus etc) *and* the entire content of push >>> notification. This includes custom key/value pairs, the name of the sound >>> file or even the size of the badge. >>> >>> Is all of that, storing the entire push notification payload really >>> needed? *No!* >>> >>> What do we need, and why? >>> >>> For counting the number of sent pushes (over time), the metrics are good >>> enough. We do *NOT* need any of the push content for that, that's >>> correct! >>> >>> But we want to do more on the 1.1.0 release. We want to introduce some >>> analytic features, to give our app developers (our users) a better >>> understanding of their push usage (see [2]). >>> >>> In order to see details on how successful a push was (or not), we need >>> to only store the value of the alert key: >>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png >>> >>> Ok, let's change that (see [3])! >>> >>> For our app developers, using the UPS to reach out to their mobile app >>> users ("user engagement"), it's important to understand which push was more >>> successful: >>> >>> - "Get 10% discount today" (sent on a Monday) >>> - "Our shop got new site, check it out and get 5% discount" (sent on >>> a Friday) >>> >>> With the upcoming analytics we can help them to improve usage of their >>> app. User interaction is very important to a successful mobile application >>> and push is a key driver here! Our app developers want an app that is >>> actively used by their users (Nobody wants his app sitting on the last page >>> of the device or, even worse, in a folder together with Apple-Maps). >>> Therefore it's critical for our app developers to understand the relevance >>> of their push messages sent and how it impacts the usage of their app. >>> That's why we do the analytics described in [2]. And, yes - only the alert, >>> not the entire payload is needed for that. >>> Privacy >>> >>> On the mentioned PR there was also some discussion about privacy >>> violations and stuff, when we store the content of the notification. An >>> example where *sensitive* data was sent over push was given. Something >>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 >>> p.m" >>> >>> 1. This is not how push notifications are used for mobile apps. Push >>> is to signal, not carry actual (sensitive) data around. >>> 2. In a lot of countries, at least almost all European countries, >>> you are not even allowed, by EU law, to give "data" to 3rd party providers >>> (like the push-networks of Microsoft, Apple or Google). >>> >>> How does the actual (sensitive) data come to an app? >>> >>> As said above a push is used to signal/ping an app, to indicate that >>> there is real data for the mobile app user. In the background the mobile >>> app tries to connect to the backend of the company, running/maintaining the >>> mobile app. After the real data was fetched, "local notifcations" are used >>> to give the user a visible notification, like "Dear Mr. Joe, your blood >>> donation appointment was scheduled for 3 p.m", or simply "New appointment >>> scheduled". >>> >>> If the app was a chat system (and not a blood donation app from the Red >>> Cross), it would be the same: After a signal, the app connects to "chat >>> server" and receives the actual chat message from there. A reply would go >>> over the same "chat server" connection. None of this would go over a 3rd >>> party push network provider like Google, Microsoft or Apple. >>> >>> What would we store from these silent notifications? >>> >>> Nothing, since there is no alert, we would just store the metrics (e.g. >>> client that send the push, number of devices, deliveryStatus etc). If the >>> signaling is actually done with an alert (e.g. alert:"you got a new Chat >>> text" or "New appointment scheduled"), we would store that. >>> >>> I hope this helps a bit to understand what is stored and also why we do >>> need a little bit of information. >>> >>> BTW. our documentation already says that push is used for signaling, not >>> carrying actual data around, but based on this email I will update it to >>> have explicit information on best practices. Also, the documentation will >>> be clear about what (the alert only) is stored by the UPS, and why. (see >>> [4]) >>> >>> Greetings, >>> >>> Matthias >>> >>> - [1] >>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 >>> - [2] https://issues.jboss.org/browse/AGPUSH-971 >>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload >>> - [4] JIRA TO CREATE: update doc regarding push message storage and >>> best practices >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> 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 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/20150205/c42c38e6/attachment.html From matzew at apache.org Thu Feb 5 17:33:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 5 Feb 2015 23:33:37 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: <54D3D91E.4000209@redhat.com> Message-ID: On Thu, Feb 5, 2015 at 10:51 PM, Sebastien Blanc wrote: > > > On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman > wrote: > >> On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: >> >> While working on the doc for AGPUSH-1258, I found this in Apple's "iOS >> Developer Program License Agreement": >> >> ... >> Further, as a condition to using the APN, You agree not to transmit >> sensitive personal or confidential information belonging to an individual >> (e.g. a social security number, financial account or transactional >> information, or any information where the individual may have a reasonable >> expectation of secure transmission) as part of any Push Notification, and >> You agree to comply with any applicable notice or consent requirements with >> respect to any collection, transmission, maintenance, processing or use of >> an end user?s personal information. >> ... >> >> That means, if an app-developer sends something like "Your blood >> donation appointment is tomorrow" to a user of his mobile app, the >> app-developer is breaking the Apple terms _and_ the law in a lot of >> countries (at least in all EU countries) :-) >> >> What we have to remember is that large amounts of information in >> aggregate can become personally identifying even if any individual message >> is not. So the law in this case doesn't help since it is only the data in >> context which becomes personally identifying or protected. >> > Good point. > >> >> I don't think anyone is advocating for sending sensitive information via >> push, but what we are advocating is not putting a big target on our (or our >> user's) backs out of the gate by storing all of the messages by default. >> > Only the alert is stored (PR has been merged) . But, and this is just an > idea that just popped out, couldn't we encrypt the value of the alert that > is stored? It could be by default or a config thingy ... > yes, I am totally fine it making this a configurable option, which needs to be enabled, for safety reasons. Those that want it, need to enabled it. I will work on the JIRA tickets for this, if we are all cool with this. Greetings, Matthias > >> > >> BTW. for Google I don't seem to find a similar paragraph, but IMO they >> are not that thoughtful on privacy terms (compared to Apple). >> >> >> Now, for our UPS guide (or documentation), I will add a few sentences >> to make it clear that our app-developers should NEVER submit sensitive >> personal or confidential information with a push. >> >> Regarding a "Privacy Policy", I will also make clear what data of the >> push we store, for analytic reasons. >> >> You'll see a PR during my Friday. >> >> >> >> >> Greetings, >> Matthias >> >> >> >> On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf >> wrote: >> >>> I have created AGPUSH-1257 and AGPUSH-1258 >>> >>> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> earlier this week there was some discussion about storing the payload >>>> of the push notifications ([1]). >>>> >>>> Right now, we store some metrics (e.g. client that send the push, >>>> number of devices, deliveryStatus etc) *and* the entire content of >>>> push notification. This includes custom key/value pairs, the name of the >>>> sound file or even the size of the badge. >>>> >>>> Is all of that, storing the entire push notification payload really >>>> needed? *No!* >>>> >>>> What do we need, and why? >>>> >>>> For counting the number of sent pushes (over time), the metrics are >>>> good enough. We do *NOT* need any of the push content for that, that's >>>> correct! >>>> >>>> But we want to do more on the 1.1.0 release. We want to introduce some >>>> analytic features, to give our app developers (our users) a better >>>> understanding of their push usage (see [2]). >>>> >>>> In order to see details on how successful a push was (or not), we need >>>> to only store the value of the alert key: >>>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png >>>> >>>> Ok, let's change that (see [3])! >>>> >>>> For our app developers, using the UPS to reach out to their mobile app >>>> users ("user engagement"), it's important to understand which push was more >>>> successful: >>>> >>>> - "Get 10% discount today" (sent on a Monday) >>>> - "Our shop got new site, check it out and get 5% discount" (sent >>>> on a Friday) >>>> >>>> With the upcoming analytics we can help them to improve usage of their >>>> app. User interaction is very important to a successful mobile application >>>> and push is a key driver here! Our app developers want an app that is >>>> actively used by their users (Nobody wants his app sitting on the last page >>>> of the device or, even worse, in a folder together with Apple-Maps). >>>> Therefore it's critical for our app developers to understand the relevance >>>> of their push messages sent and how it impacts the usage of their app. >>>> That's why we do the analytics described in [2]. And, yes - only the alert, >>>> not the entire payload is needed for that. >>>> Privacy >>>> >>>> On the mentioned PR there was also some discussion about privacy >>>> violations and stuff, when we store the content of the notification. An >>>> example where *sensitive* data was sent over push was given. Something >>>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 >>>> p.m" >>>> >>>> 1. This is not how push notifications are used for mobile apps. >>>> Push is to signal, not carry actual (sensitive) data around. >>>> 2. In a lot of countries, at least almost all European countries, >>>> you are not even allowed, by EU law, to give "data" to 3rd party providers >>>> (like the push-networks of Microsoft, Apple or Google). >>>> >>>> How does the actual (sensitive) data come to an app? >>>> >>>> As said above a push is used to signal/ping an app, to indicate that >>>> there is real data for the mobile app user. In the background the mobile >>>> app tries to connect to the backend of the company, running/maintaining the >>>> mobile app. After the real data was fetched, "local notifcations" are used >>>> to give the user a visible notification, like "Dear Mr. Joe, your blood >>>> donation appointment was scheduled for 3 p.m", or simply "New appointment >>>> scheduled". >>>> >>>> If the app was a chat system (and not a blood donation app from the Red >>>> Cross), it would be the same: After a signal, the app connects to "chat >>>> server" and receives the actual chat message from there. A reply would go >>>> over the same "chat server" connection. None of this would go over a 3rd >>>> party push network provider like Google, Microsoft or Apple. >>>> >>>> What would we store from these silent notifications? >>>> >>>> Nothing, since there is no alert, we would just store the metrics (e.g. >>>> client that send the push, number of devices, deliveryStatus etc). If the >>>> signaling is actually done with an alert (e.g. alert:"you got a new Chat >>>> text" or "New appointment scheduled"), we would store that. >>>> >>>> I hope this helps a bit to understand what is stored and also why we do >>>> need a little bit of information. >>>> >>>> BTW. our documentation already says that push is used for signaling, >>>> not carrying actual data around, but based on this email I will update it >>>> to have explicit information on best practices. Also, the documentation >>>> will be clear about what (the alert only) is stored by the UPS, and why. >>>> (see [4]) >>>> >>>> Greetings, >>>> >>>> Matthias >>>> >>>> - [1] >>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 >>>> - [2] https://issues.jboss.org/browse/AGPUSH-971 >>>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload >>>> - [4] JIRA TO CREATE: update doc regarding push message storage and >>>> best practices >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>> >>> >>> >>> -- >>> 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 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 >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150205/8804d5bf/attachment-0001.html From scm.blanc at gmail.com Fri Feb 6 04:33:26 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 6 Feb 2015 10:33:26 +0100 Subject: [aerogear-dev] [RELEASE] java-adm 0.1.0 has been staged In-Reply-To: References: Message-ID: Button has just been pressed ! On Wed, Feb 4, 2015 at 10:19 AM, Matthias Wessendorf wrote: > I have reviewed and refactored some code for the 0.1.0 release, therefore > I am +1 > > -M > > On Wed, Feb 4, 2015 at 10:14 AM, Sebastien Blanc > wrote: > >> Good morning, >> >> I'm pleased to announce that java-adm 0.1.0 has been staged : >> >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4780/ >> >> This is the first release ! The java-adm library is a connector to the >> Amazon Device Messaging Network. For instance, this library will be used by >> the UnifiedPush server for ADM support but it can be used anywhere else. >> >> If I heard nothing , I will push the button this Friday. >> >> Sebi >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150206/f5c5593b/attachment.html From bruno at abstractj.org Fri Feb 6 05:53:10 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 6 Feb 2015 08:53:10 -0200 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: <54D3D91E.4000209@redhat.com> Message-ID: <20150206105310.GC58032@abstractj.org> On 2015-02-05, Sebastien Blanc wrote: > On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman wrote: > > > On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > > > > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > > Developer Program License Agreement": > > > > ... > > Further, as a condition to using the APN, You agree not to transmit > > sensitive personal or confidential information belonging to an individual > > (e.g. a social security number, financial account or transactional > > information, or any information where the individual may have a reasonable > > expectation of secure transmission) as part of any Push Notification, and > > You agree to comply with any applicable notice or consent requirements with > > respect to any collection, transmission, maintenance, processing or use of > > an end user?s personal information. > > ... > > > > That means, if an app-developer sends something like "Your blood > > donation appointment is tomorrow" to a user of his mobile app, the > > app-developer is breaking the Apple terms _and_ the law in a lot of > > countries (at least in all EU countries) :-) > > > > What we have to remember is that large amounts of information in aggregate > > can become personally identifying even if any individual message is not. > > So the law in this case doesn't help since it is only the data in context > > which becomes personally identifying or protected. > > > Good point. > > > > > I don't think anyone is advocating for sending sensitive information via > > push, but what we are advocating is not putting a big target on our (or our > > user's) backs out of the gate by storing all of the messages by default. > > > Only the alert is stored (PR has been merged) . But, and this is just an > idea that just popped out, couldn't we encrypt the value of the alert that > is stored? It could be by default or a config thingy ... What's the big difference between an admin reading the messages sent to me or not? Encrypt won't fix all the problems. > > > > > > > > BTW. for Google I don't seem to find a similar paragraph, but IMO they > > are not that thoughtful on privacy terms (compared to Apple). > > > > > > Now, for our UPS guide (or documentation), I will add a few sentences to > > make it clear that our app-developers should NEVER submit sensitive > > personal or confidential information with a push. > > > > Regarding a "Privacy Policy", I will also make clear what data of the > > push we store, for analytic reasons. > > > > You'll see a PR during my Friday. > > > > > > > > > > Greetings, > > Matthias > > > > > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > > wrote: > > > >> I have created AGPUSH-1257 and AGPUSH-1258 > >> > >> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf > >> wrote: > >> > >>> Hi, > >>> > >>> earlier this week there was some discussion about storing the payload of > >>> the push notifications ([1]). > >>> > >>> Right now, we store some metrics (e.g. client that send the push, number > >>> of devices, deliveryStatus etc) *and* the entire content of push > >>> notification. This includes custom key/value pairs, the name of the sound > >>> file or even the size of the badge. > >>> > >>> Is all of that, storing the entire push notification payload really > >>> needed? *No!* > >>> > >>> What do we need, and why? > >>> > >>> For counting the number of sent pushes (over time), the metrics are good > >>> enough. We do *NOT* need any of the push content for that, that's > >>> correct! > >>> > >>> But we want to do more on the 1.1.0 release. We want to introduce some > >>> analytic features, to give our app developers (our users) a better > >>> understanding of their push usage (see [2]). > >>> > >>> In order to see details on how successful a push was (or not), we need > >>> to only store the value of the alert key: > >>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > >>> > >>> Ok, let's change that (see [3])! > >>> > >>> For our app developers, using the UPS to reach out to their mobile app > >>> users ("user engagement"), it's important to understand which push was more > >>> successful: > >>> > >>> - "Get 10% discount today" (sent on a Monday) > >>> - "Our shop got new site, check it out and get 5% discount" (sent on > >>> a Friday) > >>> > >>> With the upcoming analytics we can help them to improve usage of their > >>> app. User interaction is very important to a successful mobile application > >>> and push is a key driver here! Our app developers want an app that is > >>> actively used by their users (Nobody wants his app sitting on the last page > >>> of the device or, even worse, in a folder together with Apple-Maps). > >>> Therefore it's critical for our app developers to understand the relevance > >>> of their push messages sent and how it impacts the usage of their app. > >>> That's why we do the analytics described in [2]. And, yes - only the alert, > >>> not the entire payload is needed for that. > >>> Privacy > >>> > >>> On the mentioned PR there was also some discussion about privacy > >>> violations and stuff, when we store the content of the notification. An > >>> example where *sensitive* data was sent over push was given. Something > >>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 > >>> p.m" > >>> > >>> 1. This is not how push notifications are used for mobile apps. Push > >>> is to signal, not carry actual (sensitive) data around. > >>> 2. In a lot of countries, at least almost all European countries, > >>> you are not even allowed, by EU law, to give "data" to 3rd party providers > >>> (like the push-networks of Microsoft, Apple or Google). > >>> > >>> How does the actual (sensitive) data come to an app? > >>> > >>> As said above a push is used to signal/ping an app, to indicate that > >>> there is real data for the mobile app user. In the background the mobile > >>> app tries to connect to the backend of the company, running/maintaining the > >>> mobile app. After the real data was fetched, "local notifcations" are used > >>> to give the user a visible notification, like "Dear Mr. Joe, your blood > >>> donation appointment was scheduled for 3 p.m", or simply "New appointment > >>> scheduled". > >>> > >>> If the app was a chat system (and not a blood donation app from the Red > >>> Cross), it would be the same: After a signal, the app connects to "chat > >>> server" and receives the actual chat message from there. A reply would go > >>> over the same "chat server" connection. None of this would go over a 3rd > >>> party push network provider like Google, Microsoft or Apple. > >>> > >>> What would we store from these silent notifications? > >>> > >>> Nothing, since there is no alert, we would just store the metrics (e.g. > >>> client that send the push, number of devices, deliveryStatus etc). If the > >>> signaling is actually done with an alert (e.g. alert:"you got a new Chat > >>> text" or "New appointment scheduled"), we would store that. > >>> > >>> I hope this helps a bit to understand what is stored and also why we do > >>> need a little bit of information. > >>> > >>> BTW. our documentation already says that push is used for signaling, not > >>> carrying actual data around, but based on this email I will update it to > >>> have explicit information on best practices. Also, the documentation will > >>> be clear about what (the alert only) is stored by the UPS, and why. (see > >>> [4]) > >>> > >>> Greetings, > >>> > >>> Matthias > >>> > >>> - [1] > >>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > >>> - [2] https://issues.jboss.org/browse/AGPUSH-971 > >>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload > >>> - [4] JIRA TO CREATE: update doc regarding push message storage and > >>> best practices > >>> > >>> > >>> -- > >>> Matthias Wessendorf > >>> > >>> blog: http://matthiaswessendorf.wordpress.com/ > >>> sessions: http://www.slideshare.net/mwessendorf > >>> twitter: http://twitter.com/mwessendorf > >>> > >> > >> > >> > >> -- > >> 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 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 > > > _______________________________________________ > 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 Feb 6 05:54:18 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 6 Feb 2015 08:54:18 -0200 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: <54D3D91E.4000209@redhat.com> Message-ID: <20150206105418.GD58032@abstractj.org> On 2015-02-05, Matthias Wessendorf wrote: > On Thu, Feb 5, 2015 at 10:51 PM, Sebastien Blanc > wrote: > > > > > > > On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman > > wrote: > > > >> On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > >> > >> While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > >> Developer Program License Agreement": > >> > >> ... > >> Further, as a condition to using the APN, You agree not to transmit > >> sensitive personal or confidential information belonging to an individual > >> (e.g. a social security number, financial account or transactional > >> information, or any information where the individual may have a reasonable > >> expectation of secure transmission) as part of any Push Notification, and > >> You agree to comply with any applicable notice or consent requirements with > >> respect to any collection, transmission, maintenance, processing or use of > >> an end user?s personal information. > >> ... > >> > >> That means, if an app-developer sends something like "Your blood > >> donation appointment is tomorrow" to a user of his mobile app, the > >> app-developer is breaking the Apple terms _and_ the law in a lot of > >> countries (at least in all EU countries) :-) > >> > >> What we have to remember is that large amounts of information in > >> aggregate can become personally identifying even if any individual message > >> is not. So the law in this case doesn't help since it is only the data in > >> context which becomes personally identifying or protected. > >> > > Good point. > > > >> > >> I don't think anyone is advocating for sending sensitive information via > >> push, but what we are advocating is not putting a big target on our (or our > >> user's) backs out of the gate by storing all of the messages by default. > >> > > Only the alert is stored (PR has been merged) . But, and this is just an > > idea that just popped out, couldn't we encrypt the value of the alert that > > is stored? It could be by default or a config thingy ... > > > > yes, I am totally fine it making this a configurable option, which needs to > be enabled, for safety reasons. Those that want it, need to enabled it. > > I will work on the JIRA tickets for this, if we are all cool with this. So the decision of storing messages is up to the admin? > > > Greetings, > Matthias > > > > > > >> > > > >> BTW. for Google I don't seem to find a similar paragraph, but IMO they > >> are not that thoughtful on privacy terms (compared to Apple). > >> > >> > >> Now, for our UPS guide (or documentation), I will add a few sentences > >> to make it clear that our app-developers should NEVER submit sensitive > >> personal or confidential information with a push. > >> > >> Regarding a "Privacy Policy", I will also make clear what data of the > >> push we store, for analytic reasons. > >> > >> You'll see a PR during my Friday. > >> > >> > >> > >> > >> Greetings, > >> Matthias > >> > >> > >> > >> On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > >> wrote: > >> > >>> I have created AGPUSH-1257 and AGPUSH-1258 > >>> > >>> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> earlier this week there was some discussion about storing the payload > >>>> of the push notifications ([1]). > >>>> > >>>> Right now, we store some metrics (e.g. client that send the push, > >>>> number of devices, deliveryStatus etc) *and* the entire content of > >>>> push notification. This includes custom key/value pairs, the name of the > >>>> sound file or even the size of the badge. > >>>> > >>>> Is all of that, storing the entire push notification payload really > >>>> needed? *No!* > >>>> > >>>> What do we need, and why? > >>>> > >>>> For counting the number of sent pushes (over time), the metrics are > >>>> good enough. We do *NOT* need any of the push content for that, that's > >>>> correct! > >>>> > >>>> But we want to do more on the 1.1.0 release. We want to introduce some > >>>> analytic features, to give our app developers (our users) a better > >>>> understanding of their push usage (see [2]). > >>>> > >>>> In order to see details on how successful a push was (or not), we need > >>>> to only store the value of the alert key: > >>>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > >>>> > >>>> Ok, let's change that (see [3])! > >>>> > >>>> For our app developers, using the UPS to reach out to their mobile app > >>>> users ("user engagement"), it's important to understand which push was more > >>>> successful: > >>>> > >>>> - "Get 10% discount today" (sent on a Monday) > >>>> - "Our shop got new site, check it out and get 5% discount" (sent > >>>> on a Friday) > >>>> > >>>> With the upcoming analytics we can help them to improve usage of their > >>>> app. User interaction is very important to a successful mobile application > >>>> and push is a key driver here! Our app developers want an app that is > >>>> actively used by their users (Nobody wants his app sitting on the last page > >>>> of the device or, even worse, in a folder together with Apple-Maps). > >>>> Therefore it's critical for our app developers to understand the relevance > >>>> of their push messages sent and how it impacts the usage of their app. > >>>> That's why we do the analytics described in [2]. And, yes - only the alert, > >>>> not the entire payload is needed for that. > >>>> Privacy > >>>> > >>>> On the mentioned PR there was also some discussion about privacy > >>>> violations and stuff, when we store the content of the notification. An > >>>> example where *sensitive* data was sent over push was given. Something > >>>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 > >>>> p.m" > >>>> > >>>> 1. This is not how push notifications are used for mobile apps. > >>>> Push is to signal, not carry actual (sensitive) data around. > >>>> 2. In a lot of countries, at least almost all European countries, > >>>> you are not even allowed, by EU law, to give "data" to 3rd party providers > >>>> (like the push-networks of Microsoft, Apple or Google). > >>>> > >>>> How does the actual (sensitive) data come to an app? > >>>> > >>>> As said above a push is used to signal/ping an app, to indicate that > >>>> there is real data for the mobile app user. In the background the mobile > >>>> app tries to connect to the backend of the company, running/maintaining the > >>>> mobile app. After the real data was fetched, "local notifcations" are used > >>>> to give the user a visible notification, like "Dear Mr. Joe, your blood > >>>> donation appointment was scheduled for 3 p.m", or simply "New appointment > >>>> scheduled". > >>>> > >>>> If the app was a chat system (and not a blood donation app from the Red > >>>> Cross), it would be the same: After a signal, the app connects to "chat > >>>> server" and receives the actual chat message from there. A reply would go > >>>> over the same "chat server" connection. None of this would go over a 3rd > >>>> party push network provider like Google, Microsoft or Apple. > >>>> > >>>> What would we store from these silent notifications? > >>>> > >>>> Nothing, since there is no alert, we would just store the metrics (e.g. > >>>> client that send the push, number of devices, deliveryStatus etc). If the > >>>> signaling is actually done with an alert (e.g. alert:"you got a new Chat > >>>> text" or "New appointment scheduled"), we would store that. > >>>> > >>>> I hope this helps a bit to understand what is stored and also why we do > >>>> need a little bit of information. > >>>> > >>>> BTW. our documentation already says that push is used for signaling, > >>>> not carrying actual data around, but based on this email I will update it > >>>> to have explicit information on best practices. Also, the documentation > >>>> will be clear about what (the alert only) is stored by the UPS, and why. > >>>> (see [4]) > >>>> > >>>> Greetings, > >>>> > >>>> Matthias > >>>> > >>>> - [1] > >>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > >>>> - [2] https://issues.jboss.org/browse/AGPUSH-971 > >>>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload > >>>> - [4] JIRA TO CREATE: update doc regarding push message storage and > >>>> best practices > >>>> > >>>> > >>>> -- > >>>> Matthias Wessendorf > >>>> > >>>> blog: http://matthiaswessendorf.wordpress.com/ > >>>> sessions: http://www.slideshare.net/mwessendorf > >>>> twitter: http://twitter.com/mwessendorf > >>>> > >>> > >>> > >>> > >>> -- > >>> 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 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 > >> > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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 Fri Feb 6 05:56:29 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 6 Feb 2015 08:56:29 -0200 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: References: <54D3D91E.4000209@redhat.com> Message-ID: <20150206105629.GE58032@abstractj.org> On 2015-02-05, Matthias Wessendorf wrote: > On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman wrote: > > > On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > > > > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > > Developer Program License Agreement": > > > > ... > > Further, as a condition to using the APN, You agree not to transmit > > sensitive personal or confidential information belonging to an individual > > (e.g. a social security number, financial account or transactional > > information, or any information where the individual may have a reasonable > > expectation of secure transmission) as part of any Push Notification, and > > You agree to comply with any applicable notice or consent requirements with > > respect to any collection, transmission, maintenance, processing or use of > > an end user?s personal information. > > ... > > > > That means, if an app-developer sends something like "Your blood > > donation appointment is tomorrow" to a user of his mobile app, the > > app-developer is breaking the Apple terms _and_ the law in a lot of > > countries (at least in all EU countries) :-) > > > > What we have to remember is that large amounts of information in aggregate > > can become personally identifying even if any individual message is not. > > So the law in this case doesn't help since it is only the data in context > > which becomes personally identifying or protected. > > > > I don't think anyone is advocating for sending sensitive information via > > push, but what we are advocating is not putting a big target on our (or our > > user's) backs out of the gate by storing all of the messages by default. > > > > Let's make storing the 'alert' an option, which needs to be enabled, and is > turned off by default. > > This allows those that want to use the UPS for marekting reasons, to > explicitly enable it. The enabling should be done with a proper* > dialog/step inside of the setup-wizard that is planed for 1.1.x > > proper=> make it explicit that the UPS stores data, and link to privacy > policy etc. the entire thing :-) +1 on privacy policy -1 on let people enable/disable for marketing reasons. > > > Thoughts? > > > > BTW. for Google I don't seem to find a similar paragraph, but IMO they > > are not that thoughtful on privacy terms (compared to Apple). > > > > > > Now, for our UPS guide (or documentation), I will add a few sentences to > > make it clear that our app-developers should NEVER submit sensitive > > personal or confidential information with a push. > > > > Regarding a "Privacy Policy", I will also make clear what data of the > > push we store, for analytic reasons. > > > > You'll see a PR during my Friday. > > > > > > > > > > Greetings, > > Matthias > > > > > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > > wrote: > > > >> I have created AGPUSH-1257 and AGPUSH-1258 > >> > >> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf > >> wrote: > >> > >>> Hi, > >>> > >>> earlier this week there was some discussion about storing the payload of > >>> the push notifications ([1]). > >>> > >>> Right now, we store some metrics (e.g. client that send the push, number > >>> of devices, deliveryStatus etc) *and* the entire content of push > >>> notification. This includes custom key/value pairs, the name of the sound > >>> file or even the size of the badge. > >>> > >>> Is all of that, storing the entire push notification payload really > >>> needed? *No!* > >>> > >>> What do we need, and why? > >>> > >>> For counting the number of sent pushes (over time), the metrics are good > >>> enough. We do *NOT* need any of the push content for that, that's > >>> correct! > >>> > >>> But we want to do more on the 1.1.0 release. We want to introduce some > >>> analytic features, to give our app developers (our users) a better > >>> understanding of their push usage (see [2]). > >>> > >>> In order to see details on how successful a push was (or not), we need > >>> to only store the value of the alert key: > >>> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > >>> > >>> Ok, let's change that (see [3])! > >>> > >>> For our app developers, using the UPS to reach out to their mobile app > >>> users ("user engagement"), it's important to understand which push was more > >>> successful: > >>> > >>> - "Get 10% discount today" (sent on a Monday) > >>> - "Our shop got new site, check it out and get 5% discount" (sent on > >>> a Friday) > >>> > >>> With the upcoming analytics we can help them to improve usage of their > >>> app. User interaction is very important to a successful mobile application > >>> and push is a key driver here! Our app developers want an app that is > >>> actively used by their users (Nobody wants his app sitting on the last page > >>> of the device or, even worse, in a folder together with Apple-Maps). > >>> Therefore it's critical for our app developers to understand the relevance > >>> of their push messages sent and how it impacts the usage of their app. > >>> That's why we do the analytics described in [2]. And, yes - only the alert, > >>> not the entire payload is needed for that. > >>> Privacy > >>> > >>> On the mentioned PR there was also some discussion about privacy > >>> violations and stuff, when we store the content of the notification. An > >>> example where *sensitive* data was sent over push was given. Something > >>> like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 > >>> p.m" > >>> > >>> 1. This is not how push notifications are used for mobile apps. Push > >>> is to signal, not carry actual (sensitive) data around. > >>> 2. In a lot of countries, at least almost all European countries, > >>> you are not even allowed, by EU law, to give "data" to 3rd party providers > >>> (like the push-networks of Microsoft, Apple or Google). > >>> > >>> How does the actual (sensitive) data come to an app? > >>> > >>> As said above a push is used to signal/ping an app, to indicate that > >>> there is real data for the mobile app user. In the background the mobile > >>> app tries to connect to the backend of the company, running/maintaining the > >>> mobile app. After the real data was fetched, "local notifcations" are used > >>> to give the user a visible notification, like "Dear Mr. Joe, your blood > >>> donation appointment was scheduled for 3 p.m", or simply "New appointment > >>> scheduled". > >>> > >>> If the app was a chat system (and not a blood donation app from the Red > >>> Cross), it would be the same: After a signal, the app connects to "chat > >>> server" and receives the actual chat message from there. A reply would go > >>> over the same "chat server" connection. None of this would go over a 3rd > >>> party push network provider like Google, Microsoft or Apple. > >>> > >>> What would we store from these silent notifications? > >>> > >>> Nothing, since there is no alert, we would just store the metrics (e.g. > >>> client that send the push, number of devices, deliveryStatus etc). If the > >>> signaling is actually done with an alert (e.g. alert:"you got a new Chat > >>> text" or "New appointment scheduled"), we would store that. > >>> > >>> I hope this helps a bit to understand what is stored and also why we do > >>> need a little bit of information. > >>> > >>> BTW. our documentation already says that push is used for signaling, not > >>> carrying actual data around, but based on this email I will update it to > >>> have explicit information on best practices. Also, the documentation will > >>> be clear about what (the alert only) is stored by the UPS, and why. (see > >>> [4]) > >>> > >>> Greetings, > >>> > >>> Matthias > >>> > >>> - [1] > >>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > >>> - [2] https://issues.jboss.org/browse/AGPUSH-971 > >>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload > >>> - [4] JIRA TO CREATE: update doc regarding push message storage and > >>> best practices > >>> > >>> > >>> -- > >>> Matthias Wessendorf > >>> > >>> blog: http://matthiaswessendorf.wordpress.com/ > >>> sessions: http://www.slideshare.net/mwessendorf > >>> twitter: http://twitter.com/mwessendorf > >>> > >> > >> > >> > >> -- > >> 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 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 -- abstractj PGP: 0x84DC9914 From matzew at apache.org Fri Feb 6 06:39:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 6 Feb 2015 12:39:41 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: <20150206105418.GD58032@abstractj.org> References: <54D3D91E.4000209@redhat.com> <20150206105418.GD58032@abstractj.org> Message-ID: On Fri, Feb 6, 2015 at 11:54 AM, Bruno Oliveira wrote: > On 2015-02-05, Matthias Wessendorf wrote: > > On Thu, Feb 5, 2015 at 10:51 PM, Sebastien Blanc > > wrote: > > > > > > > > > > > On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman > > > wrote: > > > > > >> On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > > >> > > >> While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > > >> Developer Program License Agreement": > > >> > > >> ... > > >> Further, as a condition to using the APN, You agree not to transmit > > >> sensitive personal or confidential information belonging to an > individual > > >> (e.g. a social security number, financial account or transactional > > >> information, or any information where the individual may have a > reasonable > > >> expectation of secure transmission) as part of any Push Notification, > and > > >> You agree to comply with any applicable notice or consent > requirements with > > >> respect to any collection, transmission, maintenance, processing or > use of > > >> an end user?s personal information. > > >> ... > > >> > > >> That means, if an app-developer sends something like "Your blood > > >> donation appointment is tomorrow" to a user of his mobile app, the > > >> app-developer is breaking the Apple terms _and_ the law in a lot of > > >> countries (at least in all EU countries) :-) > > >> > > >> What we have to remember is that large amounts of information in > > >> aggregate can become personally identifying even if any individual > message > > >> is not. So the law in this case doesn't help since it is only the > data in > > >> context which becomes personally identifying or protected. > > >> > > > Good point. > > > > > >> > > >> I don't think anyone is advocating for sending sensitive information > via > > >> push, but what we are advocating is not putting a big target on our > (or our > > >> user's) backs out of the gate by storing all of the messages by > default. > > >> > > > Only the alert is stored (PR has been merged) . But, and this is just > an > > > idea that just popped out, couldn't we encrypt the value of the alert > that > > > is stored? It could be by default or a config thingy ... > > > > > > > yes, I am totally fine it making this a configurable option, which needs > to > > be enabled, for safety reasons. Those that want it, need to enabled it. > > > > I will work on the JIRA tickets for this, if we are all cool with this. > > So the decision of storing messages is up to the admin? > Good point, let's have that option to store the alert or not on the "Create Application screen" (default would be disabled). That way the app-developer company can decided per Push App if that is needed or not. - Something like the "Blood donation" app does not need it, since push is used as signalling here to fetch the 'sensitive" data from the app-developers own backend. (Does not make sense to have analytics for a gazillion pushes that are all "New appointment", or similar) - Something like the mobile app for BBC may find it useful to see if a push like "Breaking news: New iPhone presented" was well received, or not. - Similar to an app of a shopping website, may find it also useful to see if a push was successful or not (e.g. "10% discount", on a Monday - versus - "5% discount", on a Friday). These are the classic examples why we do nee the analytics from the often given JIRA. > > > > > > > Greetings, > > Matthias > > > > > > > > > > > >> > > > > > >> BTW. for Google I don't seem to find a similar paragraph, but IMO > they > > >> are not that thoughtful on privacy terms (compared to Apple). > > >> > > >> > > >> Now, for our UPS guide (or documentation), I will add a few sentences > > >> to make it clear that our app-developers should NEVER submit sensitive > > >> personal or confidential information with a push. > > >> > > >> Regarding a "Privacy Policy", I will also make clear what data of the > > >> push we store, for analytic reasons. > > >> > > >> You'll see a PR during my Friday. > > >> > > >> > > >> > > >> > > >> Greetings, > > >> Matthias > > >> > > >> > > >> > > >> On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf < > matzew at apache.org> > > >> wrote: > > >> > > >>> I have created AGPUSH-1257 and AGPUSH-1258 > > >>> > > >>> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf < > matzew at apache.org> > > >>> wrote: > > >>> > > >>>> Hi, > > >>>> > > >>>> earlier this week there was some discussion about storing the > payload > > >>>> of the push notifications ([1]). > > >>>> > > >>>> Right now, we store some metrics (e.g. client that send the push, > > >>>> number of devices, deliveryStatus etc) *and* the entire content of > > >>>> push notification. This includes custom key/value pairs, the name > of the > > >>>> sound file or even the size of the badge. > > >>>> > > >>>> Is all of that, storing the entire push notification payload really > > >>>> needed? *No!* > > >>>> > > >>>> What do we need, and why? > > >>>> > > >>>> For counting the number of sent pushes (over time), the metrics are > > >>>> good enough. We do *NOT* need any of the push content for that, > that's > > >>>> correct! > > >>>> > > >>>> But we want to do more on the 1.1.0 release. We want to introduce > some > > >>>> analytic features, to give our app developers (our users) a better > > >>>> understanding of their push usage (see [2]). > > >>>> > > >>>> In order to see details on how successful a push was (or not), we > need > > >>>> to only store the value of the alert key: > > >>>> > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > > >>>> > > >>>> Ok, let's change that (see [3])! > > >>>> > > >>>> For our app developers, using the UPS to reach out to their mobile > app > > >>>> users ("user engagement"), it's important to understand which push > was more > > >>>> successful: > > >>>> > > >>>> - "Get 10% discount today" (sent on a Monday) > > >>>> - "Our shop got new site, check it out and get 5% discount" (sent > > >>>> on a Friday) > > >>>> > > >>>> With the upcoming analytics we can help them to improve usage of > their > > >>>> app. User interaction is very important to a successful mobile > application > > >>>> and push is a key driver here! Our app developers want an app that > is > > >>>> actively used by their users (Nobody wants his app sitting on the > last page > > >>>> of the device or, even worse, in a folder together with Apple-Maps). > > >>>> Therefore it's critical for our app developers to understand the > relevance > > >>>> of their push messages sent and how it impacts the usage of their > app. > > >>>> That's why we do the analytics described in [2]. And, yes - only > the alert, > > >>>> not the entire payload is needed for that. > > >>>> >Privacy > > >>>> > > >>>> On the mentioned PR there was also some discussion about privacy > > >>>> violations and stuff, when we store the content of the > notification. An > > >>>> example where *sensitive* data was sent over push was given. > Something > > >>>> like: "Dear Mr. Joe, your blood donation appointment was scheduled > for 3 > > >>>> p.m" > > >>>> > > >>>> 1. This is not how push notifications are used for mobile apps. > > >>>> Push is to signal, not carry actual (sensitive) data around. > > >>>> 2. In a lot of countries, at least almost all European countries, > > >>>> you are not even allowed, by EU law, to give "data" to 3rd party > providers > > >>>> (like the push-networks of Microsoft, Apple or Google). > > >>>> > > >>>> How does the actual (sensitive) data come to an app? > > >>>> > > >>>> As said above a push is used to signal/ping an app, to indicate that > > >>>> there is real data for the mobile app user. In the background the > mobile > > >>>> app tries to connect to the backend of the company, > running/maintaining the > > >>>> mobile app. After the real data was fetched, "local notifcations" > are used > > >>>> to give the user a visible notification, like "Dear Mr. Joe, your > blood > > >>>> donation appointment was scheduled for 3 p.m", or simply "New > appointment > > >>>> scheduled". > > >>>> > > >>>> If the app was a chat system (and not a blood donation app from the > Red > > >>>> Cross), it would be the same: After a signal, the app connects to > "chat > > >>>> server" and receives the actual chat message from there. A reply > would go > > >>>> over the same "chat server" connection. None of this would go over > a 3rd > > >>>> party push network provider like Google, Microsoft or Apple. > > >>>> > > >>>> What would we store from these silent notifications? > > >>>> > > >>>> Nothing, since there is no alert, we would just store the metrics > (e.g. > > >>>> client that send the push, number of devices, deliveryStatus etc). > If the > > >>>> signaling is actually done with an alert (e.g. alert:"you got a new > Chat > > >>>> text" or "New appointment scheduled"), we would store that. > > >>>> > > >>>> I hope this helps a bit to understand what is stored and also why > we do > > >>>> need a little bit of information. > > >>>> > > >>>> BTW. our documentation already says that push is used for signaling, > > >>>> not carrying actual data around, but based on this email I will > update it > > >>>> to have explicit information on best practices. Also, the > documentation > > >>>> will be clear about what (the alert only) is stored by the UPS, and > why. > > >>>> (see [4]) > > >>>> > > >>>> Greetings, > > >>>> > > >>>> Matthias > > >>>> > > >>>> - [1] > > >>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > > >>>> - [2] https://issues.jboss.org/browse/AGPUSH-971 > > >>>> - [3] JIRA TO CREATE: to only store ALERT and not the full > payload > > >>>> - [4] JIRA TO CREATE: update doc regarding push message storage > and > > >>>> best practices > > >>>> > > >>>> > > >>>> -- > > >>>> Matthias Wessendorf > > >>>> > > >>>> blog: http://matthiaswessendorf.wordpress.com/ > > >>>> sessions: http://www.slideshare.net/mwessendorf > > >>>> twitter: http://twitter.com/mwessendorf > > >>>> > > >>> > > >>> > > >>> > > >>> -- > > >>> 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 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 > > >> > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/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/20150206/3ac66375/attachment-0001.html From matzew at apache.org Fri Feb 6 06:40:12 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 6 Feb 2015 12:40:12 +0100 Subject: [aerogear-dev] Storing the payload of the push notification In-Reply-To: <20150206105629.GE58032@abstractj.org> References: <54D3D91E.4000209@redhat.com> <20150206105629.GE58032@abstractj.org> Message-ID: On Fri, Feb 6, 2015 at 11:56 AM, Bruno Oliveira wrote: > On 2015-02-05, Matthias Wessendorf wrote: > > On Thu, Feb 5, 2015 at 9:57 PM, Summers Pittman > wrote: > > > > > On 02/05/2015 02:24 PM, Matthias Wessendorf wrote: > > > > > > While working on the doc for AGPUSH-1258, I found this in Apple's "iOS > > > Developer Program License Agreement": > > > > > > ... > > > Further, as a condition to using the APN, You agree not to transmit > > > sensitive personal or confidential information belonging to an > individual > > > (e.g. a social security number, financial account or transactional > > > information, or any information where the individual may have a > reasonable > > > expectation of secure transmission) as part of any Push Notification, > and > > > You agree to comply with any applicable notice or consent requirements > with > > > respect to any collection, transmission, maintenance, processing or > use of > > > an end user?s personal information. > > > ... > > > > > > That means, if an app-developer sends something like "Your blood > > > donation appointment is tomorrow" to a user of his mobile app, the > > > app-developer is breaking the Apple terms _and_ the law in a lot of > > > countries (at least in all EU countries) :-) > > > > > > What we have to remember is that large amounts of information in > aggregate > > > can become personally identifying even if any individual message is > not. > > > So the law in this case doesn't help since it is only the data in > context > > > which becomes personally identifying or protected. > > > > > > I don't think anyone is advocating for sending sensitive information > via > > > push, but what we are advocating is not putting a big target on our > (or our > > > user's) backs out of the gate by storing all of the messages by > default. > > > > > > > Let's make storing the 'alert' an option, which needs to be enabled, and > is > > turned off by default. > > > > This allows those that want to use the UPS for marekting reasons, to > > explicitly enable it. The enabling should be done with a proper* > > dialog/step inside of the setup-wizard that is planed for 1.1.x > > > > proper=> make it explicit that the UPS stores data, and link to privacy > > policy etc. the entire thing :-) > > +1 on privacy policy > > -1 on let people enable/disable for marketing reasons. > Wrong word - I mean analytics. See previous email with more details > > > > > > > Thoughts? > > > > > > > BTW. for Google I don't seem to find a similar paragraph, but IMO they > > > are not that thoughtful on privacy terms (compared to Apple). > > > > > > > > > Now, for our UPS guide (or documentation), I will add a few sentences > to > > > make it clear that our app-developers should NEVER submit sensitive > > > personal or confidential information with a push. > > > > > > Regarding a "Privacy Policy", I will also make clear what data of the > > > push we store, for analytic reasons. > > > > > > You'll see a PR during my Friday. > > > > > > > > > > > > > > > Greetings, > > > Matthias > > > > > > > > > > > > On Wed, Feb 4, 2015 at 2:53 PM, Matthias Wessendorf > > > > wrote: > > > > > >> I have created AGPUSH-1257 and AGPUSH-1258 > > >> > > >> On Fri, Jan 30, 2015 at 3:22 PM, Matthias Wessendorf < > matzew at apache.org> > > >> wrote: > > >> > > >>> Hi, > > >>> > > >>> earlier this week there was some discussion about storing the > payload of > > >>> the push notifications ([1]). > > >>> > > >>> Right now, we store some metrics (e.g. client that send the push, > number > > >>> of devices, deliveryStatus etc) *and* the entire content of push > > >>> notification. This includes custom key/value pairs, the name of the > sound > > >>> file or even the size of the badge. > > >>> > > >>> Is all of that, storing the entire push notification payload really > > >>> needed? *No!* > > >>> > > >>> What do we need, and why? > > >>> > > >>> For counting the number of sent pushes (over time), the metrics are > good > > >>> enough. We do *NOT* need any of the push content for that, that's > > >>> correct! > > >>> > > >>> But we want to do more on the 1.1.0 release. We want to introduce > some > > >>> analytic features, to give our app developers (our users) a better > > >>> understanding of their push usage (see [2]). > > >>> > > >>> In order to see details on how successful a push was (or not), we > need > > >>> to only store the value of the alert key: > > >>> > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png > > >>> > > >>> Ok, let's change that (see [3])! > > >>> > > >>> For our app developers, using the UPS to reach out to their mobile > app > > >>> users ("user engagement"), it's important to understand which push > was more > > >>> successful: > > >>> > > >>> - "Get 10% discount today" (sent on a Monday) > > >>> - "Our shop got new site, check it out and get 5% discount" (sent > on > > >>> a Friday) > > >>> > > >>> With the upcoming analytics we can help them to improve usage of > their > > >>> app. User interaction is very important to a successful mobile > application > > >>> and push is a key driver here! Our app developers want an app that is > > >>> actively used by their users (Nobody wants his app sitting on the > last page > > >>> of the device or, even worse, in a folder together with Apple-Maps). > > >>> Therefore it's critical for our app developers to understand the > relevance > > >>> of their push messages sent and how it impacts the usage of their > app. > > >>> That's why we do the analytics described in [2]. And, yes - only the > alert, > > >>> not the entire payload is needed for that. > > >>> >Privacy > > >>> > > >>> On the mentioned PR there was also some discussion about privacy > > >>> violations and stuff, when we store the content of the notification. > An > > >>> example where *sensitive* data was sent over push was given. > Something > > >>> like: "Dear Mr. Joe, your blood donation appointment was scheduled > for 3 > > >>> p.m" > > >>> > > >>> 1. This is not how push notifications are used for mobile apps. > Push > > >>> is to signal, not carry actual (sensitive) data around. > > >>> 2. In a lot of countries, at least almost all European countries, > > >>> you are not even allowed, by EU law, to give "data" to 3rd party > providers > > >>> (like the push-networks of Microsoft, Apple or Google). > > >>> > > >>> How does the actual (sensitive) data come to an app? > > >>> > > >>> As said above a push is used to signal/ping an app, to indicate that > > >>> there is real data for the mobile app user. In the background the > mobile > > >>> app tries to connect to the backend of the company, > running/maintaining the > > >>> mobile app. After the real data was fetched, "local notifcations" > are used > > >>> to give the user a visible notification, like "Dear Mr. Joe, your > blood > > >>> donation appointment was scheduled for 3 p.m", or simply "New > appointment > > >>> scheduled". > > >>> > > >>> If the app was a chat system (and not a blood donation app from the > Red > > >>> Cross), it would be the same: After a signal, the app connects to > "chat > > >>> server" and receives the actual chat message from there. A reply > would go > > >>> over the same "chat server" connection. None of this would go over a > 3rd > > >>> party push network provider like Google, Microsoft or Apple. > > >>> > > >>> What would we store from these silent notifications? > > >>> > > >>> Nothing, since there is no alert, we would just store the metrics > (e.g. > > >>> client that send the push, number of devices, deliveryStatus etc). > If the > > >>> signaling is actually done with an alert (e.g. alert:"you got a new > Chat > > >>> text" or "New appointment scheduled"), we would store that. > > >>> > > >>> I hope this helps a bit to understand what is stored and also why we > do > > >>> need a little bit of information. > > >>> > > >>> BTW. our documentation already says that push is used for signaling, > not > > >>> carrying actual data around, but based on this email I will update > it to > > >>> have explicit information on best practices. Also, the documentation > will > > >>> be clear about what (the alert only) is stored by the UPS, and why. > (see > > >>> [4]) > > >>> > > >>> Greetings, > > >>> > > >>> Matthias > > >>> > > >>> - [1] > > >>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 > > >>> - [2] https://issues.jboss.org/browse/AGPUSH-971 > > >>> - [3] JIRA TO CREATE: to only store ALERT and not the full payload > > >>> - [4] JIRA TO CREATE: update doc regarding push message storage > and > > >>> best practices > > >>> > > >>> > > >>> -- > > >>> Matthias Wessendorf > > >>> > > >>> blog: http://matthiaswessendorf.wordpress.com/ > > >>> sessions: http://www.slideshare.net/mwessendorf > > >>> twitter: http://twitter.com/mwessendorf > > >>> > > >> > > >> > > >> > > >> -- > > >> 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 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 > > > -- > > 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/20150206/7db0f7bd/attachment.html From daniel.bevenius at gmail.com Sun Feb 8 10:07:45 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 8 Feb 2015 16:07:45 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150209 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150208/3989d2bf/attachment-0001.html From supittma at redhat.com Sun Feb 8 23:14:36 2015 From: supittma at redhat.com (Summers Pittman) Date: Sun, 08 Feb 2015 23:14:36 -0500 Subject: [aerogear-dev] Android Sync Status Message-ID: <54D8342C.8080203@redhat.com> First the good news, I've refactored a lot of the xmpp-client code so now the sync client is correctly handled by an Android service. This gets around issues we were having earlier where the in-memory client would get GCed while the doc was in the background as well as some issues with loading documents when messages came in for the not currently being edited doc. Now the bad news, the past two weeks we've been focusing on using Google's two way messaging for being the backbone of sync on Android for alpha.1. One of the issues we knew about was the 4k message size limit in GCM and that after a POC phase we were going to have to address it. On Friday I noticed that the server was choking on messages much smaller than 4K. Turns out that 4K includes all of the metadata around the message in addition to the payload. I do not think the GCM bridge is a good tranport for alpha.1 and (if everyone agrees) will be focusing on the WebSocket based client. One thing that this brings up that I didn't see in the AGSYNC Jira (unless I'm blind) was how to manage the socket-connectivity interaction on the clients. Basically a protocol / pattern for how we manage the socket connections when the device gains and loses internet access or switches networks. (For instance we should probably disconnect and reconnect when the device leaves a cellular network and joins a Wifi network)This is separate from collision handling/detection which does have a Jira. If there isn't one (a connection handling Jira) should I make one? Happy Monday y'all, -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From daniel.bevenius at gmail.com Sun Feb 8 23:29:59 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 9 Feb 2015 05:29:59 +0100 Subject: [aerogear-dev] Android Sync Status In-Reply-To: <54D8342C.8080203@redhat.com> References: <54D8342C.8080203@redhat.com> Message-ID: >One thing that this brings up that I didn't see in the AGSYNC Jira (unless I'm blind) was how to manage the socket-connectivity interaction on the >clients. You are right there is no JIRAs for this and it would be great if you could create one (We should have one for iOS as well). Could this be a targeted for an alpha.2 release? On 9 February 2015 at 05:14, Summers Pittman wrote: > > First the good news, I've refactored a lot of the xmpp-client code so > now the sync client is correctly handled by an Android service. This > gets around issues we were having earlier where the in-memory client > would get GCed while the doc was in the background as well as some > issues with loading documents when messages came in for the not > currently being edited doc. > > Now the bad news, the past two weeks we've been focusing on using > Google's two way messaging for being the backbone of sync on Android for > alpha.1. One of the issues we knew about was the 4k message size limit > in GCM and that after a POC phase we were going to have to address it. > On Friday I noticed that the server was choking on messages much smaller > than 4K. Turns out that 4K includes all of the metadata around the > message in addition to the payload. I do not think the GCM bridge is a > good tranport for alpha.1 and (if everyone agrees) will be focusing on > the WebSocket based client. > > One thing that this brings up that I didn't see in the AGSYNC Jira > (unless I'm blind) was how to manage the socket-connectivity interaction > on the clients. Basically a protocol / pattern for how we manage the > socket connections when the device gains and loses internet access or > switches networks. (For instance we should probably disconnect and > reconnect when the device leaves a cellular network and joins a Wifi > network)This is separate from collision handling/detection which does > have a Jira. If there isn't one (a connection handling Jira) should I > make one? > > Happy Monday y'all, > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150209/cd072d64/attachment.html From corinnekrych at gmail.com Mon Feb 9 03:12:22 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 9 Feb 2015 09:12:22 +0100 Subject: [aerogear-dev] Android Sync Status In-Reply-To: References: <54D8342C.8080203@redhat.com> Message-ID: > On 09 Feb 2015, at 05:29, Daniel Bevenius wrote: > > >One thing that this brings up that I didn't see in the AGSYNC Jira (unless I'm blind) was how to manage the socket-connectivity interaction on the >clients. > You are right there is no JIRAs for this and it would be great if you could create one (We should have one for iOS as well). Could this be a targeted for an alpha.2 release? +1 for alpha2 > > > > On 9 February 2015 at 05:14, Summers Pittman wrote: > > First the good news, I've refactored a lot of the xmpp-client code so > now the sync client is correctly handled by an Android service. This > gets around issues we were having earlier where the in-memory client > would get GCed while the doc was in the background as well as some > issues with loading documents when messages came in for the not > currently being edited doc. > > Now the bad news, the past two weeks we've been focusing on using > Google's two way messaging for being the backbone of sync on Android for > alpha.1. One of the issues we knew about was the 4k message size limit > in GCM and that after a POC phase we were going to have to address it. > On Friday I noticed that the server was choking on messages much smaller > than 4K. Turns out that 4K includes all of the metadata around the > message in addition to the payload. I do not think the GCM bridge is a > good tranport for alpha.1 and (if everyone agrees) will be focusing on > the WebSocket based client. > > One thing that this brings up that I didn't see in the AGSYNC Jira > (unless I'm blind) was how to manage the socket-connectivity interaction > on the clients. Basically a protocol / pattern for how we manage the > socket connections when the device gains and loses internet access or > switches networks. (For instance we should probably disconnect and > reconnect when the device leaves a cellular network and joins a Wifi > network)This is separate from collision handling/detection which does > have a Jira. If there isn't one (a connection handling Jira) should I > make one? > > Happy Monday y'all, > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Mon Feb 9 05:15:12 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 9 Feb 2015 11:15:12 +0100 Subject: [aerogear-dev] Android Sync Status In-Reply-To: <54D8342C.8080203@redhat.com> References: <54D8342C.8080203@redhat.com> Message-ID: On Mon, Feb 9, 2015 at 5:14 AM, Summers Pittman wrote: > > First the good news, I've refactored a lot of the xmpp-client code so > now the sync client is correctly handled by an Android service. This > gets around issues we were having earlier where the in-memory client > would get GCed while the doc was in the background as well as some > issues with loading documents when messages came in for the not > currently being edited doc. > > Now the bad news, the past two weeks we've been focusing on using > Google's two way messaging for being the backbone of sync on Android for > alpha.1. One of the issues we knew about was the 4k message size limit > in GCM and that after a POC phase we were going to have to address it. > On Friday I noticed that the server was choking on messages much smaller > than 4K. Turns out that 4K includes all of the metadata around the > message in addition to the payload. I do not think the GCM bridge is a > good tranport for alpha.1 and (if everyone agrees) will be focusing on > the WebSocket based client. > +9001 on a solid WebSocket client library for Android. Especially for privacy our SYNC module should not rely on a 3rd party provider, like GCM, to sync the user's data (either entire documents or even patches). For the integration of GCM/XMPP, IMO the best usage here is to just signal (or notify) the mobile app (e.g. while running in the background without a persistent connection to the Sync-Server) there is "new data" is available. The app could than (while still in the background) perform a connection to the users' Sync-Server and apply the data (e.g. patch), that was delivered directly from the users' Sync-Server instance. This way the users content is not exchanged over a 3rd party provider, like Google > > One thing that this brings up that I didn't see in the AGSYNC Jira > (unless I'm blind) was how to manage the socket-connectivity interaction > on the clients. Basically a protocol / pattern for how we manage the > socket connections when the device gains and loses internet access or > switches networks. (For instance we should probably disconnect and > reconnect when the device leaves a cellular network and joins a Wifi > network)This is separate from collision handling/detection which does > have a Jira. If there isn't one (a connection handling Jira) should I > make one? > Sounds like a good idea, to have that for the next iteration of our SYNC effort > > Happy Monday y'all, > > -- > 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/20150209/b316b409/attachment.html From lholmqui at redhat.com Mon Feb 9 08:51:15 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 9 Feb 2015 08:51:15 -0500 Subject: [aerogear-dev] Android Sync Status In-Reply-To: References: <54D8342C.8080203@redhat.com> Message-ID: <3102358A-E5A6-47C1-AE24-A5CF1F931CD4@redhat.com> > On Feb 8, 2015, at 11:29 PM, Daniel Bevenius wrote: > > >One thing that this brings up that I didn't see in the AGSYNC Jira (unless I'm blind) was how to manage the socket-connectivity interaction on the >clients. > You are right there is no JIRAs for this and it would be great if you could create one (We should have one for iOS as well). Could this be a targeted for an alpha.2 release? Don;t forget to create one for JS too :) > > > > On 9 February 2015 at 05:14, Summers Pittman > wrote: > > First the good news, I've refactored a lot of the xmpp-client code so > now the sync client is correctly handled by an Android service. This > gets around issues we were having earlier where the in-memory client > would get GCed while the doc was in the background as well as some > issues with loading documents when messages came in for the not > currently being edited doc. > > Now the bad news, the past two weeks we've been focusing on using > Google's two way messaging for being the backbone of sync on Android for > alpha.1. One of the issues we knew about was the 4k message size limit > in GCM and that after a POC phase we were going to have to address it. > On Friday I noticed that the server was choking on messages much smaller > than 4K. Turns out that 4K includes all of the metadata around the > message in addition to the payload. I do not think the GCM bridge is a > good tranport for alpha.1 and (if everyone agrees) will be focusing on > the WebSocket based client. > > One thing that this brings up that I didn't see in the AGSYNC Jira > (unless I'm blind) was how to manage the socket-connectivity interaction > on the clients. Basically a protocol / pattern for how we manage the > socket connections when the device gains and loses internet access or > switches networks. (For instance we should probably disconnect and > reconnect when the device leaves a cellular network and joins a Wifi > network)This is separate from collision handling/detection which does > have a Jira. If there isn't one (a connection handling Jira) should I > make one? > > Happy Monday y'all, > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150209/d1684a28/attachment-0001.html From supittma at redhat.com Mon Feb 9 09:26:34 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 09 Feb 2015 09:26:34 -0500 Subject: [aerogear-dev] Android Sync Status In-Reply-To: References: <54D8342C.8080203@redhat.com> Message-ID: <54D8C39A.50704@redhat.com> On 02/09/2015 05:15 AM, Matthias Wessendorf wrote: > > > On Mon, Feb 9, 2015 at 5:14 AM, Summers Pittman > wrote: > > > First the good news, I've refactored a lot of the xmpp-client code so > now the sync client is correctly handled by an Android service. This > gets around issues we were having earlier where the in-memory client > would get GCed while the doc was in the background as well as some > issues with loading documents when messages came in for the not > currently being edited doc. > > Now the bad news, the past two weeks we've been focusing on using > Google's two way messaging for being the backbone of sync on > Android for > alpha.1. One of the issues we knew about was the 4k message size > limit > in GCM and that after a POC phase we were going to have to address it. > On Friday I noticed that the server was choking on messages much > smaller > than 4K. Turns out that 4K includes all of the metadata around the > message in addition to the payload. I do not think the GCM bridge > is a > good tranport for alpha.1 and (if everyone agrees) will be focusing on > the WebSocket based client. > > > +9001 on a solid WebSocket client library for Android. > > Especially for privacy our SYNC module should not rely on a 3rd party > provider, like GCM, to sync the user's data (either entire documents > or even patches). > > For the integration of GCM/XMPP, IMO the best usage here is to just > signal (or notify) the mobile app (e.g. while running in the > background without a persistent connection to the Sync-Server) there > is "new data" is available. The app could than (while still in the > background) perform a connection to the users' Sync-Server and apply > the data (e.g. patch), that was delivered directly from the users' > Sync-Server instance. This way the users content is not exchanged over > a 3rd party provider, like Google > > > One thing that this brings up that I didn't see in the AGSYNC Jira > (unless I'm blind) was how to manage the socket-connectivity > interaction > on the clients. Basically a protocol / pattern for how we manage the > socket connections when the device gains and loses internet access or > switches networks. (For instance we should probably disconnect and > reconnect when the device leaves a cellular network and joins a Wifi > network)This is separate from collision handling/detection which does > have a Jira. If there isn't one (a connection handling Jira) should I > make one? > > > Sounds like a good idea, to have that for the next iteration of our > SYNC effort And here it is https://issues.jboss.org/browse/AGSYNC-36 > > > Happy Monday y'all, > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150209/e4c96b5c/attachment.html From cvasilak at gmail.com Mon Feb 9 10:12:22 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 9 Feb 2015 17:12:22 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: <5423DC53-9722-4AB3-812E-1C36B0948039@gmail.com> fyi, meeting minutes: Meeting ended Mon Feb 9 15:11:09 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-09-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-09-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-09-15.00.log.html > On Feb 8, 2015, at 5:07 PM, Daniel Bevenius wrote: > > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20150209 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150209/7e4ef971/attachment.html From matzew at apache.org Tue Feb 10 06:00:53 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 10 Feb 2015 12:00:53 +0100 Subject: [aerogear-dev] Question on UPS dockerfile Message-ID: Hello, I am wondering if others noticed the same as well: 1) I started the vm (boot2docker start) and also did the exports, from above printout 2) Next, running "docker run -it -p 8443:8443 aerogear/wildfly" On the log I saw the WildFly booting up, but nothing for UPS/Keycloak on the log visible. 3) Now, I cloned the repo, executed the build in "dockerfiles/wildfly/unifiedpush-wildfly" (via "docker build -t aerogear/wildfly .") 4) Next I tried again to get it running "docker run -it -p 8443:8443 aerogear/wildfly" 5) The WildFly console now shows the logs that you get when you deply UPS - Now I could access "https://192.168.59.103:8443/ag-push" (after adding a security exception) Cool! Now I did stop the VM (boot2docker stop) On a new terminal, I started the vm (boot2docker start), performed the suggested exports, and did run "docker run -it -p 8443:8443 aerogear/wildfly" -> this time I got the UPS in the logs as well - wondering: is that related to my previous build ? or was there just something wrong with my "first" execute of "docker run -it -p 8443:8443 aerogear/wildfly" ? 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/20150210/475c6ebe/attachment.html From bruno at abstractj.org Tue Feb 10 09:35:20 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 10 Feb 2015 12:35:20 -0200 Subject: [aerogear-dev] AGSEC components and versioning Message-ID: <20150210143520.GA84123@abstractj.org> Good morning, I'm doing some housekeeping on AGSEC and would like to know what works best for you. For the further releases and for the sake of sanity at the roadmap, I'm separating the security releases by component: - Crypto - Sync - OTP - push - OAuth2 - offline They are pretty much "virtual" because it project follows its own release process and I just want to group by feature. For versioning what would be better for you: 1. Versioning from scratch which pretty much means each component starts with 0.0.1 and we increase accordingly with the progress. 2. Follow the Security roadmap versioning (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which means each component starting with 1.4.0 and increasing each one independesing. 3. Follow each project versioning which means: - sync: follows the same versioning for the sync server - push: same versioning from the push server Note: the idea would fail badly for OAuth2, Crypto and OTP I'd vote for 2 to prevent confusion. -- abstractj PGP: 0x84DC9914 From daniel.bevenius at gmail.com Tue Feb 10 10:35:30 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Tue, 10 Feb 2015 16:35:30 +0100 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: <20150210143520.GA84123@abstractj.org> References: <20150210143520.GA84123@abstractj.org> Message-ID: +1 for option 2. Starting with the current 1.4.0 version for each component. On 10 February 2015 at 15:35, Bruno Oliveira wrote: > Good morning, I'm doing some housekeeping on AGSEC and would like to > know what works best for you. > > For the further releases and for the sake of sanity at the roadmap, I'm > separating the security releases by component: > > - Crypto > - Sync > - OTP > - push > - OAuth2 > - offline > > They are pretty much "virtual" because it project follows its own > release process and I just want to group by feature. For versioning what > would be better for you: > > 1. Versioning from scratch which pretty much means each component starts > with 0.0.1 and we increase accordingly with the progress. > > 2. Follow the Security roadmap versioning > (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which > means each component starting with 1.4.0 and increasing each one > independesing. > > 3. Follow each project versioning which means: > - sync: follows the same versioning for the sync server > - push: same versioning from the push server > Note: the idea would fail badly for OAuth2, Crypto and OTP > > I'd vote for 2 to prevent confusion. > > -- > > 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/20150210/3b9167bb/attachment-0001.html From supittma at redhat.com Tue Feb 10 10:16:42 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 10 Feb 2015 10:16:42 -0500 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: <20150210143520.GA84123@abstractj.org> References: <20150210143520.GA84123@abstractj.org> Message-ID: <54DA20DA.8050402@redhat.com> On 02/10/2015 09:35 AM, Bruno Oliveira wrote: > Good morning, I'm doing some housekeeping on AGSEC and would like to > know what works best for you. > > For the further releases and for the sake of sanity at the roadmap, I'm > separating the security releases by component: > > - Crypto > - Sync > - OTP > - push > - OAuth2 > - offline > > They are pretty much "virtual" because it project follows its own > release process and I just want to group by feature. For versioning what > would be better for you: > > 1. Versioning from scratch which pretty much means each component starts > with 0.0.1 and we increase accordingly with the progress. > > 2. Follow the Security roadmap versioning > (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which > means each component starting with 1.4.0 and increasing each one > independesing. > > 3. Follow each project versioning which means: > - sync: follows the same versioning for the sync server > - push: same versioning from the push server > Note: the idea would fail badly for OAuth2, Crypto and OTP > > I'd vote for 2 to prevent confusion. Could you give examples of what each of your suggestions would look like in terms of the project versions(AGIOS, AGDROID, etc) and the security version(AGSEC)? I'm not sure what the consequences of each choice are. > > -- > > 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 Tue Feb 10 11:28:30 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 10 Feb 2015 14:28:30 -0200 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: <54DA20DA.8050402@redhat.com> References: <20150210143520.GA84123@abstractj.org> <54DA20DA.8050402@redhat.com> Message-ID: <20150210162830.GB84123@abstractj.org> On 2015-02-10, Summers Pittman wrote: > On 02/10/2015 09:35 AM, Bruno Oliveira wrote: > > Good morning, I'm doing some housekeeping on AGSEC and would like to > > know what works best for you. > > > > For the further releases and for the sake of sanity at the roadmap, I'm > > separating the security releases by component: > > > > - Crypto > > - Sync > > - OTP > > - push > > - OAuth2 > > - offline > > > > They are pretty much "virtual" because it project follows its own > > release process and I just want to group by feature. For versioning what > > would be better for you: > > > > 1. Versioning from scratch which pretty much means each component starts > > with 0.0.1 and we increase accordingly with the progress. > > > > 2. Follow the Security roadmap versioning > > (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which > > means each component starting with 1.4.0 and increasing each one > > independesing. > > > > 3. Follow each project versioning which means: > > - sync: follows the same versioning for the sync server > > - push: same versioning from the push server > > Note: the idea would fail badly for OAuth2, Crypto and OTP > > > > I'd vote for 2 to prevent confusion. > Could you give examples of what each of your suggestions would look like > in terms of the project versions(AGIOS, AGDROID, etc) and the security > version(AGSEC)? I'm not sure what the consequences of each choice are. There are no consequences to other projects, because each project follows its own versioning and AGSEC will always respect it. So when you read at the roadmap OAuth2 1.4, it beans a group of features delivered from: - AGDROID 2.0.x - AGIOS 1.x.x The versioning on AGSEC is pretty much to keep our sanity to have an idea about which features we've been planning and when, for security. Does it make sense for you? > > > > -- > > > > 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 matzew at apache.org Tue Feb 10 12:04:34 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 10 Feb 2015 18:04:34 +0100 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: <20150210162830.GB84123@abstractj.org> References: <20150210143520.GA84123@abstractj.org> <54DA20DA.8050402@redhat.com> <20150210162830.GB84123@abstractj.org> Message-ID: On Tue, Feb 10, 2015 at 5:28 PM, Bruno Oliveira wrote: > On 2015-02-10, Summers Pittman wrote: > > On 02/10/2015 09:35 AM, Bruno Oliveira wrote: > > > Good morning, I'm doing some housekeeping on AGSEC and would like to > > > know what works best for you. > > > > > > For the further releases and for the sake of sanity at the roadmap, I'm > > > separating the security releases by component: > > > > > > - Crypto > > > - Sync > > > - OTP > > > - push > > > - OAuth2 > > > - offline > > > > > > They are pretty much "virtual" because it project follows its own > > > release process and I just want to group by feature. For versioning > what > > > would be better for you: > > > > > > 1. Versioning from scratch which pretty much means each component > starts > > > with 0.0.1 and we increase accordingly with the progress. > > > > > > 2. Follow the Security roadmap versioning > > > (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). > Which > > > means each component starting with 1.4.0 and increasing each one > > > independesing. > > > > > > 3. Follow each project versioning which means: > > > - sync: follows the same versioning for the sync server > > > - push: same versioning from the push server > > > Note: the idea would fail badly for OAuth2, Crypto and OTP > > > > > > I'd vote for 2 to prevent confusion. > > Could you give examples of what each of your suggestions would look like > > in terms of the project versions(AGIOS, AGDROID, etc) and the security > > version(AGSEC)? I'm not sure what the consequences of each choice are. > > There are no consequences to other projects, because each project > follows its own versioning and AGSEC will always respect it. > > So when you read at the roadmap OAuth2 1.4, it beans a group of features > delivered from: > > - AGDROID 2.0.x > - AGIOS 1.x.x > > The versioning on AGSEC is pretty much to keep our sanity to have an > idea about which features we've been planning and when, for security. > > Does it make sense for you? > yes, basically a list of epics/jiras with the (in this case) OAuth2 items, linked to their platform specific implementation JIRAs > > > > > > > > -- > > > > > > 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 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150210/81dc12ba/attachment.html From daniel at passos.me Tue Feb 10 12:51:44 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 10 Feb 2015 15:51:44 -0200 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: References: <20150210143520.GA84123@abstractj.org> <54DA20DA.8050402@redhat.com> <20150210162830.GB84123@abstractj.org> Message-ID: +1 for option 2. On Tue, Feb 10, 2015 at 3:04 PM, Matthias Wessendorf wrote: > > > On Tue, Feb 10, 2015 at 5:28 PM, Bruno Oliveira > wrote: > >> On 2015-02-10, Summers Pittman wrote: >> > On 02/10/2015 09:35 AM, Bruno Oliveira wrote: >> > > Good morning, I'm doing some housekeeping on AGSEC and would like to >> > > know what works best for you. >> > > >> > > For the further releases and for the sake of sanity at the roadmap, >> I'm >> > > separating the security releases by component: >> > > >> > > - Crypto >> > > - Sync >> > > - OTP >> > > - push >> > > - OAuth2 >> > > - offline >> > > >> > > They are pretty much "virtual" because it project follows its own >> > > release process and I just want to group by feature. For versioning >> what >> > > would be better for you: >> > > >> > > 1. Versioning from scratch which pretty much means each component >> starts >> > > with 0.0.1 and we increase accordingly with the progress. >> > > >> > > 2. Follow the Security roadmap versioning >> > > (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). >> Which >> > > means each component starting with 1.4.0 and increasing each one >> > > independesing. >> > > >> > > 3. Follow each project versioning which means: >> > > - sync: follows the same versioning for the sync server >> > > - push: same versioning from the push server >> > > Note: the idea would fail badly for OAuth2, Crypto and OTP >> > > >> > > I'd vote for 2 to prevent confusion. >> > Could you give examples of what each of your suggestions would look like >> > in terms of the project versions(AGIOS, AGDROID, etc) and the security >> > version(AGSEC)? I'm not sure what the consequences of each choice are. >> >> There are no consequences to other projects, because each project >> follows its own versioning and AGSEC will always respect it. >> >> So when you read at the roadmap OAuth2 1.4, it beans a group of features >> delivered from: >> >> - AGDROID 2.0.x >> - AGIOS 1.x.x >> >> The versioning on AGSEC is pretty much to keep our sanity to have an >> idea about which features we've been planning and when, for security. >> >> Does it make sense for you? >> > > > yes, basically a list of epics/jiras with the (in this case) OAuth2 items, > linked to their platform specific implementation JIRAs > > >> >> >> > > >> > > -- >> > > >> > > 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 >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150210/0ea4c337/attachment-0001.html From supittma at redhat.com Tue Feb 10 13:57:16 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 10 Feb 2015 13:57:16 -0500 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: <20150210162830.GB84123@abstractj.org> References: <20150210143520.GA84123@abstractj.org> <54DA20DA.8050402@redhat.com> <20150210162830.GB84123@abstractj.org> Message-ID: <54DA548C.1070408@redhat.com> On 02/10/2015 11:28 AM, Bruno Oliveira wrote: > On 2015-02-10, Summers Pittman wrote: >> On 02/10/2015 09:35 AM, Bruno Oliveira wrote: >>> Good morning, I'm doing some housekeeping on AGSEC and would like to >>> know what works best for you. >>> >>> For the further releases and for the sake of sanity at the roadmap, I'm >>> separating the security releases by component: >>> >>> - Crypto >>> - Sync >>> - OTP >>> - push >>> - OAuth2 >>> - offline >>> >>> They are pretty much "virtual" because it project follows its own >>> release process and I just want to group by feature. For versioning what >>> would be better for you: >>> >>> 1. Versioning from scratch which pretty much means each component starts >>> with 0.0.1 and we increase accordingly with the progress. >>> >>> 2. Follow the Security roadmap versioning >>> (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which >>> means each component starting with 1.4.0 and increasing each one >>> independesing. >>> >>> 3. Follow each project versioning which means: >>> - sync: follows the same versioning for the sync server >>> - push: same versioning from the push server >>> Note: the idea would fail badly for OAuth2, Crypto and OTP >>> >>> I'd vote for 2 to prevent confusion. >> Could you give examples of what each of your suggestions would look like >> in terms of the project versions(AGIOS, AGDROID, etc) and the security >> version(AGSEC)? I'm not sure what the consequences of each choice are. > There are no consequences to other projects, because each project > follows its own versioning and AGSEC will always respect it. > > So when you read at the roadmap OAuth2 1.4, it beans a group of features > delivered from: > > - AGDROID 2.0.x > - AGIOS 1.x.x > > The versioning on AGSEC is pretty much to keep our sanity to have an > idea about which features we've been planning and when, for security. > > Does it make sense for you? Yes. +1 to #2 > >>> -- >>> >>> 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 > _______________________________________________ > 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 cvasilak at gmail.com Wed Feb 11 04:06:09 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 11 Feb 2015 11:06:09 +0200 Subject: [aerogear-dev] AGSEC components and versioning In-Reply-To: <20150210143520.GA84123@abstractj.org> References: <20150210143520.GA84123@abstractj.org> Message-ID: +1 for option #2 - Christos > On Feb 10, 2015, at 4:35 PM, Bruno Oliveira wrote: > > Good morning, I'm doing some housekeeping on AGSEC and would like to > know what works best for you. > > For the further releases and for the sake of sanity at the roadmap, I'm > separating the security releases by component: > > - Crypto > - Sync > - OTP > - push > - OAuth2 > - offline > > They are pretty much "virtual" because it project follows its own > release process and I just want to group by feature. For versioning what > would be better for you: > > 1. Versioning from scratch which pretty much means each component starts > with 0.0.1 and we increase accordingly with the progress. > > 2. Follow the Security roadmap versioning > (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which > means each component starting with 1.4.0 and increasing each one > independesing. > > 3. Follow each project versioning which means: > - sync: follows the same versioning for the sync server > - push: same versioning from the push server > Note: the idea would fail badly for OAuth2, Crypto and OTP > > I'd vote for 2 to prevent confusion. > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From qmx at qmx.me Thu Feb 12 20:02:18 2015 From: qmx at qmx.me (Douglas Campos) Date: Thu, 12 Feb 2015 23:02:18 -0200 Subject: [aerogear-dev] UPS bug - am I crazy? Message-ID: <20150213010218.GB65532@darkstar.local> Howdy! I was doing the migration work and found out something funny: For Installations, we have `installation.setDeviceType()`, but during Installation `persist()`, the DeviceTokenValidator is called, which in turn looks for a Variant. So after fiddling with some orm settings suddenly a bunch of tests started to break, which led me to this snippet[1]: // disabled Installation android3 = new Installation(); android3.setAlias("foo at bar.org"); android3.setDeviceToken("543234234890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"); android3.setDeviceType("Android Tablet"); android3.setEnabled(false); installationDao.create(android3); See, our tests are creating an installation without associating it to a variant first, then it blows up here[2]: // DeviceTokenValidator#isValid() if (installation.getVariant() == null || installation.getVariant().getType() == null || deviceToken == null) { return false; } This is smelling like a bug to me - kinda like the validator wasn't actually running during tests. Am I crazy? [1]:https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/InstallationDaoTest.java#L133-L140 [2]:https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L60 -- qmx From edewit at redhat.com Fri Feb 13 02:17:03 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 13 Feb 2015 08:17:03 +0100 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: <20150213010218.GB65532@darkstar.local> References: <20150213010218.GB65532@darkstar.local> Message-ID: Hi, Don?t know if it?s really a bug, but in order to validate that a device token is valid we need to know what variant type it belongs to. It makes no sense for a installation to be persisted without a Variant, because then you cannot send any messages to that device. So if you try to persist a installation without a variant the device token is not valid seems to be to be a valid statement. This was introduced when we added cordova, there it?s easy to make a mistake and have the wrong variantID / secret in your settings. Resulting in a iOS device registering under an android variant. With the deviceToken validation this can no longer happen. Does this make sense? Cheers, Erik Jan On 13 Feb,2015, at 2:02 , Douglas Campos wrote: > Howdy! > > I was doing the migration work and found out something funny: > > For Installations, we have `installation.setDeviceType()`, but during > Installation `persist()`, the DeviceTokenValidator is called, which in > turn looks for a Variant. > > So after fiddling with some orm settings suddenly a bunch of tests > started to break, which led me to this snippet[1]: > > // disabled > Installation android3 = new Installation(); > android3.setAlias("foo at bar.org"); > android3.setDeviceToken("543234234890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"); > android3.setDeviceType("Android Tablet"); > android3.setEnabled(false); > > installationDao.create(android3); > > See, our tests are creating an installation without associating it to a > variant first, then it blows up here[2]: > > // DeviceTokenValidator#isValid() > if (installation.getVariant() == null || installation.getVariant().getType() == null || deviceToken == null) { > return false; > } > > This is smelling like a bug to me - kinda like the validator wasn't > actually running during tests. Am I crazy? > > [1]:https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/InstallationDaoTest.java#L133-L140 > [2]:https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L60 > > -- > qmx > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From vivek.pandey at pinelabs.com Fri Feb 13 02:31:47 2015 From: vivek.pandey at pinelabs.com (Vivek Pandey) Date: Fri, 13 Feb 2015 13:01:47 +0530 Subject: [aerogear-dev] UPS 1.0.3? Message-ID: <003901d0475f$20038070$600a8150$@pinelabs.com> Hello team, Is UPS 1.0.3 release still in works ? I have a prod deployment of UPS 1.0.2 and was planning to upgrade to 1.0.3 (so that I don't have to migrate the db). 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/20150213/c97fa313/attachment.html From scm.blanc at gmail.com Fri Feb 13 05:17:49 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 13 Feb 2015 11:17:49 +0100 Subject: [aerogear-dev] UPS 1.0.3? In-Reply-To: <003901d0475f$20038070$600a8150$@pinelabs.com> References: <003901d0475f$20038070$600a8150$@pinelabs.com> Message-ID: Hi Vivek, Yes, the 1.0.3 release is still in the work. We have some delay due to some migration issues. You can have an overview here : https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel Regards, Sebi On Fri, Feb 13, 2015 at 8:31 AM, Vivek Pandey wrote: > Hello team, > > > > Is UPS 1.0.3 release still in works ? I have a prod deployment of UPS > 1.0.2 and was planning to upgrade to 1.0.3 (so that I don?t have to migrate > the db). > > > > Thanks, > > Vivek > > ------------------------------ > This message may contain privileged and confidential information and is > solely for the use of intended recipient. The views expressed in this email > are those of the sender and not of Pine Labs. The recipient should check > this email and attachments for the presence of viruses / malwares etc. Pine > Labs accepts no liability for any damage caused by any virus transmitted by > this email. Pine Labs may monitor and record all emails. > ------------------------------ > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150213/940b6b4b/attachment.html From matzew at apache.org Fri Feb 13 06:01:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 13 Feb 2015 12:01:07 +0100 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: References: <20150213010218.GB65532@darkstar.local> Message-ID: Hi, I agree w/ Erik - however, I think the test has a bug, if the installations are not directly associated with a Variant. Should be easy to fix. BTW. qmx, you mentioned the "setDeviceType()", but that is really just plain text metadata, like here: https://github.com/aerogear/aerogear-push-helloworld/blob/master/ios/HelloWorld/AGAppDelegate.m#L106 The validator is triggered by the actual variant type (installation .getVariant().getType()) -Matthias On Fri, Feb 13, 2015 at 8:17 AM, Erik Jan de Wit wrote: > Hi, > > Don?t know if it?s really a bug, but in order to validate that a device > token is valid we need to know what variant type it belongs to. It makes no > sense for a installation to be persisted without a Variant, because then > you cannot send any messages to that device. So if you try to persist a > installation without a variant the device token is not valid seems to be to > be a valid statement. > > This was introduced when we added cordova, there it?s easy to make a > mistake and have the wrong variantID / secret in your settings. Resulting > in a iOS device registering under an android variant. With the deviceToken > validation this can no longer happen. > > Does this make sense? > > Cheers, > Erik Jan > > On 13 Feb,2015, at 2:02 , Douglas Campos wrote: > > > Howdy! > > > > I was doing the migration work and found out something funny: > > > > For Installations, we have `installation.setDeviceType()`, but during > > Installation `persist()`, the DeviceTokenValidator is called, which in > > turn looks for a Variant. > > > > So after fiddling with some orm settings suddenly a bunch of tests > > started to break, which led me to this snippet[1]: > > > > // disabled > > Installation android3 = new Installation(); > > android3.setAlias("foo at bar.org"); > > > android3.setDeviceToken("543234234890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"); > > android3.setDeviceType("Android Tablet"); > > android3.setEnabled(false); > > > > installationDao.create(android3); > > > > See, our tests are creating an installation without associating it to a > > variant first, then it blows up here[2]: > > > > // DeviceTokenValidator#isValid() > > if (installation.getVariant() == null || > installation.getVariant().getType() == null || deviceToken == null) { > > return false; > > } > > > > This is smelling like a bug to me - kinda like the validator wasn't > > actually running during tests. Am I crazy? > > > > [1]: > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/InstallationDaoTest.java#L133-L140 > > [2]: > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L60 > > > > -- > > qmx > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150213/decee81d/attachment-0001.html From qmx at qmx.me Fri Feb 13 07:02:40 2015 From: qmx at qmx.me (Douglas Campos) Date: Fri, 13 Feb 2015 10:02:40 -0200 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: References: <20150213010218.GB65532@darkstar.local> Message-ID: <20150213120240.GF65532@darkstar.local> On Fri, Feb 13, 2015 at 12:01:07PM +0100, Matthias Wessendorf wrote: > Hi, > > I agree w/ Erik - however, I think the test has a bug, if the installations > are not directly associated with a Variant. Should be easy to fix. That's my point - this test should never pass - hence the "bug" suspicion. > > BTW. qmx, you mentioned the "setDeviceType()", but that is really just > plain text metadata, like here: > https://github.com/aerogear/aerogear-push-helloworld/blob/master/ios/HelloWorld/AGAppDelegate.m#L106 > > > The validator is triggered by the actual variant type (installation > .getVariant().getType()) > > -Matthias > > > > On Fri, Feb 13, 2015 at 8:17 AM, Erik Jan de Wit wrote: > > > Hi, > > > > Don?t know if it?s really a bug, but in order to validate that a device > > token is valid we need to know what variant type it belongs to. It makes no > > sense for a installation to be persisted without a Variant, because then > > you cannot send any messages to that device. So if you try to persist a > > installation without a variant the device token is not valid seems to be to > > be a valid statement. > > > > This was introduced when we added cordova, there it?s easy to make a > > mistake and have the wrong variantID / secret in your settings. Resulting > > in a iOS device registering under an android variant. With the deviceToken > > validation this can no longer happen. > > > > Does this make sense? > > > > Cheers, > > Erik Jan > > > > On 13 Feb,2015, at 2:02 , Douglas Campos wrote: > > > > > Howdy! > > > > > > I was doing the migration work and found out something funny: > > > > > > For Installations, we have `installation.setDeviceType()`, but during > > > Installation `persist()`, the DeviceTokenValidator is called, which in > > > turn looks for a Variant. > > > > > > So after fiddling with some orm settings suddenly a bunch of tests > > > started to break, which led me to this snippet[1]: > > > > > > // disabled > > > Installation android3 = new Installation(); > > > android3.setAlias("foo at bar.org"); > > > > > android3.setDeviceToken("543234234890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"); > > > android3.setDeviceType("Android Tablet"); > > > android3.setEnabled(false); > > > > > > installationDao.create(android3); > > > > > > See, our tests are creating an installation without associating it to a > > > variant first, then it blows up here[2]: > > > > > > // DeviceTokenValidator#isValid() > > > if (installation.getVariant() == null || > > installation.getVariant().getType() == null || deviceToken == null) { > > > return false; > > > } > > > > > > This is smelling like a bug to me - kinda like the validator wasn't > > > actually running during tests. Am I crazy? > > > > > > [1]: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/InstallationDaoTest.java#L133-L140 > > > [2]: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L60 > > > > > > -- > > > qmx > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- qmx From matzew at apache.org Fri Feb 13 07:17:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 13 Feb 2015 13:17:37 +0100 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: <20150213120240.GF65532@darkstar.local> References: <20150213010218.GB65532@darkstar.local> <20150213120240.GF65532@darkstar.local> Message-ID: yes, that's a bug in the test On Friday, February 13, 2015, Douglas Campos wrote: > On Fri, Feb 13, 2015 at 12:01:07PM +0100, Matthias Wessendorf wrote: > > Hi, > > > > I agree w/ Erik - however, I think the test has a bug, if the > installations > > are not directly associated with a Variant. Should be easy to fix. > That's my point - this test should never pass - hence the "bug" > suspicion. > > > > > BTW. qmx, you mentioned the "setDeviceType()", but that is really just > > plain text metadata, like here: > > > https://github.com/aerogear/aerogear-push-helloworld/blob/master/ios/HelloWorld/AGAppDelegate.m#L106 > > > > > > The validator is triggered by the actual variant type (installation > > .getVariant().getType()) > > > > -Matthias > > > > > > > > On Fri, Feb 13, 2015 at 8:17 AM, Erik Jan de Wit > wrote: > > > > > Hi, > > > > > > Don?t know if it?s really a bug, but in order to validate that a device > > > token is valid we need to know what variant type it belongs to. It > makes no > > > sense for a installation to be persisted without a Variant, because > then > > > you cannot send any messages to that device. So if you try to persist a > > > installation without a variant the device token is not valid seems to > be to > > > be a valid statement. > > > > > > This was introduced when we added cordova, there it?s easy to make a > > > mistake and have the wrong variantID / secret in your settings. > Resulting > > > in a iOS device registering under an android variant. With the > deviceToken > > > validation this can no longer happen. > > > > > > Does this make sense? > > > > > > Cheers, > > > Erik Jan > > > > > > On 13 Feb,2015, at 2:02 , Douglas Campos > > wrote: > > > > > > > Howdy! > > > > > > > > I was doing the migration work and found out something funny: > > > > > > > > For Installations, we have `installation.setDeviceType()`, but during > > > > Installation `persist()`, the DeviceTokenValidator is called, which > in > > > > turn looks for a Variant. > > > > > > > > So after fiddling with some orm settings suddenly a bunch of tests > > > > started to break, which led me to this snippet[1]: > > > > > > > > // disabled > > > > Installation android3 = new Installation(); > > > > android3.setAlias("foo at bar.org "); > > > > > > > > android3.setDeviceToken("543234234890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"); > > > > android3.setDeviceType("Android Tablet"); > > > > android3.setEnabled(false); > > > > > > > > installationDao.create(android3); > > > > > > > > See, our tests are creating an installation without associating it > to a > > > > variant first, then it blows up here[2]: > > > > > > > > // DeviceTokenValidator#isValid() > > > > if (installation.getVariant() == null || > > > installation.getVariant().getType() == null || deviceToken == null) { > > > > return false; > > > > } > > > > > > > > This is smelling like a bug to me - kinda like the validator wasn't > > > > actually running during tests. Am I crazy? > > > > > > > > [1]: > > > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/InstallationDaoTest.java#L133-L140 > > > > [2]: > > > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L60 > > > > > > > > -- > > > > qmx > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > qmx > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150213/7d4b0282/attachment.html From daniel.bevenius at gmail.com Sun Feb 15 07:27:21 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 15 Feb 2015 13:27:21 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150216 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150215/6a6cf94a/attachment.html From corinnekrych at gmail.com Mon Feb 16 04:06:43 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 16 Feb 2015 10:06:43 +0100 Subject: [aerogear-dev] iOS meeting on Tuesday Message-ID: Hello all Our next iOS meeting will be on Tuesday 4pm (+1 GMT), here is the agenda: http://oksoclap.com/p/aerogear_ios_meeting_17_february_2014 Main focus on 2.2 remaining tickets. ++ Corinne From cvasilak at gmail.com Mon Feb 16 10:12:33 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 16 Feb 2015 17:12:33 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: <66974972-948B-4F2A-858A-CD7DB1A8E8B3@gmail.com> fyi, meeting minutes: Meeting ended Mon Feb 16 15:10:31 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-16-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-16-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-16-15.00.log.html > On Feb 15, 2015, at 2:27 PM, Daniel Bevenius wrote: > > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20150216 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150216/67b728cc/attachment-0001.html From cvasilak at gmail.com Tue Feb 17 10:08:07 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Tue, 17 Feb 2015 17:08:07 +0200 Subject: [aerogear-dev] iOS meeting on Tuesday In-Reply-To: References: Message-ID: <805B411B-F74F-4543-A4C3-07F594A75B4D@gmail.com> fyi, meeting minutes: Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-17-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-17-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-17-15.00.log.html > On Feb 16, 2015, at 11:06 AM, Corinne Krych wrote: > > Hello all > > Our next iOS meeting will be on Tuesday 4pm (+1 GMT), here is the agenda: > http://oksoclap.com/p/aerogear_ios_meeting_17_february_2014 > > Main focus on 2.2 remaining tickets. > > ++ > 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/20150217/72425515/attachment.html From scm.blanc at gmail.com Tue Feb 17 17:06:06 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Tue, 17 Feb 2015 23:06:06 +0100 Subject: [aerogear-dev] Fwd: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences References: <54E31B28.9000705@nextop.io> Message-ID: <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> Hi ! I just wanted to share that interesting post from the Cordova dev list. It shows how to delegate XMLHttpRequest and image loading to a native implementation. Would we provide any advantage by using our iOS http lib and android Pipes over plain XMLHttpRequest ? Also check the reply where another one have used the same approach to add certificate pinning , that could be an interesting source of inspiration since I know cert pinning is on the security roadmap [1] S?bi [1] https://issues.jboss.org/browse/AGSEC-196 Envoy? de mon iPhone D?but du message transf?r? : > Exp?diteur: Brien Colwell > Date: 17 f?vrier 2015 11:42:48 UTC+1 > Destinataire: dev at cordova.apache.org > Objet: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences > R?pondre ?: dev at cordova.apache.org > > Hi All, > > I spent some time researching how much of the webview network stack I could replace with a Cordova plugin on Android. I wrote a post about it - > > https://github.com/nextopio/nextop-client/blob/master/docs/02.16.2015_CUSTOM_XMLHTTPREQUEST.md > > The take away is that a Cordova can fully replacing the default XHR and image loading in the webview for async=true, but it can't do async=false (but who uses that anyway :/). This is cool because plugins can experiment with new wire protocols to get data to the client. > > Best, > Brien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe at cordova.apache.org > For additional commands, e-mail: dev-help at cordova.apache.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150217/896d0ff2/attachment.html From matzew at apache.org Wed Feb 18 03:34:24 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Feb 2015 09:34:24 +0100 Subject: [aerogear-dev] Fwd: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences In-Reply-To: <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> References: <54E31B28.9000705@nextop.io> <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> Message-ID: On Tue, Feb 17, 2015 at 11:06 PM, S?bastien Blanc wrote: > Hi ! > I just wanted to share that interesting post from the Cordova dev list. It > shows how to delegate XMLHttpRequest and image loading to a native > implementation. > > Would we provide any advantage by using our iOS http lib and android Pipes > over plain XMLHttpRequest ? > Not sure I am really following your thoughts, but isn't that what we are already doing inside e.g. the push plugin? the actual HTTP stack is part of our native libs, instead of XHR -Matthias > > Also check the reply where another one have used the same approach to add > certificate pinning , that could be an interesting source of inspiration > since I know cert pinning is on the security roadmap [1] > > S?bi > [1] https://issues.jboss.org/browse/AGSEC-196 > > Envoy? de mon iPhone > > D?but du message transf?r? : > > *Exp?diteur:* Brien Colwell > *Date:* 17 f?vrier 2015 11:42:48 UTC+1 > *Destinataire:* dev at cordova.apache.org > *Objet:* *I replaced XMLHttpRequest and image loading with a plugin, and > wrote up my experiences* > *R?pondre ?:* dev at cordova.apache.org > > Hi All, > > I spent some time researching how much of the webview network stack I > could replace with a Cordova plugin on Android. I wrote a post about it - > > > https://github.com/nextopio/nextop-client/blob/master/docs/02.16.2015_CUSTOM_XMLHTTPREQUEST.md > > The take away is that a Cordova can fully replacing the default XHR and > image loading in the webview for async=true, but it can't do async=false > (but who uses that anyway :/). This is cool because plugins can experiment > with new wire protocols to get data to the client. > > Best, > Brien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe at cordova.apache.org > For additional commands, e-mail: dev-help at cordova.apache.org > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/7462de0f/attachment.html From scm.blanc at gmail.com Wed Feb 18 03:40:07 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 18 Feb 2015 09:40:07 +0100 Subject: [aerogear-dev] Fwd: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences In-Reply-To: References: <54E31B28.9000705@nextop.io> <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> Message-ID: On Wed, Feb 18, 2015 at 9:34 AM, Matthias Wessendorf wrote: > > > On Tue, Feb 17, 2015 at 11:06 PM, S?bastien Blanc > wrote: > >> Hi ! >> I just wanted to share that interesting post from the Cordova dev list. >> It shows how to delegate XMLHttpRequest and image loading to a native >> implementation. >> >> Would we provide any advantage by using our iOS http lib and android >> Pipes over plain XMLHttpRequest ? >> > > Not sure I am really following your thoughts, but isn't that what we are > already doing inside e.g. the push plugin? the actual HTTP stack is part of > our native libs, instead of XHR > sure that is what we do for Push, but I was not thinking of Push, was more thinking of a "AeroGear http" plugin that people could use for all their http calls but again no idea if that brings any advantage over regular XHR. > > -Matthias > > >> >> Also check the reply where another one have used the same approach to add >> certificate pinning , that could be an interesting source of inspiration >> since I know cert pinning is on the security roadmap [1] >> >> S?bi >> [1] https://issues.jboss.org/browse/AGSEC-196 >> >> Envoy? de mon iPhone >> >> D?but du message transf?r? : >> >> *Exp?diteur:* Brien Colwell >> *Date:* 17 f?vrier 2015 11:42:48 UTC+1 >> *Destinataire:* dev at cordova.apache.org >> *Objet:* *I replaced XMLHttpRequest and image loading with a plugin, and >> wrote up my experiences* >> *R?pondre ?:* dev at cordova.apache.org >> >> Hi All, >> >> I spent some time researching how much of the webview network stack I >> could replace with a Cordova plugin on Android. I wrote a post about it - >> >> >> https://github.com/nextopio/nextop-client/blob/master/docs/02.16.2015_CUSTOM_XMLHTTPREQUEST.md >> >> The take away is that a Cordova can fully replacing the default XHR and >> image loading in the webview for async=true, but it can't do async=false >> (but who uses that anyway :/). This is cool because plugins can experiment >> with new wire protocols to get data to the client. >> >> Best, >> Brien >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe at cordova.apache.org >> For additional commands, e-mail: dev-help at cordova.apache.org >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150218/6a48aa31/attachment-0001.html From matzew at apache.org Wed Feb 18 03:45:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Feb 2015 09:45:04 +0100 Subject: [aerogear-dev] Fwd: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences In-Reply-To: References: <54E31B28.9000705@nextop.io> <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> Message-ID: On Wed, Feb 18, 2015 at 9:40 AM, Sebastien Blanc wrote: > > > On Wed, Feb 18, 2015 at 9:34 AM, Matthias Wessendorf > wrote: > >> >> >> On Tue, Feb 17, 2015 at 11:06 PM, S?bastien Blanc >> wrote: >> >>> Hi ! >>> I just wanted to share that interesting post from the Cordova dev list. >>> It shows how to delegate XMLHttpRequest and image loading to a native >>> implementation. >>> >>> Would we provide any advantage by using our iOS http lib and android >>> Pipes over plain XMLHttpRequest ? >>> >> >> Not sure I am really following your thoughts, but isn't that what we are >> already doing inside e.g. the push plugin? the actual HTTP stack is part of >> our native libs, instead of XHR >> > sure that is what we do for Push, but I was not thinking of Push, was more > thinking of a "AeroGear http" plugin that people could use for all their > http calls but again no idea if that brings any advantage over regular XHR. > Ah! ok, that makes more sense - I was just wondering about this :-) Regarding Android-Pipes, since they over more than just HTTP, I am not sure if all of that is easy to integrate into the cordova web-view (e.g. Lifecycle and Activity hooks). But perhaps it's worth - at some point - to take a look at that. I doubt there is an immediate action needed, but feel free to track the idea on the AGCORDOVA jira instance > >> -Matthias >> >> >>> >>> Also check the reply where another one have used the same approach to >>> add certificate pinning , that could be an interesting source of >>> inspiration since I know cert pinning is on the security roadmap [1] >>> >>> S?bi >>> [1] https://issues.jboss.org/browse/AGSEC-196 >>> >>> Envoy? de mon iPhone >>> >>> D?but du message transf?r? : >>> >>> *Exp?diteur:* Brien Colwell >>> *Date:* 17 f?vrier 2015 11:42:48 UTC+1 >>> *Destinataire:* dev at cordova.apache.org >>> *Objet:* *I replaced XMLHttpRequest and image loading with a plugin, >>> and wrote up my experiences* >>> *R?pondre ?:* dev at cordova.apache.org >>> >>> Hi All, >>> >>> I spent some time researching how much of the webview network stack I >>> could replace with a Cordova plugin on Android. I wrote a post about it - >>> >>> >>> https://github.com/nextopio/nextop-client/blob/master/docs/02.16.2015_CUSTOM_XMLHTTPREQUEST.md >>> >>> The take away is that a Cordova can fully replacing the default XHR and >>> image loading in the webview for async=true, but it can't do async=false >>> (but who uses that anyway :/). This is cool because plugins can experiment >>> with new wire protocols to get data to the client. >>> >>> Best, >>> Brien >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe at cordova.apache.org >>> For additional commands, e-mail: dev-help at cordova.apache.org >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/94a7181b/attachment.html From corinnekrych at gmail.com Wed Feb 18 04:17:30 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 18 Feb 2015 10:17:30 +0100 Subject: [aerogear-dev] Fwd: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences In-Reply-To: References: <54E31B28.9000705@nextop.io> <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> Message-ID: <71E4A8C3-9A28-429B-AC3E-97E0F7486146@gmail.com> > On 18 Feb 2015, at 09:45, Matthias Wessendorf wrote: > > > > On Wed, Feb 18, 2015 at 9:40 AM, Sebastien Blanc wrote: > > > On Wed, Feb 18, 2015 at 9:34 AM, Matthias Wessendorf wrote: > > > On Tue, Feb 17, 2015 at 11:06 PM, S?bastien Blanc wrote: > Hi ! > I just wanted to share that interesting post from the Cordova dev list. It shows how to delegate XMLHttpRequest and image loading to a native implementation. > > Would we provide any advantage by using our iOS http lib and android Pipes over plain XMLHttpRequest ? > > Not sure I am really following your thoughts, but isn't that what we are already doing inside e.g. the push plugin? the actual HTTP stack is part of our native libs, instead of XHR > sure that is what we do for Push, but I was not thinking of Push, was more thinking of a "AeroGear http" plugin that people could use for all their http calls but again no idea if that brings any advantage over regular XHR. > > Ah! ok, that makes more sense - I was just wondering about this :-) > > Regarding Android-Pipes, since they over more than just HTTP, I am not sure if all of that is easy to integrate into the cordova web-view (e.g. Lifecycle and Activity hooks). But perhaps it's worth - at some point - to take a look at that. interesting indeed. I just don?t have a use case in mind? do you have one Sebi? > I doubt there is an immediate action needed, but feel free to track the idea on the AGCORDOVA jira instance > > > -Matthias > > > Also check the reply where another one have used the same approach to add certificate pinning , that could be an interesting source of inspiration since I know cert pinning is on the security roadmap [1] > > S?bi > [1] https://issues.jboss.org/browse/AGSEC-196 > > Envoy? de mon iPhone > > D?but du message transf?r? : > >> Exp?diteur: Brien Colwell >> Date: 17 f?vrier 2015 11:42:48 UTC+1 >> Destinataire: dev at cordova.apache.org >> Objet: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences >> R?pondre ?: dev at cordova.apache.org >> >> Hi All, >> >> I spent some time researching how much of the webview network stack I could replace with a Cordova plugin on Android. I wrote a post about it - >> >> https://github.com/nextopio/nextop-client/blob/master/docs/02.16.2015_CUSTOM_XMLHTTPREQUEST.md >> >> The take away is that a Cordova can fully replacing the default XHR and image loading in the webview for async=true, but it can't do async=false (but who uses that anyway :/). This is cool because plugins can experiment with new wire protocols to get data to the client. >> >> Best, >> Brien >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe at cordova.apache.org >> For additional commands, e-mail: dev-help at cordova.apache.org >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From scm.blanc at gmail.com Wed Feb 18 04:21:25 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 18 Feb 2015 10:21:25 +0100 Subject: [aerogear-dev] Fwd: I replaced XMLHttpRequest and image loading with a plugin, and wrote up my experiences In-Reply-To: <71E4A8C3-9A28-429B-AC3E-97E0F7486146@gmail.com> References: <54E31B28.9000705@nextop.io> <0564100C-87C0-4DCB-B9AB-25A1129A1647@gmail.com> <71E4A8C3-9A28-429B-AC3E-97E0F7486146@gmail.com> Message-ID: On Wed, Feb 18, 2015 at 10:17 AM, Corinne Krych wrote: > > > On 18 Feb 2015, at 09:45, Matthias Wessendorf wrote: > > > > > > > > On Wed, Feb 18, 2015 at 9:40 AM, Sebastien Blanc > wrote: > > > > > > On Wed, Feb 18, 2015 at 9:34 AM, Matthias Wessendorf > wrote: > > > > > > On Tue, Feb 17, 2015 at 11:06 PM, S?bastien Blanc > wrote: > > Hi ! > > I just wanted to share that interesting post from the Cordova dev list. > It shows how to delegate XMLHttpRequest and image loading to a native > implementation. > > > > Would we provide any advantage by using our iOS http lib and android > Pipes over plain XMLHttpRequest ? > > > > Not sure I am really following your thoughts, but isn't that what we are > already doing inside e.g. the push plugin? the actual HTTP stack is part of > our native libs, instead of XHR > > sure that is what we do for Push, but I was not thinking of Push, was > more thinking of a "AeroGear http" plugin that people could use for all > their http calls but again no idea if that brings any advantage over > regular XHR. > > > > Ah! ok, that makes more sense - I was just wondering about this :-) > > > > Regarding Android-Pipes, since they over more than just HTTP, I am not > sure if all of that is easy to integrate into the cordova web-view (e.g. > Lifecycle and Activity hooks). But perhaps it's worth - at some point - to > take a look at that. > > interesting indeed. > I just don?t have a use case in mind? do you have one Sebi? > To be honest I don't have one for the moment :) I was hoping on you ;) but like Matzew said let's track this idea for later. > > > > I doubt there is an immediate action needed, but feel free to track the > idea on the AGCORDOVA jira instance > > > > > > -Matthias > > > > > > Also check the reply where another one have used the same approach to > add certificate pinning , that could be an interesting source of > inspiration since I know cert pinning is on the security roadmap [1] > > > > S?bi > > [1] https://issues.jboss.org/browse/AGSEC-196 > > > > Envoy? de mon iPhone > > > > D?but du message transf?r? : > > > >> Exp?diteur: Brien Colwell > >> Date: 17 f?vrier 2015 11:42:48 UTC+1 > >> Destinataire: dev at cordova.apache.org > >> Objet: I replaced XMLHttpRequest and image loading with a plugin, and > wrote up my experiences > >> R?pondre ?: dev at cordova.apache.org > >> > >> Hi All, > >> > >> I spent some time researching how much of the webview network stack I > could replace with a Cordova plugin on Android. I wrote a post about it - > >> > >> > https://github.com/nextopio/nextop-client/blob/master/docs/02.16.2015_CUSTOM_XMLHTTPREQUEST.md > >> > >> The take away is that a Cordova can fully replacing the default XHR and > image loading in the webview for async=true, but it can't do async=false > (but who uses that anyway :/). This is cool because plugins can experiment > with new wire protocols to get data to the client. > >> > >> Best, > >> Brien > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscribe at cordova.apache.org > >> For additional commands, e-mail: dev-help at cordova.apache.org > >> > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150218/f180905c/attachment-0001.html From corinnekrych at gmail.com Wed Feb 18 04:29:52 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 18 Feb 2015 10:29:52 +0100 Subject: [aerogear-dev] house keeping on demo repos Message-ID: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> Hello guys As suggested by @passos and @abstractj I?ve just moved AeroDoc demo into our cookbook [1], [2] leaving old repo empty and deprecated. For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to 1.6.x as our 2.X Swift libs are not features complete (we?re missing storage implementation for now). Demos that implements features supported by 2.x will go on cookbook master. On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo - push demo: https://github.com/aerogear/aerogear-push-ios-demo - helloworld - push quickstart contacts - sync jedi demo (for iOS we already have a ticket for that [3]) I?d like to make sure we?re going in the same direction and create the missing tickets. Thanks for your feedback ++ Corinne [1] https://issues.jboss.org/browse/AGIOS-378 [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 [3] https://issues.jboss.org/browse/AGIOS-337 From matzew at apache.org Wed Feb 18 04:57:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Feb 2015 10:57:01 +0100 Subject: [aerogear-dev] house keeping on demo repos In-Reply-To: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> References: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> Message-ID: On Wed, Feb 18, 2015 at 10:29 AM, Corinne Krych wrote: > Hello guys > > As suggested by @passos and @abstractj I?ve just moved AeroDoc demo into > our cookbook [1], [2] leaving old repo empty and deprecated. > For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X > AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to > 1.6.x as our 2.X Swift libs are not features complete (we?re missing > storage implementation for now). Demos that implements features supported > by 2.x will go on cookbook master. > > On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : > - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo I think this needs an overhaul, due to its dependency on the server: https://github.com/aerogear/aerogear-otp-ios-demo/blob/master/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Controllers/AGLoginViewControler.m#L43 I forgot if we do have a ticket for that (do we have one for moving to cookbook?) > > - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo > - push demo: https://github.com/aerogear/aerogear-push-ios-demo > - helloworld > - push quickstart contacts > - sync jedi demo (for iOS we already have a ticket for that [3]) > Let's get tickets for them, to track the work. However, regarding push quickstarts (helloworld and contacts), lets please wait a bit - as I said earlier. However I do see a chance to (eventually) move them too.... (the related JIRAs for iOS are already assign to me) > > I?d like to make sure we?re going in the same direction and create the > missing tickets. > Thanks for your feedback > > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-378 > [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 > [3] https://issues.jboss.org/browse/AGIOS-337 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/47eac0e2/attachment.html From bruno at abstractj.org Wed Feb 18 07:05:33 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 10:05:33 -0200 Subject: [aerogear-dev] AeroGear Cordova Cookbooks repository Message-ID: <20150218120533.GC25288@abstractj.org> Good morning, people from awesomeland. I'm playing at the moment with the cookbooks from Cordova [1] and I was just wondering about move: - aerogear-aerodoc-cordova - https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova - https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/contacts-mobile-cordova To aerogear-cordova-cookbooks repository, easy to find and more centralized place. What do you think? yay/nay? [1] - https://github.com/aerogear/aerogear-cordova-cookbook -- abstractj PGP: 0x84DC9914 From matzew at apache.org Wed Feb 18 07:16:05 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Feb 2015 13:16:05 +0100 Subject: [aerogear-dev] AeroGear Cordova Cookbooks repository In-Reply-To: <20150218120533.GC25288@abstractj.org> References: <20150218120533.GC25288@abstractj.org> Message-ID: those two examples have been created for the Red Hat Unified Push Server (xPaaS), and should be kept on their own repositories. However, for our community examples, like AeroDoc, let's move these into our cookbooks. On Wed, Feb 18, 2015 at 1:05 PM, Bruno Oliveira wrote: > Good morning, people from awesomeland. I'm playing at the moment with > the cookbooks from Cordova [1] and I was just wondering about move: > > - aerogear-aerodoc-cordova > - https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova > - > https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/contacts-mobile-cordova > > To aerogear-cordova-cookbooks repository, easy to find and more > centralized place. What do you think? yay/nay? > > > [1] - https://github.com/aerogear/aerogear-cordova-cookbook > > -- > > 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/20150218/8faa4e1d/attachment.html From edewit at redhat.com Wed Feb 18 07:30:37 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 18 Feb 2015 13:30:37 +0100 Subject: [aerogear-dev] AeroGear Cordova Cookbooks repository In-Reply-To: <20150218120533.GC25288@abstractj.org> References: <20150218120533.GC25288@abstractj.org> Message-ID: <0F7F998F-29CB-4579-A0FA-0D3491045C88@redhat.com> Yeah +1 for the move of AeroDoc cordova > On 18 Feb,2015, at 13:05 , Bruno Oliveira wrote: > > Good morning, people from awesomeland. I'm playing at the moment with > the cookbooks from Cordova [1] and I was just wondering about move: > > - aerogear-aerodoc-cordova > - https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova > - https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/contacts-mobile-cordova > > To aerogear-cordova-cookbooks repository, easy to find and more > centralized place. What do you think? yay/nay? > > > [1] - https://github.com/aerogear/aerogear-cordova-cookbook > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Wed Feb 18 07:55:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Feb 2015 13:55:04 +0100 Subject: [aerogear-dev] parent release ? Message-ID: Hi, becasuse of https://github.com/aerogear/aerogear-parent/pull/41 got merged, I'd like to run another parent release - yay! However, just wondering, do any other folks have wishes to update some 3rd party dependencies in there ? 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/20150218/7e2b31a2/attachment.html From edewit at redhat.com Wed Feb 18 08:17:54 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 18 Feb 2015 14:17:54 +0100 Subject: [aerogear-dev] aerogear-oauth2-cordova Message-ID: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> Hi, I like to release another version of the aerogear-oauth2-cordova plugin version 1.0.2. Fixed are the following issues: [AGCORDOVA-58 ] - Update OAuth2 swift lib to version 0.2.0 [AGCORDOVA-46 ] - Add windows support Oauth2 To test just use the master branch: cordova plugin add https://github.com/aerogear/aerogear-oauth2-cordova.git Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/d783c4dd/attachment-0001.html From qmx at qmx.me Wed Feb 18 10:12:06 2015 From: qmx at qmx.me (Douglas Campos) Date: Wed, 18 Feb 2015 13:12:06 -0200 Subject: [aerogear-dev] UPS 1.0.3? In-Reply-To: <003901d0475f$20038070$600a8150$@pinelabs.com> References: <003901d0475f$20038070$600a8150$@pinelabs.com> Message-ID: <20150218151206.GH65532@darkstar.local> Howdy! Like mentioned on the thread, a release should be out soon - I'm still doing double and triple checks ensuring db migrations work flawlessly. I'm shooting for next week, assuming things keep going smoothly. -- qmx From lukas.fryc at gmail.com Wed Feb 18 10:14:53 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 18 Feb 2015 16:14:53 +0100 Subject: [aerogear-dev] New Site - Status Message-ID: Hey guys, the new site is in baking for a quite some time, but I believe the results are already shaping up. The Big Thanks go to Andres off course! I must say it is NOT COMPLETE yet, but I believe we can start receiving issues. Especially kind of "we need complete rework of this section" kind of issues ;-) http://staging-aerogearsite.rhcloud.com/ Please discuss bigger issues right here, but file any smaller issues under appropriate place in the New Design Epic: https://issues.jboss.org/browse/AEROGEAR-1546 Few bigger issues I identified and that I will need a help with: 1. filling in Core and Security landing pages 2. Guides for First Steps are missing for some platforms (they don't have to be overwhelmingly verbose, but at least we should have some) 3. connected individual's blog to News page (powered by planet.jboss.org, more info on IRC) Few issues that we still need to tackle - I believe we can cover that with Andres, but help is always welcomed! 1. make News page work javascript-wide (filtering, etc) [me] 2. document how-to + style guide for drafting/posting new posts on aerogear.org [me] 2. style individual Guides 3. style individual Posts 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] 5. grammar/typo corrections [Catherine offered help here] Some features I planned originally will slip from the first release, but the main priority now is get the New Site out! ETA: the site could be nearly production-ready end of this week. Cheers, ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/b46d3eb9/attachment.html From lukas.fryc at gmail.com Wed Feb 18 10:23:30 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 18 Feb 2015 16:23:30 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: First big issue popped up quickly (thanks Matthias), the OAuth2 landing pages does not fit anywhere [1] http://staging-aerogearsite.rhcloud.com/OAuth2/ I believe it should be part of Security page, right? On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the results > are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > but file any smaller issues under appropriate place in the New Design Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that with > Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/bb062dfd/attachment.html From daniel.bevenius at gmail.com Wed Feb 18 10:37:39 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 18 Feb 2015 16:37:39 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: Will go through more carefully but this looks great. Really nice work guys! On 18 February 2015 at 16:23, Luk?? Fry? wrote: > First big issue popped up quickly (thanks Matthias), the OAuth2 landing > pages does not fit anywhere [1] > > http://staging-aerogearsite.rhcloud.com/OAuth2/ > > I believe it should be part of Security page, right? > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the >> results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving >> issues. Especially kind of "we need complete rework of this section" kind >> of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, >> but file any smaller issues under appropriate place in the New Design >> Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have >> to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, >> more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that >> with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on >> aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, but >> the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> 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/20150218/76c779cc/attachment.html From bruno at abstractj.org Wed Feb 18 11:10:57 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 14:10:57 -0200 Subject: [aerogear-dev] aerogear-oauth2-cordova In-Reply-To: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> References: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> Message-ID: <20150218161057.GB27409@abstractj.org> When it will be released? On 2015-02-18, Erik Jan de Wit wrote: > Hi, > > I like to release another version of the aerogear-oauth2-cordova plugin version 1.0.2. Fixed are the following issues: > > [AGCORDOVA-58 ] - Update OAuth2 swift lib to version 0.2.0 > [AGCORDOVA-46 ] - Add windows support Oauth2 > > > To test just use the master branch: > > cordova plugin add https://github.com/aerogear/aerogear-oauth2-cordova.git > > > 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 edewit at redhat.com Wed Feb 18 11:14:22 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 18 Feb 2015 17:14:22 +0100 Subject: [aerogear-dev] aerogear-oauth2-cordova In-Reply-To: <20150218161057.GB27409@abstractj.org> References: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> <20150218161057.GB27409@abstractj.org> Message-ID: <7F7DEE24-C186-48F1-8B4D-8F2836F65F51@redhat.com> I?ll wait 72h (lazy consensus) then release... > On 18 Feb,2015, at 17:10 , Bruno Oliveira wrote: > > When it will be released? > > On 2015-02-18, Erik Jan de Wit wrote: >> Hi, >> >> I like to release another version of the aerogear-oauth2-cordova plugin version 1.0.2. Fixed are the following issues: >> >> [AGCORDOVA-58 ] - Update OAuth2 swift lib to version 0.2.0 >> [AGCORDOVA-46 ] - Add windows support Oauth2 >> >> >> To test just use the master branch: >> >> cordova plugin add https://github.com/aerogear/aerogear-oauth2-cordova.git >> >> >> 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 From scm.blanc at gmail.com Wed Feb 18 11:16:41 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 18 Feb 2015 17:16:41 +0100 Subject: [aerogear-dev] aerogear-oauth2-cordova In-Reply-To: <7F7DEE24-C186-48F1-8B4D-8F2836F65F51@redhat.com> References: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> <20150218161057.GB27409@abstractj.org> <7F7DEE24-C186-48F1-8B4D-8F2836F65F51@redhat.com> Message-ID: I'm +1 on the Windows bits. On Wed, Feb 18, 2015 at 5:14 PM, Erik Jan de Wit wrote: > I?ll wait 72h (lazy consensus) then release... > > > On 18 Feb,2015, at 17:10 , Bruno Oliveira wrote: > > > > When it will be released? > > > > On 2015-02-18, Erik Jan de Wit wrote: > >> Hi, > >> > >> I like to release another version of the aerogear-oauth2-cordova plugin > version 1.0.2. Fixed are the following issues: > >> > >> [AGCORDOVA-58 ] - Update > OAuth2 swift lib to version 0.2.0 > >> [AGCORDOVA-46 ] - Add > windows support Oauth2 > >> > >> > >> To test just use the master branch: > >> > >> cordova plugin add > https://github.com/aerogear/aerogear-oauth2-cordova.git > >> > >> > >> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/0d173956/attachment.html From bruno at abstractj.org Wed Feb 18 11:20:00 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 14:20:00 -0200 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: <20150218162000.GC27409@abstractj.org> On 2015-02-18, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the results > are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > but file any smaller issues under appropriate place in the New Design Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages Ahoy, I linked https://issues.jboss.org/browse/AGSEC-200 to solve this issue. Let me know if I messed up with something. > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that with > Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > _______________________________________________ > 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 Feb 18 11:21:37 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 14:21:37 -0200 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: <20150218162137.GD27409@abstractj.org> Totally correct, I'm on it. On 2015-02-18, Luk?? Fry? wrote: > First big issue popped up quickly (thanks Matthias), the OAuth2 landing > pages does not fit anywhere [1] > > http://staging-aerogearsite.rhcloud.com/OAuth2/ > > I believe it should be part of Security page, right? > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > > > Hey guys, > > > > the new site is in baking for a quite some time, but I believe the results > > are already shaping up. The Big Thanks go to Andres off course! > > > > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > > issues. Especially kind of "we need complete rework of this section" kind > > of issues ;-) > > > > http://staging-aerogearsite.rhcloud.com/ > > > > Please discuss bigger issues right here, > > but file any smaller issues under appropriate place in the New Design Epic: > > > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > > > > > Few bigger issues I identified and that I will need a help with: > > > > 1. filling in Core and Security landing pages > > 2. Guides for First Steps are missing for some platforms (they don't have > > to be overwhelmingly verbose, but at least we should have some) > > 3. connected individual's blog to News page (powered by planet.jboss.org, > > more info on IRC) > > > > > > > > > > Few issues that we still need to tackle - I believe we can cover that with > > Andres, but help is always welcomed! > > > > 1. make News page work javascript-wide (filtering, etc) [me] > > 2. document how-to + style guide for drafting/posting new posts on > > aerogear.org [me] > > 2. style individual Guides > > 3. style individual Posts > > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > > 5. grammar/typo corrections [Catherine offered help here] > > > > > > Some features I planned originally will slip from the first release, but > > the main priority now is get the New Site out! > > > > ETA: the site could be nearly production-ready end of this week. > > > > > > Cheers, > > > > ~ Lukas > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From supittma at redhat.com Wed Feb 18 11:28:11 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 18 Feb 2015 11:28:11 -0500 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: <54E4BD9B.3040908@redhat.com> On 02/18/2015 10:14 AM, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start > receiving issues. Especially kind of "we need complete rework of this > section" kind of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, Not sure if it is a bigger or smaller issue, but can we speed up the animations (or remove them)? Right now when I mouse over elements (header nav, sidebar nav) it is really distracting. Also the fade in on the landing page is really slow. Then again I may just drink too much coffee. > but file any smaller issues under appropriate place in the New Design > Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't > have to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by > planet.jboss.org , more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that > with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, > but the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > > _______________________________________________ > 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/20150218/4cdb5f15/attachment.html From agalante at redhat.com Wed Feb 18 11:35:44 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 18 Feb 2015 11:35:44 -0500 (EST) Subject: [aerogear-dev] New Site - Status In-Reply-To: <54E4BD9B.3040908@redhat.com> References: <54E4BD9B.3040908@redhat.com> Message-ID: <895024761.2646124.1424277344710.JavaMail.zimbra@redhat.com> Summer, no problem, I'll take care of it: https://issues.jboss.org/browse/AEROGEAR-1628 ----- Original Message ----- From: "Summers Pittman" To: aerogear-dev at lists.jboss.org Sent: Wednesday, February 18, 2015 1:28:11 PM Subject: Re: [aerogear-dev] New Site - Status On 02/18/2015 10:14 AM, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start > receiving issues. Especially kind of "we need complete rework of this > section" kind of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, Not sure if it is a bigger or smaller issue, but can we speed up the animations (or remove them)? Right now when I mouse over elements (header nav, sidebar nav) it is really distracting. Also the fade in on the landing page is really slow. Then again I may just drink too much coffee. > but file any smaller issues under appropriate place in the New Design > Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't > have to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by > planet.jboss.org , more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that > with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, > but the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From daniel at passos.me Wed Feb 18 11:36:10 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 18 Feb 2015 14:36:10 -0200 Subject: [aerogear-dev] aerogear-oauth2-cordova In-Reply-To: References: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> <20150218161057.GB27409@abstractj.org> <7F7DEE24-C186-48F1-8B4D-8F2836F65F51@redhat.com> Message-ID: Why not also update the AGDROID 2.0.alpha.1 by 2.0? -- Passos On Wed, Feb 18, 2015 at 2:16 PM, Sebastien Blanc wrote: > I'm +1 on the Windows bits. > > > On Wed, Feb 18, 2015 at 5:14 PM, Erik Jan de Wit > wrote: > >> I?ll wait 72h (lazy consensus) then release... >> >> > On 18 Feb,2015, at 17:10 , Bruno Oliveira wrote: >> > >> > When it will be released? >> > >> > On 2015-02-18, Erik Jan de Wit wrote: >> >> Hi, >> >> >> >> I like to release another version of the aerogear-oauth2-cordova >> plugin version 1.0.2. Fixed are the following issues: >> >> >> >> [AGCORDOVA-58 ] - >> Update OAuth2 swift lib to version 0.2.0 >> >> [AGCORDOVA-46 ] - Add >> windows support Oauth2 >> >> >> >> >> >> To test just use the master branch: >> >> >> >> cordova plugin add >> https://github.com/aerogear/aerogear-oauth2-cordova.git >> >> >> >> >> >> 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 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150218/45a1cb70/attachment-0001.html From supittma at redhat.com Wed Feb 18 11:37:25 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 18 Feb 2015 11:37:25 -0500 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: <54E4BFC5.3090002@redhat.com> On 02/18/2015 10:14 AM, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start > receiving issues. Especially kind of "we need complete rework of this > section" kind of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, I need to make a JIRA to change the Android section of first steps. There is no reason anyone should be compiling the Android library. However part of that will include moving the how to build the Android library docs. Where should those go? Also what should replace it? Getting started with he Android libraries is basically include the stuff you want in your build/pom and use it. Also, I noticed the getting started docs for Cordova include a lot of basic "what is cordova" flavored information. Should we really be concerned on the project page with teaching people how to use the platform? > but file any smaller issues under appropriate place in the New Design > Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't > have to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by > planet.jboss.org , more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that > with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, > but the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > > _______________________________________________ > 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/20150218/b526d269/attachment.html From bruno at abstractj.org Wed Feb 18 11:43:08 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 14:43:08 -0200 Subject: [aerogear-dev] parent release ? In-Reply-To: References: Message-ID: Go ahead! On Wed, Feb 18, 2015 at 10:55 AM, Matthias Wessendorf wrote: > Hi, > > becasuse of https://github.com/aerogear/aerogear-parent/pull/41 got > merged, I'd like to run another parent release - yay! > > However, just wondering, do any other folks have wishes to update some 3rd > party dependencies in there ? > > Thanks! > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/2ffa487b/attachment.html From bruno at abstractj.org Wed Feb 18 11:45:30 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 14:45:30 -0200 Subject: [aerogear-dev] AeroGear Cordova Cookbooks repository In-Reply-To: References: <20150218120533.GC25288@abstractj.org> Message-ID: Jira created: https://issues.jboss.org/browse/AGCORDOVA-64 On Wed, Feb 18, 2015 at 10:16 AM, Matthias Wessendorf wrote: > those two examples have been created for the Red Hat Unified Push Server > (xPaaS), and should be kept on their own repositories. > > However, for our community examples, like AeroDoc, let's move these into > our cookbooks. > > > > On Wed, Feb 18, 2015 at 1:05 PM, Bruno Oliveira > wrote: > >> Good morning, people from awesomeland. I'm playing at the moment with >> the cookbooks from Cordova [1] and I was just wondering about move: >> >> - aerogear-aerodoc-cordova >> - >> https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova >> - >> https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/contacts-mobile-cordova >> >> To aerogear-cordova-cookbooks repository, easy to find and more >> centralized place. What do you think? yay/nay? >> >> >> [1] - https://github.com/aerogear/aerogear-cordova-cookbook >> >> -- >> >> 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 > -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/0704b841/attachment.html From daniel at passos.me Wed Feb 18 11:48:51 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 18 Feb 2015 14:48:51 -0200 Subject: [aerogear-dev] house keeping on demo repos In-Reply-To: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> References: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> Message-ID: On Wed, Feb 18, 2015 at 7:29 AM, Corinne Krych wrote: > Hello guys > > As suggested by @passos and @abstractj I?ve just moved AeroDoc demo into > our cookbook [1], [2] leaving old repo empty and deprecated. > For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X > AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to > 1.6.x as our 2.X Swift libs are not features complete (we?re missing > storage implementation for now). Demos that implements features supported > by 2.x will go on cookbook master. > > On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : > - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo > - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo > - push demo: https://github.com/aerogear/aerogear-push-ios-demo > - helloworld > - push quickstart contacts > - sync jedi demo (for iOS we already have a ticket for that [3]) > > I?d like to make sure we?re going in the same direction and create the > missing tickets. > AGDROID-156 - aerogear-crypto-android-demo AGDROID-383 - aerogear-otp-android-demo > Thanks for your feedback > > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-378 > [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 > [3] https://issues.jboss.org/browse/AGIOS-337 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/7649c85f/attachment-0001.html From daniel at passos.me Wed Feb 18 11:50:25 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 18 Feb 2015 14:50:25 -0200 Subject: [aerogear-dev] parent release ? In-Reply-To: References: Message-ID: +1 On Wed, Feb 18, 2015 at 2:43 PM, Bruno Oliveira wrote: > Go ahead! > > On Wed, Feb 18, 2015 at 10:55 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> becasuse of https://github.com/aerogear/aerogear-parent/pull/41 got >> merged, I'd like to run another parent release - yay! >> >> However, just wondering, do any other folks have wishes to update some >> 3rd party dependencies in there ? >> >> Thanks! >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/56a40f77/attachment.html From bruno at abstractj.org Wed Feb 18 12:53:25 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 15:53:25 -0200 Subject: [aerogear-dev] house keeping on demo repos In-Reply-To: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> References: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> Message-ID: <20150218175325.GA41226@abstractj.org> Hi Corinne, I moved AeroDoc for the cookbooks and can do the same for the bits on iOS/JS. Feel free to file/assign jiras to me if help is needed On 2015-02-18, Corinne Krych wrote: > Hello guys > > As suggested by @passos and @abstractj I?ve just moved AeroDoc demo into our cookbook [1], [2] leaving old repo empty and deprecated. > For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to 1.6.x as our 2.X Swift libs are not features complete (we?re missing storage implementation for now). Demos that implements features supported by 2.x will go on cookbook master. > > On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : > - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo > - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo > - push demo: https://github.com/aerogear/aerogear-push-ios-demo > - helloworld > - push quickstart contacts > - sync jedi demo (for iOS we already have a ticket for that [3]) > > I?d like to make sure we?re going in the same direction and create the missing tickets. > Thanks for your feedback > > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-378 > [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 > [3] https://issues.jboss.org/browse/AGIOS-337 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From daniel.bevenius at gmail.com Wed Feb 18 12:54:34 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 18 Feb 2015 18:54:34 +0100 Subject: [aerogear-dev] parent release ? In-Reply-To: References: Message-ID: +1 onsdag 18 februari 2015 skrev Daniel Passos : > +1 > > On Wed, Feb 18, 2015 at 2:43 PM, Bruno Oliveira > wrote: > >> Go ahead! >> >> On Wed, Feb 18, 2015 at 10:55 AM, Matthias Wessendorf > > wrote: >> >>> Hi, >>> >>> becasuse of https://github.com/aerogear/aerogear-parent/pull/41 got >>> merged, I'd like to run another parent release - yay! >>> >>> However, just wondering, do any other folks have wishes to update some >>> 3rd party dependencies in there ? >>> >>> Thanks! >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150218/47209f96/attachment.html From bruno at abstractj.org Wed Feb 18 12:59:32 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 18 Feb 2015 15:59:32 -0200 Subject: [aerogear-dev] house keeping on demo repos In-Reply-To: References: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> Message-ID: <20150218175932.GB41226@abstractj.org> On 2015-02-18, Matthias Wessendorf wrote: > On Wed, Feb 18, 2015 at 10:29 AM, Corinne Krych > wrote: > > > Hello guys > > > > As suggested by @passos and @abstractj I?ve just moved AeroDoc demo into > > our cookbook [1], [2] leaving old repo empty and deprecated. > > For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X > > AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to > > 1.6.x as our 2.X Swift libs are not features complete (we?re missing > > storage implementation for now). Demos that implements features supported > > by 2.x will go on cookbook master. > > > > On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : > > - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo > > > I think this needs an overhaul, due to its dependency on the server: > https://github.com/aerogear/aerogear-otp-ios-demo/blob/master/AeroGear-OTP-Demo/AeroGear-OTP-Demo/Controllers/AGLoginViewControler.m#L43 Jira created: https://issues.jboss.org/browse/AGIOS-390 > > I forgot if we do have a ticket for that (do we have one for moving to > cookbook?) > > > > > - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo > > - push demo: https://github.com/aerogear/aerogear-push-ios-demo > > - helloworld > > - push quickstart contacts > > - sync jedi demo (for iOS we already have a ticket for that [3]) > > > > Let's get tickets for them, to track the work. > > However, regarding push quickstarts (helloworld and contacts), lets please > wait a bit - as I said earlier. However I do see a chance to (eventually) > move them too.... (the related JIRAs for iOS are already assign to me) > > > > > > > I?d like to make sure we?re going in the same direction and create the > > missing tickets. > > Thanks for your feedback > > > > ++ > > Corinne > > [1] https://issues.jboss.org/browse/AGIOS-378 > > [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 > > [3] https://issues.jboss.org/browse/AGIOS-337 > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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 edewit at redhat.com Thu Feb 19 02:16:46 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 19 Feb 2015 08:16:46 +0100 Subject: [aerogear-dev] aerogear-oauth2-cordova In-Reply-To: References: <93C505E1-EF8D-44E5-B9DD-CA994753A952@redhat.com> <20150218161057.GB27409@abstractj.org> <7F7DEE24-C186-48F1-8B4D-8F2836F65F51@redhat.com> Message-ID: <34FEC6F3-EAAD-4207-B121-A10992091968@redhat.com> > On 18 Feb,2015, at 17:36 , Daniel Passos wrote: > > Why not also update the AGDROID 2.0.alpha.1 by 2.0? Right good point, let?s do that as well > > -- Passos > > On Wed, Feb 18, 2015 at 2:16 PM, Sebastien Blanc > wrote: > I'm +1 on the Windows bits. > > > On Wed, Feb 18, 2015 at 5:14 PM, Erik Jan de Wit > wrote: > I?ll wait 72h (lazy consensus) then release... > > > On 18 Feb,2015, at 17:10 , Bruno Oliveira > wrote: > > > > When it will be released? > > > > On 2015-02-18, Erik Jan de Wit wrote: > >> Hi, > >> > >> I like to release another version of the aerogear-oauth2-cordova plugin version 1.0.2. Fixed are the following issues: > >> > >> [AGCORDOVA-58 >] - Update OAuth2 swift lib to version 0.2.0 > >> [AGCORDOVA-46 >] - Add windows support Oauth2 > >> > >> > >> To test just use the master branch: > >> > >> cordova plugin add https://github.com/aerogear/aerogear-oauth2-cordova.git > >> > > >> > >> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150219/d08243e4/attachment-0001.html From cvasilak at gmail.com Thu Feb 19 03:52:40 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 19 Feb 2015 10:52:40 +0200 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: awesome work Lucas/Agalante! went though a bit and here is a small feedback on the iOS side, let me know and will appropriate jiras in the epic if needed - In the "AeroGearCore?Guides ? section can we also add an iOS 2.x section containing the links of the "User Guides? from our old web site - In the "downloads section? let?s fix the link of ?looking for AeroGear iOS 1.x series, please visit this page? to point to this page? - In the ?Demos? section? the link of the iOS AeroDoc demo should be changed to point here and more general item: - In the home page clicking the titles ?AeroGearCore, AeroGearSecurity? etc link you to the top of the page, not sure maybe update and treat is as if the ?clicked the "Learn More? button Let me know if you need something from me, be glad to help! awesome work! - Christos > On Feb 18, 2015, at 5:14 PM, Luk?? Fry? wrote: > > Hey guys, > > the new site is in baking for a quite some time, but I believe the results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving issues. Especially kind of "we need complete rework of this section" kind of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > but file any smaller issues under appropriate place in the New Design Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org , more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > 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/20150219/0c11bfe4/attachment.html From corinnekrych at gmail.com Thu Feb 19 04:00:59 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 19 Feb 2015 10:00:59 +0100 Subject: [aerogear-dev] house keeping on demo repos In-Reply-To: References: <4423134A-CC01-4262-9E28-AC5D3773A581@gmail.com> Message-ID: <80EEB37E-3DDF-49C5-A9CD-9873EB5AFBB5@gmail.com> > On 18 Feb 2015, at 17:48, Daniel Passos wrote: > > On Wed, Feb 18, 2015 at 7:29 AM, Corinne Krych wrote: > Hello guys > > As suggested by @passos and @abstractj I?ve just moved AeroDoc demo into our cookbook [1], [2] leaving old repo empty and deprecated. > For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to 1.6.x as our 2.X Swift libs are not features complete (we?re missing storage implementation for now). Demos that implements features supported by 2.x will go on cookbook master. > > On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : > - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo > - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo > - push demo: https://github.com/aerogear/aerogear-push-ios-demo > - helloworld > - push quickstart contacts > - sync jedi demo (for iOS we already have a ticket for that [3]) > > I?d like to make sure we?re going in the same direction and create the missing tickets. > > AGDROID-156 - aerogear-crypto-android-demo > AGDROID-383 - aerogear-otp-android-demo Cool! So I've just created: AGIOS-391 for otp demo in cookbook 1.6.x AGIOS-392 for crypto demo in cookbook 1.6.x @abstractj feel free to take the tickets! AGIOS-393 for push-demo rewrite in Swift and move in cookbook 2.x AGIOS-394 for otp demo rewrite in Swift and move to cookbook 2.x AGIOS-396 for crypto demo rewrite in Swift and move to cookbook 2.x We still maintain 2 versions of cookbook: - 1.6.x branch for obj-c (not yet migrated to 2.X Swift libs) demos - master branch with Swift 2.x demos Once we?re feature complete (provide storage in 2.x etc?) we can deprecated 1.6.x branch. > > Thanks for your feedback > > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-378 > [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 > [3] https://issues.jboss.org/browse/AGIOS-337 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From lukas.fryc at gmail.com Thu Feb 19 05:44:45 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 19 Feb 2015 11:44:45 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: <54E4BFC5.3090002@redhat.com> References: <54E4BFC5.3090002@redhat.com> Message-ID: @Summers, I agree that we don't have to document whole process of setting the environment up, but the docs should at least guide users that are completely new to the subject appropriately. Use case: I haven't developed anything on native Android yet, and I want to change that. I want to make that shift with AeroGear. But what should I do? I know AeroGear, nothing else. Where should I go now to get the basics AeroGear expects from me? So First Steps guide can cover what are expectations from the user on development environment side. It may just contain brief description of prerequisites and few links where people may get more information. It can also contain our preferred/opinionated way of Android development, being it an IDE of our choice or whatever. On Wed, Feb 18, 2015 at 5:37 PM, Summers Pittman wrote: > On 02/18/2015 10:14 AM, Luk?? Fry? wrote: > > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > > I need to make a JIRA to change the Android section of first steps. There > is no reason anyone should be compiling the Android library. However part > of that will include moving the how to build the Android library docs. > Where should those go? Also what should replace it? Getting started with > he Android libraries is basically include the stuff you want in your > build/pom and use it. > > Also, I noticed the getting started docs for Cordova include a lot of > basic "what is cordova" flavored information. Should we really be > concerned on the project page with teaching people how to use the platform? > > but file any smaller issues under appropriate place in the New Design > Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that > with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150219/373afc96/attachment.html From supittma at redhat.com Thu Feb 19 11:23:06 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 19 Feb 2015 11:23:06 -0500 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: <54E4BFC5.3090002@redhat.com> Message-ID: <54E60DEA.2040303@redhat.com> On 02/19/2015 05:44 AM, Luk?? Fry? wrote: > @Summers, I agree that we don't have to document whole process of > setting the environment up, On that point JIRA created : AEROGEAR-1629 > > but the docs should at least guide users that are completely new to > the subject appropriately. > > Use case: I haven't developed anything on native Android yet, and I > want to change that. I want to make that shift with AeroGear. But what > should I do? I know AeroGear, nothing else. Where should I go now to > get the basics AeroGear expects from me? We don't exactly have a "know AeroGear". This isn't like Cordova or Titanium where you build an app targeting their runtime and package it for a platform. > > > So First Steps guide can cover what are expectations from the user on > development environment side. It may just contain brief description of > prerequisites and few links where people may get more information. Then adding in a line "We expect you to know the basics of Android development with Android Studio", including a link to Google's getting started docs and having a section on what to add to the build.gradle files with cross links to relevant user guides should be enough? That is the goal of the JIRA issue at least right now. > > It can also contain our preferred/opinionated way of Android > development, being it an IDE of our choice or whatever. I'm guessing I don't get to call Eclipse a miserable hell dimension from which there is no escape one you enter? ;) Where should the building guide go? (Will need to make another JIRA for that) > > On Wed, Feb 18, 2015 at 5:37 PM, Summers Pittman > wrote: > > On 02/18/2015 10:14 AM, Luk?? Fry? wrote: >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe >> the results are already shaping up. The Big Thanks go to Andres >> off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start >> receiving issues. Especially kind of "we need complete rework of >> this section" kind of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, > I need to make a JIRA to change the Android section of first > steps. There is no reason anyone should be compiling the Android > library. However part of that will include moving the how to > build the Android library docs. Where should those go? Also what > should replace it? Getting started with he Android libraries is > basically include the stuff you want in your build/pom and use it. > > Also, I noticed the getting started docs for Cordova include a lot > of basic "what is cordova" flavored information. Should we really > be concerned on the project page with teaching people how to use > the platform? >> but file any smaller issues under appropriate place in the New >> Design Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they >> don't have to be overwhelmingly verbose, but at least we should >> have some) >> 3. connected individual's blog to News page (powered by >> planet.jboss.org , more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover >> that with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts >> on aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first >> release, but the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150219/79747870/attachment-0001.html From scm.blanc at gmail.com Thu Feb 19 17:05:36 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Thu, 19 Feb 2015 23:05:36 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: <54E4BFC5.3090002@redhat.com> References: <54E4BFC5.3090002@redhat.com> Message-ID: <64A38D36-ADC9-4021-8206-F519A4EE6B02@gmail.com> Envoy? de mon iPhone > Le 18 f?vr. 2015 ? 17:37, Summers Pittman a ?crit : > >> On 02/18/2015 10:14 AM, Luk?? Fry? wrote: >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving issues. Especially kind of "we need complete rework of this section" kind of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, > I need to make a JIRA to change the Android section of first steps. There is no reason anyone should be compiling the Android library. However part of that will include moving the how to build the Android library docs. Where should those go? Also what should replace it? Getting started with he Android libraries is basically include the stuff you want in your build/pom and use it. > > Also, I noticed the getting started docs for Cordova include a lot of basic "what is cordova" flavored information. Should we really be concerned on the project page with teaching people how to use the platform? I agree that most of the content there is outdated and could be probably removed (except maybe the JBDS section that could be refreshed it replaced by a short introduction to eclipse Thym). I will open a jira to track this. >> but file any smaller issues under appropriate place in the New Design Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, but the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150219/e144c04e/attachment.html From matzew at apache.org Fri Feb 20 04:09:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 10:09:18 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: <54E4BD9B.3040908@redhat.com> References: <54E4BD9B.3040908@redhat.com> Message-ID: On Wed, Feb 18, 2015 at 5:28 PM, Summers Pittman wrote: > On 02/18/2015 10:14 AM, Luk?? Fry? wrote: > > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > > Not sure if it is a bigger or smaller issue, but can we speed up the > animations (or remove them)? Right now when I mouse over elements (header > nav, sidebar nav) it is really distracting. Also the fade in on the > landing page is really slow. Then again I may just drink too much coffee. > No, I fully agree > but file any smaller issues under appropriate place in the New Design > Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that > with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > > _______________________________________________ > 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/20150220/c46634e7/attachment.html From matzew at apache.org Fri Feb 20 04:10:40 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 10:10:40 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: Hi Lukas and Andres, I have several comments, here are mine for the landing page (more to come): # Startpage * annimation is nice, for the first time, but afterwards it's really annoying * version? That implies a version of AeroGear, which is not really existing * I think the current startpage does a better job, listing the supported platforms (*e.g. Android, iOS, Cordova or Windows) -> could we add logos around the device images? * clicking the arrow: nothing happens * scrolling down, I see "Modules", "cross-platform" and "What is happening". Not sure, but isn't that already a lot on the startpage? I think the big "Bringing mobile and enterprise together." is a bit too big, but I am not sure how to make it more useful (in terms of containing actual info). I looks nice, but the arrow is not working, and scrolling down is _not_ obvious ## Modules I wish this info was more visible. is it possible to do the fancy annimation just once, and afterwards have minimized devices/logos, to get an immediate overview of what AeroGear is offering (the modules)? ## What's happening Let's make that an extra tab? More mails will come ;-) On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the results > are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > but file any smaller issues under appropriate place in the New Design Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that with > Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/2aa053d0/attachment-0001.html From matzew at apache.org Fri Feb 20 04:11:50 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 10:11:50 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: <64A38D36-ADC9-4021-8206-F519A4EE6B02@gmail.com> References: <54E4BFC5.3090002@redhat.com> <64A38D36-ADC9-4021-8206-F519A4EE6B02@gmail.com> Message-ID: On Thu, Feb 19, 2015 at 11:05 PM, S?bastien Blanc wrote: > > > Envoy? de mon iPhone > > Le 18 f?vr. 2015 ? 17:37, Summers Pittman a ?crit : > > On 02/18/2015 10:14 AM, Luk?? Fry? wrote: > > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > > I need to make a JIRA to change the Android section of first steps. There > is no reason anyone should be compiling the Android library. However part > of that will include moving the how to build the Android library docs. > Where should those go? Also what should replace it? Getting started with > he Android libraries is basically include the stuff you want in your > build/pom and use it. > > Also, I noticed the getting started docs for Cordova include a lot of > basic "what is cordova" flavored information. Should we really be > concerned on the project page with teaching people how to use the platform? > > I agree that most of the content there is outdated and could be probably > removed (except maybe the JBDS section that could be refreshed it replaced > by a short introduction to eclipse Thym). > I will open a jira to track this. > Please do! I thought we agreed on an older thread already on removing some of that > > but file any smaller issues under appropriate place in the New Design > Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that > with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > > _______________________________________________ > 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/0fab5ab9/attachment.html From matzew at apache.org Fri Feb 20 04:29:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 10:29:02 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: Here area some comments for the push module # Modules - Push * the overview has a view subsections: UnifiedPush, SimplePush, WebPush, Roadmap, Get involved => is it possible to get a TOC at the righ hand side? * we have a link to all "push" repos, that is OK, but I'd also like to see explict links to the repos of the servers (UnifiedPush, SimplePush, WebPush), perhaps next to their sections? * the documentation link jumps to the specs (For UPS that is API docs), while the real doc (the UPS user guide) is not linked, on docs (I know it's in the middle of the text somewhere below, but not explict linked) ## guides (push) https://issues.jboss.org/browse/AEROGEAR-1631 can't we have something like https://aerogear.org/docs/unifiedpush/ ? that cleanly give an overview of all UPS related docs - instead of overloading the Guides index page (it has a lot of stuff) * on large pages, like http://staging-aerogearsite.rhcloud.com/docs/unifiedpush/ups_userguide/admin-ui/ I miss a TOC * we dont show the nice WARNING or INFO images anymore - here is one example: now: https://aerogear.org/docs/unifiedpush/ups_userguide/overview/ soon: http://staging-aerogearsite.rhcloud.com/docs/unifiedpush/ups_userguide/overview/ On Fri, Feb 20, 2015 at 10:10 AM, Matthias Wessendorf wrote: > Hi Lukas and Andres, > > I have several comments, here are mine for the landing page (more to come): > > # Startpage > > * annimation is nice, for the first time, but afterwards it's really > annoying > * version? That implies a version of AeroGear, which is not really existing > * I think the current startpage does a better job, listing the supported > platforms (*e.g. Android, iOS, Cordova or Windows) -> could we add logos > around the device images? > * clicking the arrow: nothing happens > * scrolling down, I see "Modules", "cross-platform" and "What is > happening". Not sure, but isn't that already a lot on the startpage? > > I think the big "Bringing mobile and enterprise together." is a bit too > big, but I am not sure how to make it more useful (in terms of containing > actual info). I looks nice, but the arrow is not working, and scrolling > down is _not_ obvious > > ## Modules > I wish this info was more visible. is it possible to do the fancy > annimation just once, and afterwards have minimized devices/logos, to get > an immediate overview of what AeroGear is offering (the modules)? > > ## What's happening > Let's make that an extra tab? > > > > More mails will come ;-) > > > > > > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the >> results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving >> issues. Especially kind of "we need complete rework of this section" kind >> of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, >> but file any smaller issues under appropriate place in the New Design >> Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have >> to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, >> more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that >> with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on >> aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, but >> the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150220/850ca34b/attachment.html From lukas.fryc at gmail.com Fri Feb 20 07:52:09 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 20 Feb 2015 13:52:09 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: <54E60DEA.2040303@redhat.com> References: <54E4BFC5.3090002@redhat.com> <54E60DEA.2040303@redhat.com> Message-ID: On Thu, Feb 19, 2015 at 5:23 PM, Summers Pittman wrote: > On 02/19/2015 05:44 AM, Luk?? Fry? wrote: > > So First Steps guide can cover what are expectations from the user on > development environment side. It may just contain brief description of > prerequisites and few links where people may get more information. > > Then adding in a line "We expect you to know the basics of Android > development with Android Studio", including a link to Google's getting > started docs and having a section on what to add to the build.gradle files > with cross links to relevant user guides should be enough? That is the goal > of the JIRA issue at least right now. > Yep, that's sounds good. +1 to link to specific guides maybe with brief description what they contains > > It can also contain our preferred/opinionated way of Android > development, being it an IDE of our choice or whatever. > > I'm guessing I don't get to call Eclipse a miserable hell dimension from > which there is no escape one you enter? ;) > > Where should the building guide go? (Will need to make another JIRA for > that) > TBH It doesn't fit into site, I would put it into Github README / Wiki or so normally, but there is no Android umbrella repository. What about Gist? Or we can just make it a document on the site that will be linked just externally. > > > On Wed, Feb 18, 2015 at 5:37 PM, Summers Pittman > wrote: > >> On 02/18/2015 10:14 AM, Luk?? Fry? wrote: >> >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the >> results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving >> issues. Especially kind of "we need complete rework of this section" kind >> of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, >> >> I need to make a JIRA to change the Android section of first steps. >> There is no reason anyone should be compiling the Android library. However >> part of that will include moving the how to build the Android library >> docs. Where should those go? Also what should replace it? Getting >> started with he Android libraries is basically include the stuff you want >> in your build/pom and use it. >> >> Also, I noticed the getting started docs for Cordova include a lot of >> basic "what is cordova" flavored information. Should we really be >> concerned on the project page with teaching people how to use the platform? >> >> but file any smaller issues under appropriate place in the New Design >> Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have >> to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, >> more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that >> with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on >> aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, >> but the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> >> _______________________________________________ >> 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 >> > > > > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/f9d2bb77/attachment-0001.html From ivan.gurtler at ahead-itec.com Fri Feb 20 08:03:52 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 20 Feb 2015 14:03:52 +0100 Subject: [aerogear-dev] release question Message-ID: Hi, please when will new stable version of UnifiedPush server be released? Will release contain handling of raw notification for Windows Phone? Thanks *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/1fa8980f/attachment.html From lukas.fryc at gmail.com Fri Feb 20 08:08:48 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 20 Feb 2015 14:08:48 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: I agree on most of the objections, some are just leftovers, but let me react on selected issues: On Fri, Feb 20, 2015 at 10:10 AM, Matthias Wessendorf wrote: > > > # Startpage > > * annimation is nice, for the first time, but afterwards it's really > annoying > * version? That implies a version of AeroGear, which is not really existing > * I think the current startpage does a better job, listing the supported > platforms (*e.g. Android, iOS, Cordova or Windows) -> could we add logos > around the device images? > * clicking the arrow: nothing happens > * scrolling down, I see "Modules", "cross-platform" and "What is > happening". Not sure, but isn't that already a lot on the startpage? > I actually find it useful having it all there - you basically get complete overview of "What is AeroGear" on the start page: 1. mission: "Bringing mobile and enterprise together." 2. modules (features): Core, Security, Push, Sync 3. cross-platform nature: 4. links to News, Upcoming events, etc (shows project activity) It's all obvious and not necessary for us, but it is definitely useful for newcomers. When you go to the site repeatedly, you don't actually use start page anymore. The only important information for you is the Navigation. > > I think the big "Bringing mobile and enterprise together." is a bit too > big, but I am not sure how to make it more useful (in terms of containing > actual info). I looks nice, but the arrow is not working, and scrolling > down is _not_ obvious > > ## Modules > I wish this info was more visible. is it possible to do the fancy > annimation just once, and afterwards have minimized devices/logos, to get > an immediate overview of what AeroGear is offering (the modules)? > +1 I don't mind how it is now, but the true is that it is a bit unusual for a project site @Andres what you have some ideas here? We can hangout if handy... > > ## What's happening > Let's make that an extra tab? > > There already is this extra tab - News. That page automatically shows latest Activity from News, and I kinda like it, inspiration from here: http://arquillian.org/#activity > > > More mails will come ;-) > > > > > > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the >> results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving >> issues. Especially kind of "we need complete rework of this section" kind >> of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, >> but file any smaller issues under appropriate place in the New Design >> Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have >> to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, >> more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that >> with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on >> aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, but >> the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150220/88959b50/attachment.html From matzew at apache.org Fri Feb 20 08:19:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 14:19:27 +0100 Subject: [aerogear-dev] release question In-Reply-To: References: Message-ID: On Fri, Feb 20, 2015 at 2:03 PM, Ivan G?rtler wrote: > Hi, > > please when will new stable version of UnifiedPush server be released? > Hopefully next week, we will be able to start the release related work for 1.0.3 > Will release contain handling of raw notification for Windows Phone? > Nope, that's in 1.1.0 series (on master). Shortly after 1.0.3 there will be a 1.1.0-alpha.2 > > Thanks > > > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/a691bdeb/attachment.html From matzew at apache.org Fri Feb 20 08:39:05 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 14:39:05 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: A few more: * Modules -> what are the thoughts around having a TOC ? * Docs->Road Map --> should that be its own tab on the navigation bar? Not sure I'd really consider a roadmap as a doc (e.g. howto) On * Docs->API Documentation and Specifications It lists: AeroGearCore Specifications => IMO all of these for Android, iOS, Cordova and JavaScript are really API Docs, and not Specifications. Same for "AeroGearPush Specifications" On Fri, Feb 20, 2015 at 2:08 PM, Luk?? Fry? wrote: > I agree on most of the objections, some are just leftovers, but let me > react on selected issues: > > On Fri, Feb 20, 2015 at 10:10 AM, Matthias Wessendorf > wrote: >> >> >> # Startpage >> >> * annimation is nice, for the first time, but afterwards it's really >> annoying >> * version? That implies a version of AeroGear, which is not really >> existing >> * I think the current startpage does a better job, listing the supported >> platforms (*e.g. Android, iOS, Cordova or Windows) -> could we add logos >> around the device images? >> * clicking the arrow: nothing happens >> * scrolling down, I see "Modules", "cross-platform" and "What is >> happening". Not sure, but isn't that already a lot on the startpage? >> > > I actually find it useful having it all there - you basically get complete > overview of "What is AeroGear" on the start page: > 1. mission: "Bringing mobile and enterprise together." > 2. modules (features): Core, Security, Push, Sync > 3. cross-platform nature: > 4. links to News, Upcoming events, etc (shows project activity) > > It's all obvious and not necessary for us, but it is definitely useful for > newcomers. > > When you go to the site repeatedly, you don't actually use start page > anymore. The only important information for you is the Navigation. > > >> >> I think the big "Bringing mobile and enterprise together." is a bit too >> big, but I am not sure how to make it more useful (in terms of containing >> actual info). I looks nice, but the arrow is not working, and scrolling >> down is _not_ obvious >> >> ## Modules >> I wish this info was more visible. is it possible to do the fancy >> annimation just once, and afterwards have minimized devices/logos, to get >> an immediate overview of what AeroGear is offering (the modules)? >> > > +1 I don't mind how it is now, but the true is that it is a bit unusual > for a project site > > @Andres what you have some ideas here? We can hangout if handy... > > >> >> ## What's happening >> Let's make that an extra tab? >> >> > There already is this extra tab - News. > > That page automatically shows latest Activity from News, > and I kinda like it, inspiration from here: > > http://arquillian.org/#activity > > >> >> >> More mails will come ;-) >> >> >> >> >> >> >> On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: >> >>> Hey guys, >>> >>> the new site is in baking for a quite some time, but I believe the >>> results are already shaping up. The Big Thanks go to Andres off course! >>> >>> >>> I must say it is NOT COMPLETE yet, but I believe we can start receiving >>> issues. Especially kind of "we need complete rework of this section" kind >>> of issues ;-) >>> >>> http://staging-aerogearsite.rhcloud.com/ >>> >>> Please discuss bigger issues right here, >>> but file any smaller issues under appropriate place in the New Design >>> Epic: >>> >>> https://issues.jboss.org/browse/AEROGEAR-1546 >>> >>> >>> >>> Few bigger issues I identified and that I will need a help with: >>> >>> 1. filling in Core and Security landing pages >>> 2. Guides for First Steps are missing for some platforms (they don't >>> have to be overwhelmingly verbose, but at least we should have some) >>> 3. connected individual's blog to News page (powered by planet.jboss.org, >>> more info on IRC) >>> >>> >>> >>> >>> Few issues that we still need to tackle - I believe we can cover that >>> with Andres, but help is always welcomed! >>> >>> 1. make News page work javascript-wide (filtering, etc) [me] >>> 2. document how-to + style guide for drafting/posting new posts on >>> aerogear.org [me] >>> 2. style individual Guides >>> 3. style individual Posts >>> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >>> 5. grammar/typo corrections [Catherine offered help here] >>> >>> >>> Some features I planned originally will slip from the first release, but >>> the main priority now is get the New Site out! >>> >>> ETA: the site could be nearly production-ready end of this week. >>> >>> >>> Cheers, >>> >>> ~ Lukas >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/31c55696/attachment-0001.html From matzew at apache.org Fri Feb 20 08:48:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 20 Feb 2015 14:48:25 +0100 Subject: [aerogear-dev] AeroGear Core? (was: Re: New Site - Status) Message-ID: Hi, after reviewing the new sexy site, I am not sure I really like the "AeroGear Core". I think I have said that already before, when reviewing the drafts. I am wondering: Should we perhaps call it "AeroGear (powered) platforms" ? Let me give you an example, I really like the Cookbook section: http://staging-aerogearsite.rhcloud.com/getstarted/demos/#cookbooks It lists all of our cookbooks, like Android Cookbook iOS Cookbook Cordova Cookbook ... This makes sense - However, it would IMO read odd if that was Android Core Cookbook, iOS Core Cookbook. Speaking of 'core', we really have just one repo that has the name core in it: https://github.com/aerogear?query=core Another example, I think this page: http://staging-aerogearsite.rhcloud.com/docs/specs/ Would really read a bit nice if it said: AeroGear (powered) platform Specifications (or API Docs), listing all of our platforms - instead of just calling it CORE. Not sure, just some thoughts, after spending a morning on the site Greetings, Matthias On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > Hey guys, > > the new site is in baking for a quite some time, but I believe the results > are already shaping up. The Big Thanks go to Andres off course! > > > I must say it is NOT COMPLETE yet, but I believe we can start receiving > issues. Especially kind of "we need complete rework of this section" kind > of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > but file any smaller issues under appropriate place in the New Design Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they don't have > to be overwhelmingly verbose, but at least we should have some) > 3. connected individual's blog to News page (powered by planet.jboss.org, > more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover that with > Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first release, but > the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150220/59258d8d/attachment.html From scm.blanc at gmail.com Fri Feb 20 08:56:03 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 20 Feb 2015 14:56:03 +0100 Subject: [aerogear-dev] AeroGear Core? (was: Re: New Site - Status) In-Reply-To: References: Message-ID: +1 I always found this term "core" a bit odd On Fri, Feb 20, 2015 at 2:48 PM, Matthias Wessendorf wrote: > Hi, > > after reviewing the new sexy site, I am not sure I really like the > "AeroGear Core". I think I have said that already before, when reviewing > the drafts. > I am wondering: Should we perhaps call it "AeroGear (powered) platforms" ? > > Let me give you an example, I really like the Cookbook section: > http://staging-aerogearsite.rhcloud.com/getstarted/demos/#cookbooks > > It lists all of our cookbooks, like > Android Cookbook > iOS Cookbook > Cordova Cookbook > ... > > This makes sense - However, it would IMO read odd if that was Android Core > Cookbook, iOS Core Cookbook. Speaking of 'core', we really have just one > repo that has the name core in it: > https://github.com/aerogear?query=core > > Another example, I think this page: > http://staging-aerogearsite.rhcloud.com/docs/specs/ > > Would really read a bit nice if it said: > > AeroGear (powered) platform Specifications (or API Docs), listing all of > our platforms - instead of just calling it CORE. > > Not sure, just some thoughts, after spending a morning on the site > > Greetings, > Matthias > > > > > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the >> results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving >> issues. Especially kind of "we need complete rework of this section" kind >> of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, >> but file any smaller issues under appropriate place in the New Design >> Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have >> to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, >> more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that >> with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on >> aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, but >> the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150220/a8852199/attachment.html From lukas.fryc at gmail.com Fri Feb 20 08:56:56 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 20 Feb 2015 14:56:56 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: Message-ID: On Fri, Feb 20, 2015 at 10:29 AM, Matthias Wessendorf wrote: > Here area some comments for the push module > > > # Modules - Push > > * the overview has a view subsections: UnifiedPush, SimplePush, WebPush, > Roadmap, Get involved => is it possible to get a TOC at the righ hand side? > Yep, TOC to left hand side will it be. > * we have a link to all "push" repos, that is OK, but I'd also like to see > explict links to the repos of the servers (UnifiedPush, SimplePush, > WebPush), perhaps next to their sections? > We can either have: AeroGearPush + followed by links (as it is now) UnifiedPush Server + links SimplePush Server + links WebPush Server + links or just links under each specific server: AeroGear Push UnifiedPush Server + links SimplePush Server + links WebPush Server + links > * the documentation link jumps to the specs (For UPS that is API docs), > while the real doc (the UPS user guide) is not linked, on docs (I know it's > in the middle of the text somewhere below, but not explict linked) > We have link Documentation (meaning API Docs) and then link to Guides#push (could be just Guide and link directly to UPS Guide). Would be renaming to API Documentation sufficient? > > > ## guides (push) > https://issues.jboss.org/browse/AEROGEAR-1631 > > can't we have something like https://aerogear.org/docs/unifiedpush/ ? > that cleanly give an overview of all UPS related docs - instead of > overloading the Guides index page (it has a lot of stuff) > > * on large pages, like > http://staging-aerogearsite.rhcloud.com/docs/unifiedpush/ups_userguide/admin-ui/ > I miss a TOC > * we dont show the nice WARNING or INFO images anymore - here is one > example: > now: > https://aerogear.org/docs/unifiedpush/ups_userguide/overview/ > soon: > > http://staging-aerogearsite.rhcloud.com/docs/unifiedpush/ups_userguide/overview/ > > > > > > > > > > On Fri, Feb 20, 2015 at 10:10 AM, Matthias Wessendorf > wrote: > >> Hi Lukas and Andres, >> >> I have several comments, here are mine for the landing page (more to >> come): >> >> # Startpage >> >> * annimation is nice, for the first time, but afterwards it's really >> annoying >> * version? That implies a version of AeroGear, which is not really >> existing >> * I think the current startpage does a better job, listing the supported >> platforms (*e.g. Android, iOS, Cordova or Windows) -> could we add logos >> around the device images? >> * clicking the arrow: nothing happens >> * scrolling down, I see "Modules", "cross-platform" and "What is >> happening". Not sure, but isn't that already a lot on the startpage? >> >> I think the big "Bringing mobile and enterprise together." is a bit too >> big, but I am not sure how to make it more useful (in terms of containing >> actual info). I looks nice, but the arrow is not working, and scrolling >> down is _not_ obvious >> >> ## Modules >> I wish this info was more visible. is it possible to do the fancy >> annimation just once, and afterwards have minimized devices/logos, to get >> an immediate overview of what AeroGear is offering (the modules)? >> >> ## What's happening >> Let's make that an extra tab? >> >> >> >> More mails will come ;-) >> >> >> >> >> >> >> On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: >> >>> Hey guys, >>> >>> the new site is in baking for a quite some time, but I believe the >>> results are already shaping up. The Big Thanks go to Andres off course! >>> >>> >>> I must say it is NOT COMPLETE yet, but I believe we can start receiving >>> issues. Especially kind of "we need complete rework of this section" kind >>> of issues ;-) >>> >>> http://staging-aerogearsite.rhcloud.com/ >>> >>> Please discuss bigger issues right here, >>> but file any smaller issues under appropriate place in the New Design >>> Epic: >>> >>> https://issues.jboss.org/browse/AEROGEAR-1546 >>> >>> >>> >>> Few bigger issues I identified and that I will need a help with: >>> >>> 1. filling in Core and Security landing pages >>> 2. Guides for First Steps are missing for some platforms (they don't >>> have to be overwhelmingly verbose, but at least we should have some) >>> 3. connected individual's blog to News page (powered by planet.jboss.org, >>> more info on IRC) >>> >>> >>> >>> >>> Few issues that we still need to tackle - I believe we can cover that >>> with Andres, but help is always welcomed! >>> >>> 1. make News page work javascript-wide (filtering, etc) [me] >>> 2. document how-to + style guide for drafting/posting new posts on >>> aerogear.org [me] >>> 2. style individual Guides >>> 3. style individual Posts >>> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >>> 5. grammar/typo corrections [Catherine offered help here] >>> >>> >>> Some features I planned originally will slip from the first release, but >>> the main priority now is get the New Site out! >>> >>> ETA: the site could be nearly production-ready end of this week. >>> >>> >>> Cheers, >>> >>> ~ Lukas >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20150220/f40c7c92/attachment-0001.html From supittma at redhat.com Fri Feb 20 09:08:44 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 20 Feb 2015 09:08:44 -0500 Subject: [aerogear-dev] AeroGear Core? (was: Re: New Site - Status) In-Reply-To: References: Message-ID: <54E73FEC.5060600@redhat.com> On 02/20/2015 08:48 AM, Matthias Wessendorf wrote: > Hi, > > after reviewing the new sexy site, I am not sure I really like the > "AeroGear Core". I think I have said that already before, when > reviewing the drafts. > I am wondering: Should we perhaps call it "AeroGear (powered) > platforms" ? > > Let me give you an example, I really like the Cookbook section: > http://staging-aerogearsite.rhcloud.com/getstarted/demos/#cookbooks > > It lists all of our cookbooks, like > Android Cookbook > iOS Cookbook > Cordova Cookbook > ... > > This makes sense - However, it would IMO read odd if that was Android > Core Cookbook, iOS Core Cookbook. Speaking of 'core', we really have > just one repo that has the name core in it: > https://github.com/aerogear?query=core > > Another example, I think this page: > http://staging-aerogearsite.rhcloud.com/docs/specs/ > > Would really read a bit nice if it said: > > AeroGear (powered) platform Specifications (or API Docs), listing all > of our platforms - instead of just calling it CORE. > > Not sure, just some thoughts, after spending a morning on the site > +1 > Greetings, > Matthias > > > > > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? > wrote: > > Hey guys, > > the new site is in baking for a quite some time, but I believe the > results are already shaping up. The Big Thanks go to Andres off > course! > > > I must say it is NOT COMPLETE yet, but I believe we can start > receiving issues. Especially kind of "we need complete rework of > this section" kind of issues ;-) > > http://staging-aerogearsite.rhcloud.com/ > > Please discuss bigger issues right here, > but file any smaller issues under appropriate place in the New > Design Epic: > > https://issues.jboss.org/browse/AEROGEAR-1546 > > > > Few bigger issues I identified and that I will need a help with: > > 1. filling in Core and Security landing pages > 2. Guides for First Steps are missing for some platforms (they > don't have to be overwhelmingly verbose, but at least we should > have some) > 3. connected individual's blog to News page (powered by > planet.jboss.org , more info on IRC) > > > > > Few issues that we still need to tackle - I believe we can cover > that with Andres, but help is always welcomed! > > 1. make News page work javascript-wide (filtering, etc) [me] > 2. document how-to + style guide for drafting/posting new posts on > aerogear.org [me] > 2. style individual Guides > 3. style individual Posts > 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] > 5. grammar/typo corrections [Catherine offered help here] > > > Some features I planned originally will slip from the first > release, but the main priority now is get the New Site out! > > ETA: the site could be nearly production-ready end of this week. > > > Cheers, > > ~ Lukas > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150220/ab445cca/attachment.html From supittma at redhat.com Fri Feb 20 09:10:25 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 20 Feb 2015 09:10:25 -0500 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: <54E4BFC5.3090002@redhat.com> <54E60DEA.2040303@redhat.com> Message-ID: <54E74051.3020704@redhat.com> On 02/20/2015 07:52 AM, Luk?? Fry? wrote: > > On Thu, Feb 19, 2015 at 5:23 PM, Summers Pittman > wrote: > > On 02/19/2015 05:44 AM, Luk?? Fry? wrote: >> So First Steps guide can cover what are expectations from the >> user on development environment side. It may just contain brief >> description of prerequisites and few links where people may get >> more information. > Then adding in a line "We expect you to know the basics of Android > development with Android Studio", including a link to Google's > getting started docs and having a section on what to add to the > build.gradle files with cross links to relevant user guides should > be enough? That is the goal of the JIRA issue at least right now. > > > > Yep, that's sounds good. > > +1 to link to specific guides maybe with brief description what they > contains > > >> >> It can also contain our preferred/opinionated way of Android >> development, being it an IDE of our choice or whatever. > I'm guessing I don't get to call Eclipse a miserable hell > dimension from which there is no escape one you enter? ;) > > Where should the building guide go? (Will need to make another > JIRA for that) > > > TBH It doesn't fit into site, I would put it into Github README / Wiki > or so normally, but there is no Android umbrella repository. What > about Gist? > > Or we can just make it a document on the site that will be linked just > externally. Or we add it to the contribution section since setting up the build is one of the first things people will want to do. > > > >> >> On Wed, Feb 18, 2015 at 5:37 PM, Summers Pittman >> > wrote: >> >> On 02/18/2015 10:14 AM, Luk?? Fry? wrote: >>> Hey guys, >>> >>> the new site is in baking for a quite some time, but I >>> believe the results are already shaping up. The Big Thanks >>> go to Andres off course! >>> >>> >>> I must say it is NOT COMPLETE yet, but I believe we can >>> start receiving issues. Especially kind of "we need complete >>> rework of this section" kind of issues ;-) >>> >>> http://staging-aerogearsite.rhcloud.com/ >>> >>> Please discuss bigger issues right here, >> I need to make a JIRA to change the Android section of first >> steps. There is no reason anyone should be compiling the >> Android library. However part of that will include moving >> the how to build the Android library docs. Where should >> those go? Also what should replace it? Getting started with >> he Android libraries is basically include the stuff you want >> in your build/pom and use it. >> >> Also, I noticed the getting started docs for Cordova include >> a lot of basic "what is cordova" flavored information. >> Should we really be concerned on the project page with >> teaching people how to use the platform? >>> but file any smaller issues under appropriate place in the >>> New Design Epic: >>> >>> https://issues.jboss.org/browse/AEROGEAR-1546 >>> >>> >>> >>> Few bigger issues I identified and that I will need a help with: >>> >>> 1. filling in Core and Security landing pages >>> 2. Guides for First Steps are missing for some platforms >>> (they don't have to be overwhelmingly verbose, but at least >>> we should have some) >>> 3. connected individual's blog to News page (powered by >>> planet.jboss.org , more info on IRC) >>> >>> >>> >>> >>> Few issues that we still need to tackle - I believe we can >>> cover that with Andres, but help is always welcomed! >>> >>> 1. make News page work javascript-wide (filtering, etc) [me] >>> 2. document how-to + style guide for drafting/posting new >>> posts on aerogear.org [me] >>> 2. style individual Guides >>> 3. style individual Posts >>> 4. HTML structure corrections (e.g. wrong use of HTML tags) >>> [Andres] >>> 5. grammar/typo corrections [Catherine offered help here] >>> >>> >>> Some features I planned originally will slip from the first >>> release, but the main priority now is get the New Site out! >>> >>> ETA: the site could be nearly production-ready end of this week. >>> >>> >>> Cheers, >>> >>> ~ Lukas >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> -- >> Summers Pittman >> >>Phone:404 941 4698 >> >>Java is my crack. >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- 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/20150220/38c0c926/attachment-0001.html From daniel.bevenius at gmail.com Sun Feb 22 07:22:45 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 22 Feb 2015 13:22:45 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150223 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150222/9dee586e/attachment.html From lukas.fryc at gmail.com Mon Feb 23 06:50:25 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 23 Feb 2015 12:50:25 +0100 Subject: [aerogear-dev] AeroGear Core? (was: Re: New Site - Status) In-Reply-To: <54E73FEC.5060600@redhat.com> References: <54E73FEC.5060600@redhat.com> Message-ID: I agree with that update, but to make it clear, the intention would be a) just rename AeroGear Core to AeroGear Platforms (on the Home page and under Modules dropdown) b) or rather create a new structure alongside Modules, such as new dropdown menu in the Navbar? ~~~ I personally like b), which would reuse our platform landing pages: https://aerogear.org/android/ https://aerogear.org/ios/ https://aerogear.org/cordova/ https://aerogear.org/javascript/ It would leaves us with just 3 modules: Push, Sync and Security. I've created https://issues.jboss.org/browse/AEROGEAR-1634 to cover this. Description TBD - will reflect what we conclude here. On Fri, Feb 20, 2015 at 3:08 PM, Summers Pittman wrote: > On 02/20/2015 08:48 AM, Matthias Wessendorf wrote: > > Hi, > > after reviewing the new sexy site, I am not sure I really like the > "AeroGear Core". I think I have said that already before, when reviewing > the drafts. > I am wondering: Should we perhaps call it "AeroGear (powered) platforms" ? > > Let me give you an example, I really like the Cookbook section: > http://staging-aerogearsite.rhcloud.com/getstarted/demos/#cookbooks > > It lists all of our cookbooks, like > Android Cookbook > iOS Cookbook > Cordova Cookbook > ... > > This makes sense - However, it would IMO read odd if that was Android > Core Cookbook, iOS Core Cookbook. Speaking of 'core', we really have just > one repo that has the name core in it: > https://github.com/aerogear?query=core > > Another example, I think this page: > http://staging-aerogearsite.rhcloud.com/docs/specs/ > > Would really read a bit nice if it said: > > AeroGear (powered) platform Specifications (or API Docs), listing all of > our platforms - instead of just calling it CORE. > > Not sure, just some thoughts, after spending a morning on the site > > +1 > > Greetings, > Matthias > > > > > > On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> the new site is in baking for a quite some time, but I believe the >> results are already shaping up. The Big Thanks go to Andres off course! >> >> >> I must say it is NOT COMPLETE yet, but I believe we can start receiving >> issues. Especially kind of "we need complete rework of this section" kind >> of issues ;-) >> >> http://staging-aerogearsite.rhcloud.com/ >> >> Please discuss bigger issues right here, >> but file any smaller issues under appropriate place in the New Design >> Epic: >> >> https://issues.jboss.org/browse/AEROGEAR-1546 >> >> >> >> Few bigger issues I identified and that I will need a help with: >> >> 1. filling in Core and Security landing pages >> 2. Guides for First Steps are missing for some platforms (they don't have >> to be overwhelmingly verbose, but at least we should have some) >> 3. connected individual's blog to News page (powered by planet.jboss.org, >> more info on IRC) >> >> >> >> >> Few issues that we still need to tackle - I believe we can cover that >> with Andres, but help is always welcomed! >> >> 1. make News page work javascript-wide (filtering, etc) [me] >> 2. document how-to + style guide for drafting/posting new posts on >> aerogear.org [me] >> 2. style individual Guides >> 3. style individual Posts >> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >> 5. grammar/typo corrections [Catherine offered help here] >> >> >> Some features I planned originally will slip from the first release, >> but the main priority now is get the New Site out! >> >> ETA: the site could be nearly production-ready end of this week. >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/6521d08d/attachment.html From ivan.gurtler at ahead-itec.com Mon Feb 23 07:29:01 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Mon, 23 Feb 2015 13:29:01 +0100 Subject: [aerogear-dev] master branch - maven install - error Message-ID: Hi, I downloaded zip from ... https://github.com/aerogear/aerogear-unifiedpush-server ... import as maven project ... but I am facing some problem ... when I run maven install... [INFO] ------------------------------------------------------------------------ [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ unifiedpush-admin-ui --- [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ unifiedpush-admin-ui --- [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ unifiedpush-admin-ui --- [INFO] [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ unifiedpush-admin-ui --- [INFO] [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ unifiedpush-admin-ui --- [INFO] [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install node and npm) @ unifiedpush-admin-ui --- [INFO] Node v0.10.31 is already installed. [INFO] Found NPM version 1.4.23 [INFO] [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ unifiedpush-admin-ui --- [INFO] Running 'npm install --color=false' in C:\Users\Ivan\Documents\Aerogear projects\aerogear-unifiedpush-server-master\admin-ui [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data requires mime@'~1.2.11' but will load [INFO] npm WARN unmet dependency undefined, [INFO] npm WARN unmet dependency which is version undefined [INFO] [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ unifiedpush-admin-ui --- [INFO] Running 'grunt dist --no-color' in C:\Users\Ivan\Documents\Aerogear projects\aerogear-unifiedpush-server-master\admin-ui [INFO] Loading "bower_task.js" tasks...ERROR [INFO] >> Error: Cannot find module 'mime' [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? [INFO] Warning: Task "bower:install" not found. Use --force to continue. [INFO] [INFO] Aborted due to warnings. [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ 2.020 s] [INFO] UnifiedPush Model Layer ............................ SUCCESS [ 0.077 s] [INFO] UnifiedPush Server Model API ....................... SUCCESS [ 2.958 s] [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ 12.992 s] [INFO] UnifiedPush Service Layer .......................... SUCCESS [ 17.831 s] [INFO] UnifiedPush Sender Module .......................... SUCCESS [ 0.066 s] [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ 2.369 s] [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ 3.585 s] [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ 5.240 s] [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ 4.898 s] [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: 53.305 s [INFO] Finished at: 2015-02-23T13:01:24+01:00 [INFO] Final Memory: 98M/635M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' failed. (error code 3) -> [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/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :unifiedpush-admin-ui Thanks for help *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/6e979e7e/attachment-0001.html From matzew at apache.org Mon Feb 23 07:32:22 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 13:32:22 +0100 Subject: [aerogear-dev] AeroGear Core? (was: Re: New Site - Status) In-Reply-To: References: <54E73FEC.5060600@redhat.com> Message-ID: On Monday, February 23, 2015, Luk?? Fry? wrote: > I agree with that update, > > but to make it clear, the intention would be > > a) just rename AeroGear Core to AeroGear Platforms (on the Home page and > under Modules dropdown) > b) or rather create a new structure alongside Modules, such as new > dropdown menu in the Navbar? > > ~~~ > > I personally like b), which would reuse our platform landing pages: > https://aerogear.org/android/ > https://aerogear.org/ios/ > https://aerogear.org/cordova/ > https://aerogear.org/javascript/ > > It would leaves us with just 3 modules: Push, Sync and Security. > yes, I do like that > > > I've created https://issues.jboss.org/browse/AEROGEAR-1634 to cover this. > Description TBD - will reflect what we conclude here. > > On Fri, Feb 20, 2015 at 3:08 PM, Summers Pittman > wrote: > >> On 02/20/2015 08:48 AM, Matthias Wessendorf wrote: >> >> Hi, >> >> after reviewing the new sexy site, I am not sure I really like the >> "AeroGear Core". I think I have said that already before, when reviewing >> the drafts. >> I am wondering: Should we perhaps call it "AeroGear (powered) platforms" >> ? >> >> Let me give you an example, I really like the Cookbook section: >> http://staging-aerogearsite.rhcloud.com/getstarted/demos/#cookbooks >> >> It lists all of our cookbooks, like >> Android Cookbook >> iOS Cookbook >> Cordova Cookbook >> ... >> >> This makes sense - However, it would IMO read odd if that was Android >> Core Cookbook, iOS Core Cookbook. Speaking of 'core', we really have just >> one repo that has the name core in it: >> https://github.com/aerogear?query=core >> >> Another example, I think this page: >> http://staging-aerogearsite.rhcloud.com/docs/specs/ >> >> Would really read a bit nice if it said: >> >> AeroGear (powered) platform Specifications (or API Docs), listing all >> of our platforms - instead of just calling it CORE. >> >> Not sure, just some thoughts, after spending a morning on the site >> >> +1 >> >> Greetings, >> Matthias >> >> >> >> >> >> On Wed, Feb 18, 2015 at 4:14 PM, Luk?? Fry? > > wrote: >> >>> Hey guys, >>> >>> the new site is in baking for a quite some time, but I believe the >>> results are already shaping up. The Big Thanks go to Andres off course! >>> >>> >>> I must say it is NOT COMPLETE yet, but I believe we can start >>> receiving issues. Especially kind of "we need complete rework of this >>> section" kind of issues ;-) >>> >>> http://staging-aerogearsite.rhcloud.com/ >>> >>> Please discuss bigger issues right here, >>> but file any smaller issues under appropriate place in the New Design >>> Epic: >>> >>> https://issues.jboss.org/browse/AEROGEAR-1546 >>> >>> >>> >>> Few bigger issues I identified and that I will need a help with: >>> >>> 1. filling in Core and Security landing pages >>> 2. Guides for First Steps are missing for some platforms (they don't >>> have to be overwhelmingly verbose, but at least we should have some) >>> 3. connected individual's blog to News page (powered by planet.jboss.org, >>> more info on IRC) >>> >>> >>> >>> >>> Few issues that we still need to tackle - I believe we can cover that >>> with Andres, but help is always welcomed! >>> >>> 1. make News page work javascript-wide (filtering, etc) [me] >>> 2. document how-to + style guide for drafting/posting new posts on >>> aerogear.org [me] >>> 2. style individual Guides >>> 3. style individual Posts >>> 4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres] >>> 5. grammar/typo corrections [Catherine offered help here] >>> >>> >>> Some features I planned originally will slip from the first release, >>> but the main priority now is get the New Site out! >>> >>> ETA: the site could be nearly production-ready end of this week. >>> >>> >>> Cheers, >>> >>> ~ Lukas >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/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.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 >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/c9128fa7/attachment.html From matzew at apache.org Mon Feb 23 07:54:24 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 13:54:24 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: the node/npm thing fails randomly for me as well. try running the mvn build again ;-( On Monday, February 23, 2015, Ivan G?rtler wrote: > > Hi, > > I downloaded zip from ... > https://github.com/aerogear/aerogear-unifiedpush-server ... import as > maven project ... > but I am facing some problem ... when I run maven install... > > [INFO] > ------------------------------------------------------------------------ > [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ > unifiedpush-admin-ui --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ > unifiedpush-admin-ui --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ > unifiedpush-admin-ui --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp > (get-build-timestamp) @ unifiedpush-admin-ui --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ > unifiedpush-admin-ui --- > [INFO] > [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install node > and npm) @ unifiedpush-admin-ui --- > [INFO] Node v0.10.31 is already installed. > [INFO] Found NPM version 1.4.23 > [INFO] > [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ > unifiedpush-admin-ui --- > [INFO] Running 'npm install --color=false' in > C:\Users\Ivan\Documents\Aerogear > projects\aerogear-unifiedpush-server-master\admin-ui > [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear > projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data > requires mime@'~1.2.11' but will load > [INFO] npm WARN unmet dependency undefined, > [INFO] npm WARN unmet dependency which is version undefined > [INFO] > [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ > unifiedpush-admin-ui --- > [INFO] Running 'grunt dist --no-color' in C:\Users\Ivan\Documents\Aerogear > projects\aerogear-unifiedpush-server-master\admin-ui > [INFO] Loading "bower_task.js" tasks...ERROR > [INFO] >> Error: Cannot find module 'mime' > [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? > [INFO] Warning: Task "bower:install" not found. Use --force to continue. > [INFO] > [INFO] Aborted due to warnings. > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ > 2.020 s] > [INFO] UnifiedPush Model Layer ............................ SUCCESS [ > 0.077 s] > [INFO] UnifiedPush Server Model API ....................... SUCCESS [ > 2.958 s] > [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ > 12.992 s] > [INFO] UnifiedPush Service Layer .......................... SUCCESS [ > 17.831 s] > [INFO] UnifiedPush Sender Module .......................... SUCCESS [ > 0.066 s] > [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ > 2.369 s] > [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ > 3.585 s] > [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ > 5.240 s] > [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ > 4.898 s] > [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: 53.305 s > [INFO] Finished at: 2015-02-23T13:01:24+01:00 > [INFO] Final Memory: 98M/635M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on > project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' > failed. (error code 3) -> [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/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :unifiedpush-admin-ui > > > > Thanks for help > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/6697fcdc/attachment-0001.html From ivan.gurtler at ahead-itec.com Mon Feb 23 08:06:07 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Mon, 23 Feb 2015 14:06:07 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: I try it 10 times :-D ... but always with error *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : > the node/npm thing fails randomly for me as well. try running the mvn > build again ;-( > > > On Monday, February 23, 2015, Ivan G?rtler > wrote: > >> >> Hi, >> >> I downloaded zip from ... >> https://github.com/aerogear/aerogear-unifiedpush-server ... import as >> maven project ... >> but I am facing some problem ... when I run maven install... >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] >> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ >> unifiedpush-admin-ui --- >> [INFO] >> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ >> unifiedpush-admin-ui --- >> [INFO] >> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >> unifiedpush-admin-ui --- >> [INFO] >> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >> (get-build-timestamp) @ unifiedpush-admin-ui --- >> [INFO] >> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >> unifiedpush-admin-ui --- >> [INFO] >> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install >> node and npm) @ unifiedpush-admin-ui --- >> [INFO] Node v0.10.31 is already installed. >> [INFO] Found NPM version 1.4.23 >> [INFO] >> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >> unifiedpush-admin-ui --- >> [INFO] Running 'npm install --color=false' in >> C:\Users\Ivan\Documents\Aerogear >> projects\aerogear-unifiedpush-server-master\admin-ui >> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >> requires mime@'~1.2.11' but will load >> [INFO] npm WARN unmet dependency undefined, >> [INFO] npm WARN unmet dependency which is version undefined >> [INFO] >> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >> unifiedpush-admin-ui --- >> [INFO] Running 'grunt dist --no-color' in >> C:\Users\Ivan\Documents\Aerogear >> projects\aerogear-unifiedpush-server-master\admin-ui >> [INFO] Loading "bower_task.js" tasks...ERROR >> [INFO] >> Error: Cannot find module 'mime' >> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >> [INFO] Warning: Task "bower:install" not found. Use --force to continue. >> [INFO] >> [INFO] Aborted due to warnings. >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ >> 2.020 s] >> [INFO] UnifiedPush Model Layer ............................ SUCCESS [ >> 0.077 s] >> [INFO] UnifiedPush Server Model API ....................... SUCCESS [ >> 2.958 s] >> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ >> 12.992 s] >> [INFO] UnifiedPush Service Layer .......................... SUCCESS [ >> 17.831 s] >> [INFO] UnifiedPush Sender Module .......................... SUCCESS [ >> 0.066 s] >> [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ >> 2.369 s] >> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ >> 3.585 s] >> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ >> 5.240 s] >> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ >> 4.898 s] >> [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: 53.305 s >> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >> [INFO] Final Memory: 98M/635M >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal >> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >> failed. (error code 3) -> [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/MojoFailureException >> [ERROR] >> [ERROR] After correcting the problems, you can resume the build with the >> command >> [ERROR] mvn -rf :unifiedpush-admin-ui >> >> >> >> Thanks for help >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> > > > -- > 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/20150223/776e929d/attachment.html From matzew at apache.org Mon Feb 23 08:18:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 14:18:01 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler wrote: > I try it 10 times :-D ... but always with error > lol - sorry to hear. what operating system are you on ? > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : > >> the node/npm thing fails randomly for me as well. try running the mvn >> build again ;-( >> >> >> On Monday, February 23, 2015, Ivan G?rtler >> wrote: >> >>> >>> Hi, >>> >>> I downloaded zip from ... >>> https://github.com/aerogear/aerogear-unifiedpush-server ... import as >>> maven project ... >>> but I am facing some problem ... when I run maven install... >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] >>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ >>> unifiedpush-admin-ui --- >>> [INFO] >>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ >>> unifiedpush-admin-ui --- >>> [INFO] >>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>> unifiedpush-admin-ui --- >>> [INFO] >>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>> [INFO] >>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >>> unifiedpush-admin-ui --- >>> [INFO] >>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install >>> node and npm) @ unifiedpush-admin-ui --- >>> [INFO] Node v0.10.31 is already installed. >>> [INFO] Found NPM version 1.4.23 >>> [INFO] >>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>> unifiedpush-admin-ui --- >>> [INFO] Running 'npm install --color=false' in >>> C:\Users\Ivan\Documents\Aerogear >>> projects\aerogear-unifiedpush-server-master\admin-ui >>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>> requires mime@'~1.2.11' but will load >>> [INFO] npm WARN unmet dependency undefined, >>> [INFO] npm WARN unmet dependency which is version undefined >>> [INFO] >>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>> unifiedpush-admin-ui --- >>> [INFO] Running 'grunt dist --no-color' in >>> C:\Users\Ivan\Documents\Aerogear >>> projects\aerogear-unifiedpush-server-master\admin-ui >>> [INFO] Loading "bower_task.js" tasks...ERROR >>> [INFO] >> Error: Cannot find module 'mime' >>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>> [INFO] Warning: Task "bower:install" not found. Use --force to continue. >>> [INFO] >>> [INFO] Aborted due to warnings. >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Reactor Summary: >>> [INFO] >>> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ >>> 2.020 s] >>> [INFO] UnifiedPush Model Layer ............................ SUCCESS [ >>> 0.077 s] >>> [INFO] UnifiedPush Server Model API ....................... SUCCESS [ >>> 2.958 s] >>> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ >>> 12.992 s] >>> [INFO] UnifiedPush Service Layer .......................... SUCCESS [ >>> 17.831 s] >>> [INFO] UnifiedPush Sender Module .......................... SUCCESS [ >>> 0.066 s] >>> [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ >>> 2.369 s] >>> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ >>> 3.585 s] >>> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ >>> 5.240 s] >>> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ >>> 4.898 s] >>> [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: 53.305 s >>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>> [INFO] Final Memory: 98M/635M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal >>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>> failed. (error code 3) -> [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/MojoFailureException >>> [ERROR] >>> [ERROR] After correcting the problems, you can resume the build with the >>> command >>> [ERROR] mvn -rf :unifiedpush-admin-ui >>> >>> >>> >>> Thanks for help >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >> >> >> -- >> 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/20150223/f2437573/attachment-0001.html From matzew at apache.org Mon Feb 23 08:18:23 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 14:18:23 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: Oh, windows - I see ... On Mon, Feb 23, 2015 at 2:18 PM, Matthias Wessendorf wrote: > > > On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler > wrote: > >> I try it 10 times :-D ... but always with error >> > > lol - sorry to hear. > > what operating system are you on ? > > >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : >> >>> the node/npm thing fails randomly for me as well. try running the mvn >>> build again ;-( >>> >>> >>> On Monday, February 23, 2015, Ivan G?rtler >>> wrote: >>> >>>> >>>> Hi, >>>> >>>> I downloaded zip from ... >>>> https://github.com/aerogear/aerogear-unifiedpush-server ... import as >>>> maven project ... >>>> but I am facing some problem ... when I run maven install... >>>> >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] >>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ >>>> unifiedpush-admin-ui --- >>>> [INFO] >>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) >>>> @ unifiedpush-admin-ui --- >>>> [INFO] >>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>>> unifiedpush-admin-ui --- >>>> [INFO] >>>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>>> [INFO] >>>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >>>> unifiedpush-admin-ui --- >>>> [INFO] >>>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install >>>> node and npm) @ unifiedpush-admin-ui --- >>>> [INFO] Node v0.10.31 is already installed. >>>> [INFO] Found NPM version 1.4.23 >>>> [INFO] >>>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>>> unifiedpush-admin-ui --- >>>> [INFO] Running 'npm install --color=false' in >>>> C:\Users\Ivan\Documents\Aerogear >>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>>> requires mime@'~1.2.11' but will load >>>> [INFO] npm WARN unmet dependency undefined, >>>> [INFO] npm WARN unmet dependency which is version undefined >>>> [INFO] >>>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>>> unifiedpush-admin-ui --- >>>> [INFO] Running 'grunt dist --no-color' in >>>> C:\Users\Ivan\Documents\Aerogear >>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>> [INFO] Loading "bower_task.js" tasks...ERROR >>>> [INFO] >> Error: Cannot find module 'mime' >>>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>>> [INFO] Warning: Task "bower:install" not found. Use --force to continue. >>>> [INFO] >>>> [INFO] Aborted due to warnings. >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Reactor Summary: >>>> [INFO] >>>> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ >>>> 2.020 s] >>>> [INFO] UnifiedPush Model Layer ............................ SUCCESS [ >>>> 0.077 s] >>>> [INFO] UnifiedPush Server Model API ....................... SUCCESS [ >>>> 2.958 s] >>>> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ >>>> 12.992 s] >>>> [INFO] UnifiedPush Service Layer .......................... SUCCESS [ >>>> 17.831 s] >>>> [INFO] UnifiedPush Sender Module .......................... SUCCESS [ >>>> 0.066 s] >>>> [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ >>>> 2.369 s] >>>> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ >>>> 3.585 s] >>>> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ >>>> 5.240 s] >>>> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ >>>> 4.898 s] >>>> [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: 53.305 s >>>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>>> [INFO] Final Memory: 98M/635M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] Failed to execute goal >>>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>>> failed. (error code 3) -> [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/MojoFailureException >>>> [ERROR] >>>> [ERROR] After correcting the problems, you can resume the build with >>>> the command >>>> [ERROR] mvn -rf :unifiedpush-admin-ui >>>> >>>> >>>> >>>> Thanks for help >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>> >>> >>> -- >>> 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/ecfc1e9a/attachment.html From ivan.gurtler at ahead-itec.com Mon Feb 23 08:35:42 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Mon, 23 Feb 2015 14:35:42 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: yes :D win 8.1 ... but when I downloaded lower version (alpha1) source code ... mvn install is ok ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-23 14:18 GMT+01:00 Matthias Wessendorf : > Oh, windows - I see ... > > On Mon, Feb 23, 2015 at 2:18 PM, Matthias Wessendorf > wrote: > >> >> >> On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> I try it 10 times :-D ... but always with error >>> >> >> lol - sorry to hear. >> >> what operating system are you on ? >> >> >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : >>> >>>> the node/npm thing fails randomly for me as well. try running the mvn >>>> build again ;-( >>>> >>>> >>>> On Monday, February 23, 2015, Ivan G?rtler >>>> wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> I downloaded zip from ... >>>>> https://github.com/aerogear/aerogear-unifiedpush-server ... import as >>>>> maven project ... >>>>> but I am facing some problem ... when I run maven install... >>>>> >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] >>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) >>>>> @ unifiedpush-admin-ui --- >>>>> [INFO] >>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) >>>>> @ unifiedpush-admin-ui --- >>>>> [INFO] >>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>>>> unifiedpush-admin-ui --- >>>>> [INFO] >>>>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>>>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>>>> [INFO] >>>>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >>>>> unifiedpush-admin-ui --- >>>>> [INFO] >>>>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install >>>>> node and npm) @ unifiedpush-admin-ui --- >>>>> [INFO] Node v0.10.31 is already installed. >>>>> [INFO] Found NPM version 1.4.23 >>>>> [INFO] >>>>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>>>> unifiedpush-admin-ui --- >>>>> [INFO] Running 'npm install --color=false' in >>>>> C:\Users\Ivan\Documents\Aerogear >>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>>>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>>>> requires mime@'~1.2.11' but will load >>>>> [INFO] npm WARN unmet dependency undefined, >>>>> [INFO] npm WARN unmet dependency which is version undefined >>>>> [INFO] >>>>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>>>> unifiedpush-admin-ui --- >>>>> [INFO] Running 'grunt dist --no-color' in >>>>> C:\Users\Ivan\Documents\Aerogear >>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>> [INFO] Loading "bower_task.js" tasks...ERROR >>>>> [INFO] >> Error: Cannot find module 'mime' >>>>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>>>> [INFO] Warning: Task "bower:install" not found. Use --force to >>>>> continue. >>>>> [INFO] >>>>> [INFO] Aborted due to warnings. >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] Reactor Summary: >>>>> [INFO] >>>>> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ >>>>> 2.020 s] >>>>> [INFO] UnifiedPush Model Layer ............................ SUCCESS [ >>>>> 0.077 s] >>>>> [INFO] UnifiedPush Server Model API ....................... SUCCESS [ >>>>> 2.958 s] >>>>> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ >>>>> 12.992 s] >>>>> [INFO] UnifiedPush Service Layer .......................... SUCCESS [ >>>>> 17.831 s] >>>>> [INFO] UnifiedPush Sender Module .......................... SUCCESS [ >>>>> 0.066 s] >>>>> [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ >>>>> 2.369 s] >>>>> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ >>>>> 3.585 s] >>>>> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ >>>>> 5.240 s] >>>>> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ >>>>> 4.898 s] >>>>> [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: 53.305 s >>>>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>>>> [INFO] Final Memory: 98M/635M >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [ERROR] Failed to execute goal >>>>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>>>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>>>> failed. (error code 3) -> [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/MojoFailureException >>>>> [ERROR] >>>>> [ERROR] After correcting the problems, you can resume the build with >>>>> the command >>>>> [ERROR] mvn -rf :unifiedpush-admin-ui >>>>> >>>>> >>>>> >>>>> Thanks for help >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>> >>>> >>>> -- >>>> 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 >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150223/abbddd21/attachment-0001.html From scm.blanc at gmail.com Mon Feb 23 08:43:12 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 23 Feb 2015 14:43:12 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: I can build master under Windows 8.1, I did not have the issue. Really strange and annoying issue. On Mon, Feb 23, 2015 at 2:35 PM, Ivan G?rtler wrote: > yes :D win 8.1 ... but when I downloaded lower version (alpha1) source > code ... mvn install is ok ... > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-23 14:18 GMT+01:00 Matthias Wessendorf : > >> Oh, windows - I see ... >> >> On Mon, Feb 23, 2015 at 2:18 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> I try it 10 times :-D ... but always with error >>>> >>> >>> lol - sorry to hear. >>> >>> what operating system are you on ? >>> >>> >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : >>>> >>>>> the node/npm thing fails randomly for me as well. try running the mvn >>>>> build again ;-( >>>>> >>>>> >>>>> On Monday, February 23, 2015, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> I downloaded zip from ... >>>>>> https://github.com/aerogear/aerogear-unifiedpush-server ... import >>>>>> as maven project ... >>>>>> but I am facing some problem ... when I run maven install... >>>>>> >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] >>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) >>>>>> @ unifiedpush-admin-ui --- >>>>>> [INFO] >>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>> (enforce-maven-version) @ unifiedpush-admin-ui --- >>>>>> [INFO] >>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>>>>> unifiedpush-admin-ui --- >>>>>> [INFO] >>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>>>>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>>>>> [INFO] >>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >>>>>> unifiedpush-admin-ui --- >>>>>> [INFO] >>>>>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm (install >>>>>> node and npm) @ unifiedpush-admin-ui --- >>>>>> [INFO] Node v0.10.31 is already installed. >>>>>> [INFO] Found NPM version 1.4.23 >>>>>> [INFO] >>>>>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>>>>> unifiedpush-admin-ui --- >>>>>> [INFO] Running 'npm install --color=false' in >>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>>>>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>>>>> requires mime@'~1.2.11' but will load >>>>>> [INFO] npm WARN unmet dependency undefined, >>>>>> [INFO] npm WARN unmet dependency which is version undefined >>>>>> [INFO] >>>>>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>>>>> unifiedpush-admin-ui --- >>>>>> [INFO] Running 'grunt dist --no-color' in >>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>> [INFO] Loading "bower_task.js" tasks...ERROR >>>>>> [INFO] >> Error: Cannot find module 'mime' >>>>>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>>>>> [INFO] Warning: Task "bower:install" not found. Use --force to >>>>>> continue. >>>>>> [INFO] >>>>>> [INFO] Aborted due to warnings. >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Reactor Summary: >>>>>> [INFO] >>>>>> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS [ >>>>>> 2.020 s] >>>>>> [INFO] UnifiedPush Model Layer ............................ SUCCESS [ >>>>>> 0.077 s] >>>>>> [INFO] UnifiedPush Server Model API ....................... SUCCESS [ >>>>>> 2.958 s] >>>>>> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS [ >>>>>> 12.992 s] >>>>>> [INFO] UnifiedPush Service Layer .......................... SUCCESS [ >>>>>> 17.831 s] >>>>>> [INFO] UnifiedPush Sender Module .......................... SUCCESS [ >>>>>> 0.066 s] >>>>>> [INFO] UnifiedPush Push Message Model ..................... SUCCESS [ >>>>>> 2.369 s] >>>>>> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS [ >>>>>> 3.585 s] >>>>>> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS [ >>>>>> 5.240 s] >>>>>> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE [ >>>>>> 4.898 s] >>>>>> [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: 53.305 s >>>>>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>>>>> [INFO] Final Memory: 98M/635M >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [ERROR] Failed to execute goal >>>>>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>>>>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>>>>> failed. (error code 3) -> [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/MojoFailureException >>>>>> [ERROR] >>>>>> [ERROR] After correcting the problems, you can resume the build with >>>>>> the command >>>>>> [ERROR] mvn -rf :unifiedpush-admin-ui >>>>>> >>>>>> >>>>>> >>>>>> Thanks for help >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150223/837d15fc/attachment.html From ivan.gurtler at ahead-itec.com Mon Feb 23 08:54:48 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Mon, 23 Feb 2015 14:54:48 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: after download alpha1 version and mvn instal ... everything OK ... I downloaded master again .... and after import master and mvn install everthing is OK ... it was strange ... Thanks for your help *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-23 14:43 GMT+01:00 Sebastien Blanc : > I can build master under Windows 8.1, I did not have the issue. Really > strange and annoying issue. > > > On Mon, Feb 23, 2015 at 2:35 PM, Ivan G?rtler > wrote: > >> yes :D win 8.1 ... but when I downloaded lower version (alpha1) source >> code ... mvn install is ok ... >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-23 14:18 GMT+01:00 Matthias Wessendorf : >> >>> Oh, windows - I see ... >>> >>> On Mon, Feb 23, 2015 at 2:18 PM, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler < >>>> ivan.gurtler at ahead-itec.com> wrote: >>>> >>>>> I try it 10 times :-D ... but always with error >>>>> >>>> >>>> lol - sorry to hear. >>>> >>>> what operating system are you on ? >>>> >>>> >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>>> 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : >>>>> >>>>>> the node/npm thing fails randomly for me as well. try running the mvn >>>>>> build again ;-( >>>>>> >>>>>> >>>>>> On Monday, February 23, 2015, Ivan G?rtler < >>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I downloaded zip from ... >>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server ... import >>>>>>> as maven project ... >>>>>>> but I am facing some problem ... when I run maven install... >>>>>>> >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] >>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>>> (enforce-java-version) @ unifiedpush-admin-ui --- >>>>>>> [INFO] >>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>>> (enforce-maven-version) @ unifiedpush-admin-ui --- >>>>>>> [INFO] >>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>>>>>> unifiedpush-admin-ui --- >>>>>>> [INFO] >>>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>>>>>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>>>>>> [INFO] >>>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >>>>>>> unifiedpush-admin-ui --- >>>>>>> [INFO] >>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm >>>>>>> (install node and npm) @ unifiedpush-admin-ui --- >>>>>>> [INFO] Node v0.10.31 is already installed. >>>>>>> [INFO] Found NPM version 1.4.23 >>>>>>> [INFO] >>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>>>>>> unifiedpush-admin-ui --- >>>>>>> [INFO] Running 'npm install --color=false' in >>>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>>>>>> requires mime@'~1.2.11' but will load >>>>>>> [INFO] npm WARN unmet dependency undefined, >>>>>>> [INFO] npm WARN unmet dependency which is version undefined >>>>>>> [INFO] >>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>>>>>> unifiedpush-admin-ui --- >>>>>>> [INFO] Running 'grunt dist --no-color' in >>>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>>> [INFO] Loading "bower_task.js" tasks...ERROR >>>>>>> [INFO] >> Error: Cannot find module 'mime' >>>>>>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>>>>>> [INFO] Warning: Task "bower:install" not found. Use --force to >>>>>>> continue. >>>>>>> [INFO] >>>>>>> [INFO] Aborted due to warnings. >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Reactor Summary: >>>>>>> [INFO] >>>>>>> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS >>>>>>> [ 2.020 s] >>>>>>> [INFO] UnifiedPush Model Layer ............................ SUCCESS >>>>>>> [ 0.077 s] >>>>>>> [INFO] UnifiedPush Server Model API ....................... SUCCESS >>>>>>> [ 2.958 s] >>>>>>> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS >>>>>>> [ 12.992 s] >>>>>>> [INFO] UnifiedPush Service Layer .......................... SUCCESS >>>>>>> [ 17.831 s] >>>>>>> [INFO] UnifiedPush Sender Module .......................... SUCCESS >>>>>>> [ 0.066 s] >>>>>>> [INFO] UnifiedPush Push Message Model ..................... SUCCESS >>>>>>> [ 2.369 s] >>>>>>> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS >>>>>>> [ 3.585 s] >>>>>>> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS >>>>>>> [ 5.240 s] >>>>>>> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE >>>>>>> [ 4.898 s] >>>>>>> [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: 53.305 s >>>>>>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>>>>>> [INFO] Final Memory: 98M/635M >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [ERROR] Failed to execute goal >>>>>>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>>>>>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>>>>>> failed. (error code 3) -> [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/MojoFailureException >>>>>>> [ERROR] >>>>>>> [ERROR] After correcting the problems, you can resume the build with >>>>>>> the command >>>>>>> [ERROR] mvn -rf :unifiedpush-admin-ui >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks for help >>>>>>> >>>>>>> *Mgr. Ivan G?rtler* >>>>>>> Mobile software developer >>>>>>> >>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>> 602 00 Brno (Czech Republic) >>>>>>> >>>>>>> www.ahead-itec.com | twitter | >>>>>>> mobile security solutions >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> 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 >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150223/0949de0d/attachment-0001.html From matzew at apache.org Mon Feb 23 09:05:42 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 15:05:42 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: npm :-) On Mon, Feb 23, 2015 at 2:54 PM, Ivan G?rtler wrote: > after download alpha1 version and mvn instal ... everything OK ... I > downloaded master again .... and after import master and mvn install > everthing is OK ... it was strange ... > > Thanks for your help > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-23 14:43 GMT+01:00 Sebastien Blanc : > >> I can build master under Windows 8.1, I did not have the issue. Really >> strange and annoying issue. >> >> >> On Mon, Feb 23, 2015 at 2:35 PM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> yes :D win 8.1 ... but when I downloaded lower version (alpha1) source >>> code ... mvn install is ok ... >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-02-23 14:18 GMT+01:00 Matthias Wessendorf : >>> >>>> Oh, windows - I see ... >>>> >>>> On Mon, Feb 23, 2015 at 2:18 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> >>>>> >>>>> On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> I try it 10 times :-D ... but always with error >>>>>> >>>>> >>>>> lol - sorry to hear. >>>>> >>>>> what operating system are you on ? >>>>> >>>>> >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>>> 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : >>>>>> >>>>>>> the node/npm thing fails randomly for me as well. try running the >>>>>>> mvn build again ;-( >>>>>>> >>>>>>> >>>>>>> On Monday, February 23, 2015, Ivan G?rtler < >>>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I downloaded zip from ... >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server ... import >>>>>>>> as maven project ... >>>>>>>> but I am facing some problem ... when I run maven install... >>>>>>>> >>>>>>>> [INFO] >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> [INFO] Building UnifiedPush Server (Admin UI) 1.1.0-alpha.2-SNAPSHOT >>>>>>>> [INFO] >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> [INFO] >>>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>>>> (enforce-java-version) @ unifiedpush-admin-ui --- >>>>>>>> [INFO] >>>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>>>> (enforce-maven-version) @ unifiedpush-admin-ui --- >>>>>>>> [INFO] >>>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>>>>>>> unifiedpush-admin-ui --- >>>>>>>> [INFO] >>>>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>>>>>>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>>>>>>> [INFO] >>>>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ >>>>>>>> unifiedpush-admin-ui --- >>>>>>>> [INFO] >>>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm >>>>>>>> (install node and npm) @ unifiedpush-admin-ui --- >>>>>>>> [INFO] Node v0.10.31 is already installed. >>>>>>>> [INFO] Found NPM version 1.4.23 >>>>>>>> [INFO] >>>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>>>>>>> unifiedpush-admin-ui --- >>>>>>>> [INFO] Running 'npm install --color=false' in >>>>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>>>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>>>>>>> requires mime@'~1.2.11' but will load >>>>>>>> [INFO] npm WARN unmet dependency undefined, >>>>>>>> [INFO] npm WARN unmet dependency which is version undefined >>>>>>>> [INFO] >>>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>>>>>>> unifiedpush-admin-ui --- >>>>>>>> [INFO] Running 'grunt dist --no-color' in >>>>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>>>> [INFO] Loading "bower_task.js" tasks...ERROR >>>>>>>> [INFO] >> Error: Cannot find module 'mime' >>>>>>>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>>>>>>> [INFO] Warning: Task "bower:install" not found. Use --force to >>>>>>>> continue. >>>>>>>> [INFO] >>>>>>>> [INFO] Aborted due to warnings. >>>>>>>> [INFO] >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> [INFO] Reactor Summary: >>>>>>>> [INFO] >>>>>>>> [INFO] AeroGear UnifiedPush Server ........................ SUCCESS >>>>>>>> [ 2.020 s] >>>>>>>> [INFO] UnifiedPush Model Layer ............................ SUCCESS >>>>>>>> [ 0.077 s] >>>>>>>> [INFO] UnifiedPush Server Model API ....................... SUCCESS >>>>>>>> [ 2.958 s] >>>>>>>> [INFO] UnifiedPush Server Model JPA implementation ........ SUCCESS >>>>>>>> [ 12.992 s] >>>>>>>> [INFO] UnifiedPush Service Layer .......................... SUCCESS >>>>>>>> [ 17.831 s] >>>>>>>> [INFO] UnifiedPush Sender Module .......................... SUCCESS >>>>>>>> [ 0.066 s] >>>>>>>> [INFO] UnifiedPush Push Message Model ..................... SUCCESS >>>>>>>> [ 2.369 s] >>>>>>>> [INFO] UnifiedPush Push Notification Networks ............. SUCCESS >>>>>>>> [ 3.585 s] >>>>>>>> [INFO] UnifiedPush RESTful Endpoint ....................... SUCCESS >>>>>>>> [ 5.240 s] >>>>>>>> [INFO] UnifiedPush Server (Admin UI) ...................... FAILURE >>>>>>>> [ 4.898 s] >>>>>>>> [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: 53.305 s >>>>>>>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>>>>>>> [INFO] Final Memory: 98M/635M >>>>>>>> [INFO] >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> [ERROR] Failed to execute goal >>>>>>>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>>>>>>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>>>>>>> failed. (error code 3) -> [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/MojoFailureException >>>>>>>> [ERROR] >>>>>>>> [ERROR] After correcting the problems, you can resume the build >>>>>>>> with the command >>>>>>>> [ERROR] mvn -rf :unifiedpush-admin-ui >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thanks for help >>>>>>>> >>>>>>>> *Mgr. Ivan G?rtler* >>>>>>>> Mobile software developer >>>>>>>> >>>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>>> 602 00 Brno (Czech Republic) >>>>>>>> >>>>>>>> www.ahead-itec.com | twitter | >>>>>>>> mobile security solutions >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/9533ba1b/attachment.html From lukas.fryc at gmail.com Mon Feb 23 09:43:24 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 23 Feb 2015 15:43:24 +0100 Subject: [aerogear-dev] New Site - Status In-Reply-To: <54E74051.3020704@redhat.com> References: <54E4BFC5.3090002@redhat.com> <54E60DEA.2040303@redhat.com> <54E74051.3020704@redhat.com> Message-ID: Good idea, should we put there instructions for building all libs? Speaking about JavaScript, we can just link to the aerogear-js repo, what about other platforms? On Fri, Feb 20, 2015 at 3:10 PM, Summers Pittman wrote: > > Or we add it to the contribution section since setting up the build is one > of the first things people will want to do. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/055dde14/attachment-0001.html From abstractj at redhat.com Mon Feb 23 10:03:04 2015 From: abstractj at redhat.com (Bruno Oliveira) Date: Mon, 23 Feb 2015 12:03:04 -0300 Subject: [aerogear-dev] Code snippets for aerogear.org Message-ID: <20150223150304.GA3359@redhat.com> Good morning people. Today while I was revisiting our documentation I was wondering if we could follow the same approach from FH docs, which means switch between snippets for iOS, Android, JS, Windows Phone[1]. It not necessarily need to be a pattern to every documentation on AeroGear. But I would like to include at some guides, for example: "How to make use of OAuth2 on AG". Wdyt? [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to the Example section) -- abstractj PGP: 0x84DC9914 From bruno at abstractj.org Mon Feb 23 10:03:56 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 23 Feb 2015 12:03:56 -0300 Subject: [aerogear-dev] Code snippets for aerogear.org Message-ID: <20150223150356.GA3392@abstractj.org> Good morning people. Today while I was revisiting our documentation I was wondering if we could follow the same approach from FH docs, which means switch between snippets for iOS, Android, JS, Windows Phone[1]. It not necessarily need to be a pattern to every documentation on AeroGear. But I would like to include at some guides, for example: "How to make use of OAuth2 on AG". Wdyt? [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to the Example section) -- abstractj PGP: 0x84DC9914 From lukas.fryc at gmail.com Mon Feb 23 10:06:50 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 23 Feb 2015 16:06:50 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: <20150223150304.GA3359@redhat.com> References: <20150223150304.GA3359@redhat.com> Message-ID: +1 I love it We can't have it everywhere, because we don't offer feature parity across all APIs, but let's put it everywhere it does make sense. I can make it pretty once you finish OAuth2 docs. ~ Lukas On Mon, Feb 23, 2015 at 4:03 PM, Bruno Oliveira wrote: > > Good morning people. > > Today while I was revisiting our documentation I was wondering if we > could follow the same approach from FH docs, which means switch between > snippets for iOS, Android, JS, Windows Phone[1]. > > It not necessarily need to be a pattern to every documentation on > AeroGear. But I would like to include at some guides, for example: > > "How to make use of OAuth2 on AG". > > Wdyt? > > [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to > the Example section) > > -- > > 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/20150223/54e4701a/attachment.html From cvasilak at gmail.com Mon Feb 23 10:19:43 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 23 Feb 2015 17:19:43 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Mon Feb 23 15:16:31 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-23-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-23-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-02-23-15.00.log.html > On Feb 22, 2015, at 2:22 PM, Daniel Bevenius wrote: > > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20150223 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/dec5dc30/attachment.html From lholmqui at redhat.com Mon Feb 23 10:25:18 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 23 Feb 2015 10:25:18 -0500 Subject: [aerogear-dev] New Site - Status In-Reply-To: References: <54E4BFC5.3090002@redhat.com> <54E60DEA.2040303@redhat.com> <54E74051.3020704@redhat.com> Message-ID: For the Web/JS platform thing on the home page, it would be nice if we could use the JS colors, http://www.w3devcampus.com/wp-content/uploads/logoAndOther/logo_JavaScript.png > On Feb 23, 2015, at 9:43 AM, Luk?? Fry? wrote: > > Good idea, should we put there instructions for building all libs? > > Speaking about JavaScript, we can just link to the aerogear-js repo, what about other platforms? > > On Fri, Feb 20, 2015 at 3:10 PM, Summers Pittman > wrote: > Or we add it to the contribution section since setting up the build is one of the first things people will want to do. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/70aed1ef/attachment.html From daniel.bevenius at gmail.com Mon Feb 23 10:33:46 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 23 Feb 2015 16:33:46 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: References: <20150223150304.GA3359@redhat.com> Message-ID: +1 That is very nice! On 23 February 2015 at 16:06, Luk?? Fry? wrote: > +1 I love it > > We can't have it everywhere, because we don't offer feature parity across > all APIs, > > but let's put it everywhere it does make sense. I can make it pretty once > you finish OAuth2 docs. > > ~ Lukas > > On Mon, Feb 23, 2015 at 4:03 PM, Bruno Oliveira > wrote: > >> >> Good morning people. >> >> Today while I was revisiting our documentation I was wondering if we >> could follow the same approach from FH docs, which means switch between >> snippets for iOS, Android, JS, Windows Phone[1]. >> >> It not necessarily need to be a pattern to every documentation on >> AeroGear. But I would like to include at some guides, for example: >> >> "How to make use of OAuth2 on AG". >> >> Wdyt? >> >> [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to >> the Example section) >> >> -- >> >> 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/20150223/0eeae7cd/attachment.html From daniel.bevenius at gmail.com Mon Feb 23 10:33:56 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 23 Feb 2015 16:33:56 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: <20150223150356.GA3392@abstractj.org> References: <20150223150356.GA3392@abstractj.org> Message-ID: +1 On 23 February 2015 at 16:03, Bruno Oliveira wrote: > Good morning people. > > Today while I was revisiting our documentation I was wondering if we > could follow the same approach from FH docs, which means switch between > snippets for iOS, Android, JS, Windows Phone[1]. > > It not necessarily need to be a pattern to every documentation on > AeroGear. But I would like to include at some guides, for example: > > "How to make use of OAuth2 on AG". > > Wdyt? > > [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to > the Example section) > > -- > > 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/20150223/af02de79/attachment-0001.html From scm.blanc at gmail.com Mon Feb 23 10:34:57 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 23 Feb 2015 16:34:57 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: References: <20150223150304.GA3359@redhat.com> Message-ID: +1 Love that but for the Push Snippets let's make sure they are in sync with those displayed on the UPS console. On Mon, Feb 23, 2015 at 4:33 PM, Daniel Bevenius wrote: > +1 That is very nice! > > On 23 February 2015 at 16:06, Luk?? Fry? wrote: > >> +1 I love it >> >> We can't have it everywhere, because we don't offer feature parity across >> all APIs, >> >> but let's put it everywhere it does make sense. I can make it pretty once >> you finish OAuth2 docs. >> >> ~ Lukas >> >> On Mon, Feb 23, 2015 at 4:03 PM, Bruno Oliveira >> wrote: >> >>> >>> Good morning people. >>> >>> Today while I was revisiting our documentation I was wondering if we >>> could follow the same approach from FH docs, which means switch between >>> snippets for iOS, Android, JS, Windows Phone[1]. >>> >>> It not necessarily need to be a pattern to every documentation on >>> AeroGear. But I would like to include at some guides, for example: >>> >>> "How to make use of OAuth2 on AG". >>> >>> Wdyt? >>> >>> [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to >>> the Example section) >>> >>> -- >>> >>> 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/20150223/2f1efb74/attachment.html From lukas.fryc at gmail.com Mon Feb 23 10:42:19 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 23 Feb 2015 16:42:19 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: References: <20150223150304.GA3359@redhat.com> Message-ID: We could pull that from the UPS repo, is that worth it? On Mon, Feb 23, 2015 at 4:34 PM, Sebastien Blanc wrote: > +1 Love that but for the Push Snippets let's make sure they are in sync > with those displayed on the UPS console. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/a797658e/attachment.html From scm.blanc at gmail.com Mon Feb 23 10:48:20 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 23 Feb 2015 16:48:20 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: References: <20150223150304.GA3359@redhat.com> Message-ID: We would need to clean it a bit, otherwise it will be a nightmare to extract for the website. Would be nice if each snippet was extracted into a separate file. On Mon, Feb 23, 2015 at 4:42 PM, Luk?? Fry? wrote: > We could pull that from the UPS repo, is that worth it? > > On Mon, Feb 23, 2015 at 4:34 PM, Sebastien Blanc > wrote: > >> +1 Love that but for the Push Snippets let's make sure they are in sync >> with those displayed on the UPS console. >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150223/8b17e86b/attachment.html From matzew at apache.org Mon Feb 23 10:49:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 16:49:02 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: <20150223150356.GA3392@abstractj.org> References: <20150223150356.GA3392@abstractj.org> Message-ID: +9001 especially for modules (like Push, Sync, OAuth2), were the same stuff is covered over the different platforms. -Matthias On Mon, Feb 23, 2015 at 4:03 PM, Bruno Oliveira wrote: > Good morning people. > > Today while I was revisiting our documentation I was wondering if we > could follow the same approach from FH docs, which means switch between > snippets for iOS, Android, JS, Windows Phone[1]. > > It not necessarily need to be a pattern to every documentation on > AeroGear. But I would like to include at some guides, for example: > > "How to make use of OAuth2 on AG". > > Wdyt? > > [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to > the Example section) > > -- > > 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/20150223/2d4ef6d6/attachment.html From matzew at apache.org Mon Feb 23 10:50:13 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 23 Feb 2015 16:50:13 +0100 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: <20150223150304.GA3359@redhat.com> References: <20150223150304.GA3359@redhat.com> Message-ID: +9001 especially for modules (like Push, Sync, OAuth2), were the same stuff is covered over the different platforms. -Matthias On Mon, Feb 23, 2015 at 4:03 PM, Bruno Oliveira wrote: > > Good morning people. > > Today while I was revisiting our documentation I was wondering if we > could follow the same approach from FH docs, which means switch between > snippets for iOS, Android, JS, Windows Phone[1]. > > It not necessarily need to be a pattern to every documentation on > AeroGear. But I would like to include at some guides, for example: > > "How to make use of OAuth2 on AG". > > Wdyt? > > [1] - http://docs.feedhenry.com/v3/api/app_api.html (Just scroll down to > the Example section) > > -- > > 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/20150223/75acd104/attachment.html From bruno at abstractj.org Mon Feb 23 11:52:30 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 23 Feb 2015 13:52:30 -0300 Subject: [aerogear-dev] Code snippets for aerogear.org In-Reply-To: References: <20150223150304.GA3359@redhat.com> Message-ID: <20150223165230.GA3830@abstractj.org> +1 Lukas Jira created to track this issue: https://issues.jboss.org/browse/AEROGEAR-1643 On 2015-02-23, Luk?? Fry? wrote: > We could pull that from the UPS repo, is that worth it? > > On Mon, Feb 23, 2015 at 4:34 PM, Sebastien Blanc > wrote: > > > +1 Love that but for the Push Snippets let's make sure they are in sync > > with those displayed on the UPS console. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From ivan.gurtler at ahead-itec.com Tue Feb 24 04:24:02 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 10:24:02 +0100 Subject: [aerogear-dev] deployment problem - master branch Message-ID: Hi, I try to deploy 2 .war files ... build from master branch. I use JBoss EAP 6.3 in domain mode. Profile: default. I have problem with depolying ag-push.war... 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for persistenceUnit 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not point to a valid jar for a Class-Path reference. 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for keycloak-default 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI annotations but beans.xml was not found. 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=com.aheaditec.cms.backend.webservice.WebApiImpl address=http://localhost:8080/AheadCMS-Backend/WebApiImpl implementor=com.aheaditec.cms.backend.webservice.WebApiImpl serviceName={http://webservice.backend.cms.aheaditec.com/}WebApiImplService portName={http://webservice.backend.cms.aheaditec.com/}WebApiImplPort annotationWsdlLocation=null wsdlLocationOverride=null mtomEnabled=false 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=com.aheaditec.cms.backend.webservice.MobileApiImpl address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl serviceName={ http://webservice.backend.cms.aheaditec.com/}MobileApiImplService portName={http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort annotationWsdlLocation=null wsdlLocationOverride=null mtomEnabled=false 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /AheadCMS-Frontend 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private module ("org.apache.httpcomponents:main") which may be changed or removed in future versions without notice. 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private module ("org.apache.httpcomponents:main") which may be changed or removed in future versions without notice. 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice. 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice. 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice. 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice. 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice. 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice. 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /EnvTest-1.0 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /auth 10:16:14,145 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service { http://webservice.backend.cms.aheaditec.com/}WebApiImplService from class com.aheaditec.cms.backend.webservice.WebApi 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 51) HV000001: Hibernate Validator 4.3.1.Final-redhat-1 10:16:14,958 INFO [org.keycloak.services.resources.KeycloakApplication] (ServerService Thread Pool -- 51) Load config from vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/AheadCMS-Backend/WebApiImpl 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl 10:16:16,493 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service { http://webservice.backend.cms.aheaditec.com/}MobileApiImplService from class com.aheaditec.cms.backend.webservice.MobileApi 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/AheadCMS-Backend/MobileApiImpl 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.port-component-link 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011402: Starting Persistence Unit Service 'AheadCMS-Backend.war#persistenceUnit' 10:16:17,190 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons Annotations {4.0.1.Final-redhat-2} 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000206: hibernate.properties not found 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000021: Bytecode provider name : javassist 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [ name: persistenceUnit ...] 10:16:17,838 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect 10:16:18,983 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory 10:16:19,008 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession() 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /AheadCMS-Backend 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect 10:16:22,141 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory 10:16:22,145 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none 10:16:24,077 INFO [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] (ServerService Thread Pool -- 51) Initializing database schema 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 51) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect 10:16:28,669 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory 10:16:28,670 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory 10:16:29,687 INFO [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread Pool -- 51) Initializing master realm 10:16:33,552 INFO [org.keycloak.services.resources.KeycloakApplication] (ServerService Thread Pool -- 51) Imported realm aerogear from resource /WEB-INF/ups-realm.json 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 51) Adding singleton resource org.keycloak.services.resources.admin.AdminRoot from Application javax.ws.rs.core.Application 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 51) Adding singleton resource org.keycloak.services.resources.SocialResource from Application javax.ws.rs.core.Application 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 51) Adding singleton resource org.keycloak.services.resources.RealmsResource from Application javax.ws.rs.core.Application 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 51) Adding singleton resource org.keycloak.services.resources.ServerVersionResource from Application javax.ws.rs.core.Application 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : "AheadCMS-Frontend.war") 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : "AheadCMS-Backend.war") 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 37203ms - Started 366 of 408 services (70 services are lazy, passive or on-demand) 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: "ag-push.war") 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader' 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter' 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for unifiedpush-default 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private module ("org.apache.httpcomponents:main") which may be changed or removed in future versions without notice. 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private module ("org.apache.httpcomponents:main") which may be changed or removed in future versions without notice. 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice. 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice. 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice. 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice. 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment ag-push.war 10:16:47,154 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" are as follows: java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService java:global/ag-push/ClientInstallationServiceImpl java:app/ag-push/ClientInstallationServiceImpl java:module/ClientInstallationServiceImpl 10:16:47,155 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are as follows: java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService java:global/ag-push/GenericVariantServiceImpl java:app/ag-push/GenericVariantServiceImpl java:module/GenericVariantServiceImpl 10:16:47,155 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are as follows: java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService java:global/ag-push/PushApplicationServiceImpl java:app/ag-push/PushApplicationServiceImpl java:module/PushApplicationServiceImpl 10:16:47,156 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named DeleteOldPushMessageInformationScheduler in deployment unit deployment "ag-push.war" are as follows: java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler java:global/ag-push/DeleteOldPushMessageInformationScheduler java:app/ag-push/DeleteOldPushMessageInformationScheduler java:module/DeleteOldPushMessageInformationScheduler 10:16:47,156 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named SenderServiceImpl in deployment unit deployment "ag-push.war" are as follows: java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService java:global/ag-push/SenderServiceImpl java:app/ag-push/SenderServiceImpl java:module/SenderServiceImpl 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: ag-push.war 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.23 (redhat) 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."ag-push.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "ag-push.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] 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] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018096: Error instantiating container component: org.keycloak.adapters.as7.KeycloakAuthenticatorValve at org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) at org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] ... 5 more Caused by: java.lang.ClassNotFoundException: org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module "deployment.ag-push.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) ... 8 more 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the following failure message: { "JBAS014671: Failed services" => {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"ag-push.war\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018096: Error instantiating container component: org.keycloak.adapters.as7.KeycloakAuthenticatorValve Caused by: java.lang.ClassNotFoundException: org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module \"deployment.ag-push.war:main\" from Service Module Loader]"}, "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] } 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) in 29ms 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 14) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.deployment.unit."ag-push.war".beanmanager (missing) dependents: [service jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] JBAS014777: Services which failed to start: service jboss.deployment.unit."ag-push.war".INSTALL Thanks for help ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/46f09f2f/attachment-0001.html From matzew at apache.org Tue Feb 24 04:29:56 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 10:29:56 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler wrote: > Hi, > > I try to deploy 2 .war files ... build from master branch. I use JBoss EAP > 6.3 in domain mode. Profile: default. > > I have problem with depolying ag-push.war... > you used the one from the as7 server folder ? > > 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: > Read persistence.xml for persistenceUnit > 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in > /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not > point to a valid jar for a Class-Path reference. > 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: > Read persistence.xml for keycloak-default > 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) > JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI > annotations but beans.xml was not found. > 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) > JBWS024061: Adding service endpoint metadata: > id=com.aheaditec.cms.backend.webservice.WebApiImpl > address=http://localhost:8080/AheadCMS-Backend/WebApiImpl > implementor=com.aheaditec.cms.backend.webservice.WebApiImpl > serviceName={ > http://webservice.backend.cms.aheaditec.com/}WebApiImplService > portName={http://webservice.backend.cms.aheaditec.com/}WebApiImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) > JBWS024061: Adding service endpoint metadata: > id=com.aheaditec.cms.backend.webservice.MobileApiImpl > address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl > implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl > serviceName={ > http://webservice.backend.cms.aheaditec.com/}MobileApiImplService > portName={http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) > JBAS018210: Register web context: /AheadCMS-Frontend > 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private > module ("org.apache.httpcomponents:main") which may be changed or removed > in future versions without notice. > 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private > module ("org.apache.httpcomponents:main") which may be changed or removed > in future versions without notice. > 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private > module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed > or removed in future versions without notice. > 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private > module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed > or removed in future versions without notice. > 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private > module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be > changed or removed in future versions without notice. > 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private > module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be > changed or removed in future versions without notice. > 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service > thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an > unsupported module ("org.infinispan:main") which may be changed or removed > in future versions without notice. > 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service > thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an > unsupported module ("org.infinispan:main") which may be changed or removed > in future versions without notice. > 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) > JBAS018210: Register web context: /EnvTest-1.0 > 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) > JBAS018210: Register web context: /auth > 10:16:14,145 INFO > [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service > thread 1-2) Creating Service { > http://webservice.backend.cms.aheaditec.com/}WebApiImplService from class > com.aheaditec.cms.backend.webservice.WebApi > 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] > (ServerService Thread Pool -- 51) HV000001: Hibernate Validator > 4.3.1.Final-redhat-1 > 10:16:14,958 INFO [org.keycloak.services.resources.KeycloakApplication] > (ServerService Thread Pool -- 51) Load config from > vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json > 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service > thread 1-2) Setting the server's publish address to be > http://localhost:8080/AheadCMS-Backend/WebApiImpl > 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) > JBWS024074: WSDL published to: > file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl > 10:16:16,493 INFO > [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service > thread 1-2) Creating Service { > http://webservice.backend.cms.aheaditec.com/}MobileApiImplService from > class com.aheaditec.cms.backend.webservice.MobileApi > 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service > thread 1-2) Setting the server's publish address to be > http://localhost:8080/AheadCMS-Backend/MobileApiImpl > 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) > JBWS024074: WSDL published to: > file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl > 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015539: Starting service jboss.ws.port-component-link > 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015539: Starting service > jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" > 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread 1-2) > JBAS015539: Starting service > jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" > 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) > JBAS011402: Starting Persistence Unit Service > 'AheadCMS-Backend.war#persistenceUnit' > 10:16:17,190 INFO [org.hibernate.annotations.common.Version] > (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons > Annotations {4.0.1.Final-redhat-2} > 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool -- > 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} > 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService Thread > Pool -- 50) HHH000206: hibernate.properties not found > 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService Thread > Pool -- 50) HHH000021: Bytecode provider name : javassist > 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService > Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [ > name: persistenceUnit > ...] > 10:16:17,838 INFO > [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] > (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit > connection provider: > org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider > 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService Thread > Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect > 10:16:18,983 INFO > [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] > (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: > org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory > 10:16:19,008 INFO > [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService > Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory > 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService > Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none > 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] > (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used > with JDBCTransactionFactory; auto-flush will not operate correctly with > getCurrentSession() > 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) > JBAS018210: Register web context: /AheadCMS-Backend > 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService Thread > Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect > 10:16:22,141 INFO > [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] > (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: > org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory > 10:16:22,145 INFO > [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService > Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory > 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService > Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none > 10:16:24,077 INFO > [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] > (ServerService Thread Pool -- 51) Initializing database schema > 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService Thread > Pool -- 51) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect > 10:16:28,669 INFO > [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] > (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: > org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory > 10:16:28,670 INFO > [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService > Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory > 10:16:29,687 INFO [org.keycloak.services.managers.ApplianceBootstrap] > (ServerService Thread Pool -- 51) Initializing master realm > 10:16:33,552 INFO [org.keycloak.services.resources.KeycloakApplication] > (ServerService Thread Pool -- 51) Imported realm aerogear from resource > /WEB-INF/ups-realm.json > 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] > (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: > class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication > 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] > (ServerService Thread Pool -- 51) Adding singleton resource > org.keycloak.services.resources.admin.AdminRoot from Application > javax.ws.rs.core.Application > 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] > (ServerService Thread Pool -- 51) Adding singleton resource > org.keycloak.services.resources.SocialResource from Application > javax.ws.rs.core.Application > 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] > (ServerService Thread Pool -- 51) Adding singleton resource > org.keycloak.services.resources.RealmsResource from Application > javax.ws.rs.core.Application > 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] > (ServerService Thread Pool -- 51) Adding singleton resource > org.keycloak.services.resources.ServerVersionResource from Application > javax.ws.rs.core.Application > 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) > JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") > 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) > JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : > "AheadCMS-Frontend.war") > 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) > JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : > "AheadCMS-Backend.war") > 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) > JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") > 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: > JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 37203ms - > Started 366 of 408 services (70 services are lazy, passive or on-demand) > 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: > "ag-push.war") > 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyReader' > 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' > for service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service thread > 1-1) JBAS015893: Encountered invalid class name > 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for > service type 'javax.ws.rs.ext.MessageBodyWriter' > 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: > Read persistence.xml for unifiedpush-default > 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private > module ("org.apache.httpcomponents:main") which may be changed or removed > in future versions without notice. > 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private > module ("org.apache.httpcomponents:main") which may be changed or removed > in future versions without notice. > 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private > module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed > or removed in future versions without notice. > 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private > module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed > or removed in future versions without notice. > 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private > module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be > changed or removed in future versions without notice. > 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread > 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private > module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be > changed or removed in future versions without notice. > 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) > JBAS016002: Processing weld deployment ag-push.war > 10:16:47,154 INFO > [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] > (MSC service thread 1-1) JNDI bindings for session bean named > ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" > are as follows: > > > java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService > > java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService > > java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService > java:global/ag-push/ClientInstallationServiceImpl > java:app/ag-push/ClientInstallationServiceImpl > java:module/ClientInstallationServiceImpl > > 10:16:47,155 INFO > [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] > (MSC service thread 1-1) JNDI bindings for session bean named > GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are > as follows: > > > java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService > > java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService > > java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService > java:global/ag-push/GenericVariantServiceImpl > java:app/ag-push/GenericVariantServiceImpl > java:module/GenericVariantServiceImpl > > 10:16:47,155 INFO > [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] > (MSC service thread 1-1) JNDI bindings for session bean named > PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are > as follows: > > > java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService > > java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService > > java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService > java:global/ag-push/PushApplicationServiceImpl > java:app/ag-push/PushApplicationServiceImpl > java:module/PushApplicationServiceImpl > > 10:16:47,156 INFO > [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] > (MSC service thread 1-1) JNDI bindings for session bean named > DeleteOldPushMessageInformationScheduler in deployment unit deployment > "ag-push.war" are as follows: > > > java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler > > java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler > > java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler > java:global/ag-push/DeleteOldPushMessageInformationScheduler > java:app/ag-push/DeleteOldPushMessageInformationScheduler > java:module/DeleteOldPushMessageInformationScheduler > > 10:16:47,156 INFO > [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] > (MSC service thread 1-1) JNDI bindings for session bean named > SenderServiceImpl in deployment unit deployment "ag-push.war" are as > follows: > > > java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService > > java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService > > java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService > java:global/ag-push/SenderServiceImpl > java:app/ag-push/SenderServiceImpl > java:module/SenderServiceImpl > > 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) > JBAS016005: Starting Services for CDI deployment: ag-push.war > 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) > WELD-000900 1.1.23 (redhat) > 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) > MSC000001: Failed to start service > jboss.deployment.unit."ag-push.war".INSTALL: > org.jboss.msc.service.StartException in service > jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process > phase INSTALL of deployment "ag-push.war" > at > org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) > [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > 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] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [rt.jar:1.7.0_75] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [rt.jar:1.7.0_75] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] > Caused by: > org.jboss.as.server.deployment.DeploymentUnitProcessingException: > JBAS018096: Error instantiating container component: > org.keycloak.adapters.as7.KeycloakAuthenticatorValve > at > org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) > at > org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) > at > org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) > at > org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) > [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > ... 5 more > Caused by: java.lang.ClassNotFoundException: > org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module > "deployment.ag-push.war:main" from Service Module Loader] > at > org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) > [jboss-modules.jar:1.3.3.Final-redhat-1] > at > org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) > [jboss-modules.jar:1.3.3.Final-redhat-1] > at > org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) > [jboss-modules.jar:1.3.3.Final-redhat-1] > at > org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) > [jboss-modules.jar:1.3.3.Final-redhat-1] > at > org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) > [jboss-modules.jar:1.3.3.Final-redhat-1] > at > org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) > ... 8 more > > 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 14) > JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the > following failure message: > { > "JBAS014671: Failed services" => > {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => > "org.jboss.msc.service.StartException in service > jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to > process phase INSTALL of deployment \"ag-push.war\" > Caused by: > org.jboss.as.server.deployment.DeploymentUnitProcessingException: > JBAS018096: Error instantiating container component: > org.keycloak.adapters.as7.KeycloakAuthenticatorValve > Caused by: java.lang.ClassNotFoundException: > org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module > \"deployment.ag-push.war:main\" from Service Module Loader]"}, > "JBAS014771: Services with missing/unavailable dependencies" => > ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is > missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] > } > 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) > in 29ms > 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread Pool -- > 14) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.deployment.unit."ag-push.war".beanmanager (missing) > dependents: [service > jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] > JBAS014777: Services which failed to start: service > jboss.deployment.unit."ag-push.war".INSTALL > > > Thanks for help ... > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/321ee620/attachment-0001.html From ivan.gurtler at ahead-itec.com Tue Feb 24 04:32:08 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 10:32:08 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: yes ... I use AS7 version .. *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : > > > On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> Hi, >> >> I try to deploy 2 .war files ... build from master branch. I use JBoss >> EAP 6.3 in domain mode. Profile: default. >> >> I have problem with depolying ag-push.war... >> > > you used the one from the as7 server folder ? > > > > >> >> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >> JBAS011401: Read persistence.xml for persistenceUnit >> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >> point to a valid jar for a Class-Path reference. >> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >> JBAS011401: Read persistence.xml for keycloak-default >> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) >> JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >> annotations but beans.xml was not found. >> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) >> JBWS024061: Adding service endpoint metadata: >> id=com.aheaditec.cms.backend.webservice.WebApiImpl >> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >> serviceName={ >> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >> portName={http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >> annotationWsdlLocation=null >> wsdlLocationOverride=null >> mtomEnabled=false >> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) >> JBWS024061: Adding service endpoint metadata: >> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >> serviceName={ >> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >> portName={http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >> annotationWsdlLocation=null >> wsdlLocationOverride=null >> mtomEnabled=false >> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >> JBAS018210: Register web context: /AheadCMS-Frontend >> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >> module ("org.apache.httpcomponents:main") which may be changed or removed >> in future versions without notice. >> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >> module ("org.apache.httpcomponents:main") which may be changed or removed >> in future versions without notice. >> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >> or removed in future versions without notice. >> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >> or removed in future versions without notice. >> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >> changed or removed in future versions without notice. >> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >> changed or removed in future versions without notice. >> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >> unsupported module ("org.infinispan:main") which may be changed or removed >> in future versions without notice. >> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >> unsupported module ("org.infinispan:main") which may be changed or removed >> in future versions without notice. >> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >> JBAS018210: Register web context: /EnvTest-1.0 >> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >> JBAS018210: Register web context: /auth >> 10:16:14,145 INFO >> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >> thread 1-2) Creating Service { >> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >> class com.aheaditec.cms.backend.webservice.WebApi >> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >> 4.3.1.Final-redhat-1 >> 10:16:14,958 INFO [org.keycloak.services.resources.KeycloakApplication] >> (ServerService Thread Pool -- 51) Load config from >> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >> thread 1-2) Setting the server's publish address to be >> http://localhost:8080/AheadCMS-Backend/WebApiImpl >> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) >> JBWS024074: WSDL published to: >> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >> 10:16:16,493 INFO >> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >> thread 1-2) Creating Service { >> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService from >> class com.aheaditec.cms.backend.webservice.MobileApi >> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >> thread 1-2) Setting the server's publish address to be >> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) >> JBWS024074: WSDL published to: >> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >> JBAS015539: Starting service jboss.ws.port-component-link >> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >> JBAS015539: Starting service >> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread 1-2) >> JBAS015539: Starting service >> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) >> JBAS011402: Starting Persistence Unit Service >> 'AheadCMS-Backend.war#persistenceUnit' >> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >> Annotations {4.0.1.Final-redhat-2} >> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool -- >> 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService Thread >> Pool -- 50) HHH000206: hibernate.properties not found >> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService Thread >> Pool -- 50) HHH000021: Bytecode provider name : javassist >> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService >> Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [ >> name: persistenceUnit >> ...] >> 10:16:17,838 INFO >> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >> connection provider: >> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService Thread >> Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect >> 10:16:18,983 INFO >> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >> 10:16:19,008 INFO >> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >> with JDBCTransactionFactory; auto-flush will not operate correctly with >> getCurrentSession() >> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >> JBAS018210: Register web context: /AheadCMS-Backend >> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService Thread >> Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect >> 10:16:22,141 INFO >> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >> 10:16:22,145 INFO >> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >> 10:16:24,077 INFO >> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >> (ServerService Thread Pool -- 51) Initializing database schema >> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService Thread >> Pool -- 51) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect >> 10:16:28,669 INFO >> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >> 10:16:28,670 INFO >> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >> 10:16:29,687 INFO [org.keycloak.services.managers.ApplianceBootstrap] >> (ServerService Thread Pool -- 51) Initializing master realm >> 10:16:33,552 INFO [org.keycloak.services.resources.KeycloakApplication] >> (ServerService Thread Pool -- 51) Imported realm aerogear from resource >> /WEB-INF/ups-realm.json >> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >> (ServerService Thread Pool -- 51) Adding singleton resource >> org.keycloak.services.resources.admin.AdminRoot from Application >> javax.ws.rs.core.Application >> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >> (ServerService Thread Pool -- 51) Adding singleton resource >> org.keycloak.services.resources.SocialResource from Application >> javax.ws.rs.core.Application >> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >> (ServerService Thread Pool -- 51) Adding singleton resource >> org.keycloak.services.resources.RealmsResource from Application >> javax.ws.rs.core.Application >> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >> (ServerService Thread Pool -- 51) Adding singleton resource >> org.keycloak.services.resources.ServerVersionResource from Application >> javax.ws.rs.core.Application >> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >> "AheadCMS-Frontend.war") >> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >> "AheadCMS-Backend.war") >> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: >> JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 37203ms - >> Started 366 of 408 services (70 services are lazy, passive or on-demand) >> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >> "ag-push.war") >> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyReader' >> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >> for service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service thread >> 1-1) JBAS015893: Encountered invalid class name >> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >> service type 'javax.ws.rs.ext.MessageBodyWriter' >> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >> JBAS011401: Read persistence.xml for unifiedpush-default >> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >> module ("org.apache.httpcomponents:main") which may be changed or removed >> in future versions without notice. >> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >> module ("org.apache.httpcomponents:main") which may be changed or removed >> in future versions without notice. >> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >> or removed in future versions without notice. >> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >> or removed in future versions without notice. >> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >> changed or removed in future versions without notice. >> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >> changed or removed in future versions without notice. >> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >> JBAS016002: Processing weld deployment ag-push.war >> 10:16:47,154 INFO >> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >> (MSC service thread 1-1) JNDI bindings for session bean named >> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >> are as follows: >> >> >> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >> >> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >> >> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >> java:global/ag-push/ClientInstallationServiceImpl >> java:app/ag-push/ClientInstallationServiceImpl >> java:module/ClientInstallationServiceImpl >> >> 10:16:47,155 INFO >> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >> (MSC service thread 1-1) JNDI bindings for session bean named >> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >> as follows: >> >> >> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >> >> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >> >> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >> java:global/ag-push/GenericVariantServiceImpl >> java:app/ag-push/GenericVariantServiceImpl >> java:module/GenericVariantServiceImpl >> >> 10:16:47,155 INFO >> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >> (MSC service thread 1-1) JNDI bindings for session bean named >> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >> as follows: >> >> >> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >> >> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >> >> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >> java:global/ag-push/PushApplicationServiceImpl >> java:app/ag-push/PushApplicationServiceImpl >> java:module/PushApplicationServiceImpl >> >> 10:16:47,156 INFO >> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >> (MSC service thread 1-1) JNDI bindings for session bean named >> DeleteOldPushMessageInformationScheduler in deployment unit deployment >> "ag-push.war" are as follows: >> >> >> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >> >> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >> >> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >> java:global/ag-push/DeleteOldPushMessageInformationScheduler >> java:app/ag-push/DeleteOldPushMessageInformationScheduler >> java:module/DeleteOldPushMessageInformationScheduler >> >> 10:16:47,156 INFO >> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >> (MSC service thread 1-1) JNDI bindings for session bean named >> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >> follows: >> >> >> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >> >> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >> >> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >> java:global/ag-push/SenderServiceImpl >> java:app/ag-push/SenderServiceImpl >> java:module/SenderServiceImpl >> >> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) >> JBAS016005: Starting Services for CDI deployment: ag-push.war >> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >> WELD-000900 1.1.23 (redhat) >> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) >> MSC000001: Failed to start service >> jboss.deployment.unit."ag-push.war".INSTALL: >> org.jboss.msc.service.StartException in service >> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >> phase INSTALL of deployment "ag-push.war" >> at >> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >> 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] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> [rt.jar:1.7.0_75] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> [rt.jar:1.7.0_75] >> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >> Caused by: >> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >> JBAS018096: Error instantiating container component: >> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >> at >> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >> at >> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >> at >> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >> at >> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >> ... 5 more >> Caused by: java.lang.ClassNotFoundException: >> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >> "deployment.ag-push.war:main" from Service Module Loader] >> at >> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >> [jboss-modules.jar:1.3.3.Final-redhat-1] >> at >> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >> [jboss-modules.jar:1.3.3.Final-redhat-1] >> at >> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >> [jboss-modules.jar:1.3.3.Final-redhat-1] >> at >> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >> [jboss-modules.jar:1.3.3.Final-redhat-1] >> at >> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >> [jboss-modules.jar:1.3.3.Final-redhat-1] >> at >> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >> ... 8 more >> >> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool -- >> 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the >> following failure message: >> { >> "JBAS014671: Failed services" => >> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >> "org.jboss.msc.service.StartException in service >> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >> process phase INSTALL of deployment \"ag-push.war\" >> Caused by: >> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >> JBAS018096: Error instantiating container component: >> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >> Caused by: java.lang.ClassNotFoundException: >> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >> "JBAS014771: Services with missing/unavailable dependencies" => >> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >> } >> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service thread >> 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) >> in 29ms >> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread Pool >> -- 14) JBAS014774: Service status report >> JBAS014775: New missing/unsatisfied dependencies: >> service jboss.deployment.unit."ag-push.war".beanmanager (missing) >> dependents: [service >> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >> JBAS014777: Services which failed to start: service >> jboss.deployment.unit."ag-push.war".INSTALL >> >> >> Thanks for help ... >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150224/5d0ef984/attachment-0001.html From matzew at apache.org Tue Feb 24 04:34:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 10:34:19 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: yeah, I now see it: KeycloakAuthenticatorValve Caused by: java.lang.ClassNotFoundException: org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module \"deployment.ag-push.war:main\" from Service Module Loader]"}, looks like an issue w/ the KC adapter for AS7, that comes with the 1.1.x series of Keycloak - I will take a look in a bit On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler wrote: > yes ... I use AS7 version .. > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : > >> >> >> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> Hi, >>> >>> I try to deploy 2 .war files ... build from master branch. I use JBoss >>> EAP 6.3 in domain mode. Profile: default. >>> >>> I have problem with depolying ag-push.war... >>> >> >> you used the one from the as7 server folder ? >> >> >> >> >>> >>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>> JBAS011401: Read persistence.xml for persistenceUnit >>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>> point to a valid jar for a Class-Path reference. >>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>> JBAS011401: Read persistence.xml for keycloak-default >>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) >>> JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>> annotations but beans.xml was not found. >>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) >>> JBWS024061: Adding service endpoint metadata: >>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>> serviceName={ >>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>> portName={http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>> annotationWsdlLocation=null >>> wsdlLocationOverride=null >>> mtomEnabled=false >>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) >>> JBWS024061: Adding service endpoint metadata: >>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>> serviceName={ >>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>> portName={ >>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>> annotationWsdlLocation=null >>> wsdlLocationOverride=null >>> mtomEnabled=false >>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>> JBAS018210: Register web context: /AheadCMS-Frontend >>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >>> module ("org.apache.httpcomponents:main") which may be changed or removed >>> in future versions without notice. >>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >>> module ("org.apache.httpcomponents:main") which may be changed or removed >>> in future versions without notice. >>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >>> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >>> or removed in future versions without notice. >>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >>> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >>> or removed in future versions without notice. >>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >>> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >>> changed or removed in future versions without notice. >>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a private >>> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >>> changed or removed in future versions without notice. >>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>> unsupported module ("org.infinispan:main") which may be changed or removed >>> in future versions without notice. >>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>> unsupported module ("org.infinispan:main") which may be changed or removed >>> in future versions without notice. >>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>> JBAS018210: Register web context: /EnvTest-1.0 >>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>> JBAS018210: Register web context: /auth >>> 10:16:14,145 INFO >>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>> thread 1-2) Creating Service { >>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >>> class com.aheaditec.cms.backend.webservice.WebApi >>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>> 4.3.1.Final-redhat-1 >>> 10:16:14,958 INFO [org.keycloak.services.resources.KeycloakApplication] >>> (ServerService Thread Pool -- 51) Load config from >>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>> thread 1-2) Setting the server's publish address to be >>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>> 1-2) JBWS024074: WSDL published to: >>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>> 10:16:16,493 INFO >>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>> thread 1-2) Creating Service { >>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService from >>> class com.aheaditec.cms.backend.webservice.MobileApi >>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>> thread 1-2) Setting the server's publish address to be >>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>> 1-2) JBWS024074: WSDL published to: >>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >>> JBAS015539: Starting service jboss.ws.port-component-link >>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >>> JBAS015539: Starting service >>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread 1-2) >>> JBAS015539: Starting service >>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) >>> JBAS011402: Starting Persistence Unit Service >>> 'AheadCMS-Backend.war#persistenceUnit' >>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>> Annotations {4.0.1.Final-redhat-2} >>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool -- >>> 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService Thread >>> Pool -- 50) HHH000206: hibernate.properties not found >>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService Thread >>> Pool -- 50) HHH000021: Bytecode provider name : javassist >>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService >>> Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [ >>> name: persistenceUnit >>> ...] >>> 10:16:17,838 INFO >>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>> connection provider: >>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService Thread >>> Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect >>> 10:16:18,983 INFO >>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>> 10:16:19,008 INFO >>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>> getCurrentSession() >>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>> JBAS018210: Register web context: /AheadCMS-Backend >>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService Thread >>> Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect >>> 10:16:22,141 INFO >>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>> 10:16:22,145 INFO >>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>> 10:16:24,077 INFO >>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>> (ServerService Thread Pool -- 51) Initializing database schema >>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService Thread >>> Pool -- 51) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect >>> 10:16:28,669 INFO >>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>> 10:16:28,670 INFO >>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>> 10:16:29,687 INFO [org.keycloak.services.managers.ApplianceBootstrap] >>> (ServerService Thread Pool -- 51) Initializing master realm >>> 10:16:33,552 INFO [org.keycloak.services.resources.KeycloakApplication] >>> (ServerService Thread Pool -- 51) Imported realm aerogear from resource >>> /WEB-INF/ups-realm.json >>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>> (ServerService Thread Pool -- 51) Adding singleton resource >>> org.keycloak.services.resources.admin.AdminRoot from Application >>> javax.ws.rs.core.Application >>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>> (ServerService Thread Pool -- 51) Adding singleton resource >>> org.keycloak.services.resources.SocialResource from Application >>> javax.ws.rs.core.Application >>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>> (ServerService Thread Pool -- 51) Adding singleton resource >>> org.keycloak.services.resources.RealmsResource from Application >>> javax.ws.rs.core.Application >>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>> (ServerService Thread Pool -- 51) Adding singleton resource >>> org.keycloak.services.resources.ServerVersionResource from Application >>> javax.ws.rs.core.Application >>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>> "AheadCMS-Frontend.war") >>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>> "AheadCMS-Backend.war") >>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: >>> JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 37203ms - >>> Started 366 of 408 services (70 services are lazy, passive or on-demand) >>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service thread >>> 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>> "ag-push.war") >>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-1) JBAS015893: Encountered invalid class name >>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>> JBAS011401: Read persistence.xml for unifiedpush-default >>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >>> module ("org.apache.httpcomponents:main") which may be changed or removed >>> in future versions without notice. >>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >>> module ("org.apache.httpcomponents:main") which may be changed or removed >>> in future versions without notice. >>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >>> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >>> or removed in future versions without notice. >>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >>> module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed >>> or removed in future versions without notice. >>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >>> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >>> changed or removed in future versions without notice. >>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service thread >>> 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a private >>> module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be >>> changed or removed in future versions without notice. >>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >>> JBAS016002: Processing weld deployment ag-push.war >>> 10:16:47,154 INFO >>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>> (MSC service thread 1-1) JNDI bindings for session bean named >>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>> are as follows: >>> >>> >>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>> >>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>> >>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>> java:global/ag-push/ClientInstallationServiceImpl >>> java:app/ag-push/ClientInstallationServiceImpl >>> java:module/ClientInstallationServiceImpl >>> >>> 10:16:47,155 INFO >>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>> (MSC service thread 1-1) JNDI bindings for session bean named >>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>> as follows: >>> >>> >>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>> >>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>> >>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>> java:global/ag-push/GenericVariantServiceImpl >>> java:app/ag-push/GenericVariantServiceImpl >>> java:module/GenericVariantServiceImpl >>> >>> 10:16:47,155 INFO >>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>> (MSC service thread 1-1) JNDI bindings for session bean named >>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>> as follows: >>> >>> >>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>> >>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>> >>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>> java:global/ag-push/PushApplicationServiceImpl >>> java:app/ag-push/PushApplicationServiceImpl >>> java:module/PushApplicationServiceImpl >>> >>> 10:16:47,156 INFO >>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>> (MSC service thread 1-1) JNDI bindings for session bean named >>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>> "ag-push.war" are as follows: >>> >>> >>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>> >>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>> >>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>> java:module/DeleteOldPushMessageInformationScheduler >>> >>> 10:16:47,156 INFO >>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>> (MSC service thread 1-1) JNDI bindings for session bean named >>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>> follows: >>> >>> >>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>> >>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>> >>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>> java:global/ag-push/SenderServiceImpl >>> java:app/ag-push/SenderServiceImpl >>> java:module/SenderServiceImpl >>> >>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) >>> JBAS016005: Starting Services for CDI deployment: ag-push.war >>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >>> WELD-000900 1.1.23 (redhat) >>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) >>> MSC000001: Failed to start service >>> jboss.deployment.unit."ag-push.war".INSTALL: >>> org.jboss.msc.service.StartException in service >>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>> phase INSTALL of deployment "ag-push.war" >>> at >>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>> 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] >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>> [rt.jar:1.7.0_75] >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> [rt.jar:1.7.0_75] >>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>> Caused by: >>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>> JBAS018096: Error instantiating container component: >>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>> at >>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>> at >>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>> at >>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>> at >>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>> ... 5 more >>> Caused by: java.lang.ClassNotFoundException: >>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>> "deployment.ag-push.war:main" from Service Module Loader] >>> at >>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>> at >>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>> at >>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>> at >>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>> at >>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>> at >>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>> ... 8 more >>> >>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool -- >>> 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the >>> following failure message: >>> { >>> "JBAS014671: Failed services" => >>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>> "org.jboss.msc.service.StartException in service >>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>> process phase INSTALL of deployment \"ag-push.war\" >>> Caused by: >>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>> JBAS018096: Error instantiating container component: >>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>> Caused by: java.lang.ClassNotFoundException: >>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>> "JBAS014771: Services with missing/unavailable dependencies" => >>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>> } >>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service thread >>> 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) >>> in 29ms >>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread Pool >>> -- 14) JBAS014774: Service status report >>> JBAS014775: New missing/unsatisfied dependencies: >>> service jboss.deployment.unit."ag-push.war".beanmanager (missing) >>> dependents: [service >>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>> JBAS014777: Services which failed to start: service >>> jboss.deployment.unit."ag-push.war".INSTALL >>> >>> >>> Thanks for help ... >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/90fc0b6b/attachment-0001.html From matzew at apache.org Tue Feb 24 04:34:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 10:34:37 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: Ivan, can you file a JIRA ticket for this? On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf wrote: > yeah, I now see it: > > KeycloakAuthenticatorValve > Caused by: java.lang.ClassNotFoundException: > org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module > \"deployment.ag-push.war:main\" from Service Module Loader]"}, > > > looks like an issue w/ the KC adapter for AS7, that comes with the 1.1.x > series of Keycloak - I will take a look in a bit > > On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> yes ... I use AS7 version .. >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >> >>> >>> >>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> Hi, >>>> >>>> I try to deploy 2 .war files ... build from master branch. I use JBoss >>>> EAP 6.3 in domain mode. Profile: default. >>>> >>>> I have problem with depolying ag-push.war... >>>> >>> >>> you used the one from the as7 server folder ? >>> >>> >>> >>> >>>> >>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>> JBAS011401: Read persistence.xml for persistenceUnit >>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>> point to a valid jar for a Class-Path reference. >>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>> JBAS011401: Read persistence.xml for keycloak-default >>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) >>>> JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>> annotations but beans.xml was not found. >>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) >>>> JBWS024061: Adding service endpoint metadata: >>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>> serviceName={ >>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>> portName={http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>> annotationWsdlLocation=null >>>> wsdlLocationOverride=null >>>> mtomEnabled=false >>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) >>>> JBWS024061: Adding service endpoint metadata: >>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>> serviceName={ >>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>> portName={ >>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>> annotationWsdlLocation=null >>>> wsdlLocationOverride=null >>>> mtomEnabled=false >>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>> JBAS018210: Register web context: /AheadCMS-Frontend >>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>> removed in future versions without notice. >>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>> removed in future versions without notice. >>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>> changed or removed in future versions without notice. >>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>> changed or removed in future versions without notice. >>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>> be changed or removed in future versions without notice. >>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>> be changed or removed in future versions without notice. >>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>>> unsupported module ("org.infinispan:main") which may be changed or removed >>>> in future versions without notice. >>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>>> unsupported module ("org.infinispan:main") which may be changed or removed >>>> in future versions without notice. >>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>> JBAS018210: Register web context: /EnvTest-1.0 >>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>> JBAS018210: Register web context: /auth >>>> 10:16:14,145 INFO >>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>> thread 1-2) Creating Service { >>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >>>> class com.aheaditec.cms.backend.webservice.WebApi >>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>> 4.3.1.Final-redhat-1 >>>> 10:16:14,958 INFO >>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>> Thread Pool -- 51) Load config from >>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>> thread 1-2) Setting the server's publish address to be >>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>> 1-2) JBWS024074: WSDL published to: >>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>> 10:16:16,493 INFO >>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>> thread 1-2) Creating Service { >>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService from >>>> class com.aheaditec.cms.backend.webservice.MobileApi >>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>> thread 1-2) Setting the server's publish address to be >>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>> 1-2) JBWS024074: WSDL published to: >>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >>>> JBAS015539: Starting service jboss.ws.port-component-link >>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >>>> JBAS015539: Starting service >>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread 1-2) >>>> JBAS015539: Starting service >>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) >>>> JBAS011402: Starting Persistence Unit Service >>>> 'AheadCMS-Backend.war#persistenceUnit' >>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>> Annotations {4.0.1.Final-redhat-2} >>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool >>>> -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService >>>> Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [ >>>> name: persistenceUnit >>>> ...] >>>> 10:16:17,838 INFO >>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>> connection provider: >>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>> Thread Pool -- 50) HHH000400: Using dialect: >>>> org.hibernate.dialect.Oracle10gDialect >>>> 10:16:18,983 INFO >>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>> 10:16:19,008 INFO >>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>> getCurrentSession() >>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>> JBAS018210: Register web context: /AheadCMS-Backend >>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>> Thread Pool -- 50) HHH000400: Using dialect: >>>> org.hibernate.dialect.Oracle10gDialect >>>> 10:16:22,141 INFO >>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>> 10:16:22,145 INFO >>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>>> 10:16:24,077 INFO >>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>> (ServerService Thread Pool -- 51) Initializing database schema >>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>> Thread Pool -- 51) HHH000400: Using dialect: >>>> org.hibernate.dialect.Oracle10gDialect >>>> 10:16:28,669 INFO >>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>> 10:16:28,670 INFO >>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>> 10:16:29,687 INFO [org.keycloak.services.managers.ApplianceBootstrap] >>>> (ServerService Thread Pool -- 51) Initializing master realm >>>> 10:16:33,552 INFO >>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>> Thread Pool -- 51) Imported realm aerogear from resource >>>> /WEB-INF/ups-realm.json >>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>> javax.ws.rs.core.Application >>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>> org.keycloak.services.resources.SocialResource from Application >>>> javax.ws.rs.core.Application >>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>> org.keycloak.services.resources.RealmsResource from Application >>>> javax.ws.rs.core.Application >>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>> org.keycloak.services.resources.ServerVersionResource from Application >>>> javax.ws.rs.core.Application >>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>> "AheadCMS-Frontend.war") >>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>> "AheadCMS-Backend.war") >>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: >>>> JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 37203ms - >>>> Started 366 of 408 services (70 services are lazy, passive or on-demand) >>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service thread >>>> 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>> "ag-push.war") >>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015893: Encountered invalid class name >>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>> removed in future versions without notice. >>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>> removed in future versions without notice. >>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>> changed or removed in future versions without notice. >>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>> changed or removed in future versions without notice. >>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>> be changed or removed in future versions without notice. >>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>> be changed or removed in future versions without notice. >>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >>>> JBAS016002: Processing weld deployment ag-push.war >>>> 10:16:47,154 INFO >>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>> are as follows: >>>> >>>> >>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>> >>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>> >>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>> java:global/ag-push/ClientInstallationServiceImpl >>>> java:app/ag-push/ClientInstallationServiceImpl >>>> java:module/ClientInstallationServiceImpl >>>> >>>> 10:16:47,155 INFO >>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>> as follows: >>>> >>>> >>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>> >>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>> >>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>> java:global/ag-push/GenericVariantServiceImpl >>>> java:app/ag-push/GenericVariantServiceImpl >>>> java:module/GenericVariantServiceImpl >>>> >>>> 10:16:47,155 INFO >>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>> as follows: >>>> >>>> >>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>> >>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>> >>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>> java:global/ag-push/PushApplicationServiceImpl >>>> java:app/ag-push/PushApplicationServiceImpl >>>> java:module/PushApplicationServiceImpl >>>> >>>> 10:16:47,156 INFO >>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>> "ag-push.war" are as follows: >>>> >>>> >>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>> >>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>> >>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>> java:module/DeleteOldPushMessageInformationScheduler >>>> >>>> 10:16:47,156 INFO >>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>> follows: >>>> >>>> >>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>> >>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>> >>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>> java:global/ag-push/SenderServiceImpl >>>> java:app/ag-push/SenderServiceImpl >>>> java:module/SenderServiceImpl >>>> >>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) >>>> JBAS016005: Starting Services for CDI deployment: ag-push.war >>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >>>> WELD-000900 1.1.23 (redhat) >>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>> 1-2) MSC000001: Failed to start service >>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>> org.jboss.msc.service.StartException in service >>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>> phase INSTALL of deployment "ag-push.war" >>>> at >>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>> 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] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>> [rt.jar:1.7.0_75] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>> [rt.jar:1.7.0_75] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>> Caused by: >>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>> JBAS018096: Error instantiating container component: >>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>> at >>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>> at >>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>> at >>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>> at >>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>> ... 5 more >>>> Caused by: java.lang.ClassNotFoundException: >>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>> "deployment.ag-push.war:main" from Service Module Loader] >>>> at >>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>> at >>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>> at >>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>> at >>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>> at >>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>> at >>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>> ... 8 more >>>> >>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool -- >>>> 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the >>>> following failure message: >>>> { >>>> "JBAS014671: Failed services" => >>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>> "org.jboss.msc.service.StartException in service >>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>> process phase INSTALL of deployment \"ag-push.war\" >>>> Caused by: >>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>> JBAS018096: Error instantiating container component: >>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>> Caused by: java.lang.ClassNotFoundException: >>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>> } >>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service thread >>>> 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) >>>> in 29ms >>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread Pool >>>> -- 14) JBAS014774: Service status report >>>> JBAS014775: New missing/unsatisfied dependencies: >>>> service jboss.deployment.unit."ag-push.war".beanmanager (missing) >>>> dependents: [service >>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>> JBAS014777: Services which failed to start: service >>>> jboss.deployment.unit."ag-push.war".INSTALL >>>> >>>> >>>> Thanks for help ... >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150224/d1181856/attachment-0001.html From ivan.gurtler at ahead-itec.com Tue Feb 24 04:46:32 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 10:46:32 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: You mean in JIRA for AG ??? *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : > Ivan, > > can you file a JIRA ticket for this? > > On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf > wrote: > >> yeah, I now see it: >> >> KeycloakAuthenticatorValve >> Caused by: java.lang.ClassNotFoundException: >> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >> >> >> looks like an issue w/ the KC adapter for AS7, that comes with the 1.1.x >> series of Keycloak - I will take a look in a bit >> >> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> yes ... I use AS7 version .. >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>> >>>> >>>> >>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>> ivan.gurtler at ahead-itec.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I try to deploy 2 .war files ... build from master branch. I use JBoss >>>>> EAP 6.3 in domain mode. Profile: default. >>>>> >>>>> I have problem with depolying ag-push.war... >>>>> >>>> >>>> you used the one from the as7 server folder ? >>>> >>>> >>>> >>>> >>>>> >>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>> point to a valid jar for a Class-Path reference. >>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) >>>>> JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>> annotations but beans.xml was not found. >>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>> serviceName={ >>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>> portName={http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>> annotationWsdlLocation=null >>>>> wsdlLocationOverride=null >>>>> mtomEnabled=false >>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>> serviceName={ >>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>> portName={ >>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>> annotationWsdlLocation=null >>>>> wsdlLocationOverride=null >>>>> mtomEnabled=false >>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>> JBAS018210: Register web context: /AheadCMS-Frontend >>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>> removed in future versions without notice. >>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>> removed in future versions without notice. >>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>> changed or removed in future versions without notice. >>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>> changed or removed in future versions without notice. >>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>> be changed or removed in future versions without notice. >>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>> be changed or removed in future versions without notice. >>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>>>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>>>> unsupported module ("org.infinispan:main") which may be changed or removed >>>>> in future versions without notice. >>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>>>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>>>> unsupported module ("org.infinispan:main") which may be changed or removed >>>>> in future versions without notice. >>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>> JBAS018210: Register web context: /EnvTest-1.0 >>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>> JBAS018210: Register web context: /auth >>>>> 10:16:14,145 INFO >>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>> thread 1-2) Creating Service { >>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >>>>> class com.aheaditec.cms.backend.webservice.WebApi >>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>> 4.3.1.Final-redhat-1 >>>>> 10:16:14,958 INFO >>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>> Thread Pool -- 51) Load config from >>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>> thread 1-2) Setting the server's publish address to be >>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>> 1-2) JBWS024074: WSDL published to: >>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>> 10:16:16,493 INFO >>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>> thread 1-2) Creating Service { >>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>> thread 1-2) Setting the server's publish address to be >>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>> 1-2) JBWS024074: WSDL published to: >>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >>>>> JBAS015539: Starting service jboss.ws.port-component-link >>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread 1-1) >>>>> JBAS015539: Starting service >>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread 1-2) >>>>> JBAS015539: Starting service >>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- >>>>> 50) JBAS011402: Starting Persistence Unit Service >>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>> Annotations {4.0.1.Final-redhat-2} >>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool >>>>> -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>> [ >>>>> name: persistenceUnit >>>>> ...] >>>>> 10:16:17,838 INFO >>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>> connection provider: >>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>> org.hibernate.dialect.Oracle10gDialect >>>>> 10:16:18,983 INFO >>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>> 10:16:19,008 INFO >>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>>>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>> getCurrentSession() >>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>> JBAS018210: Register web context: /AheadCMS-Backend >>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>> org.hibernate.dialect.Oracle10gDialect >>>>> 10:16:22,141 INFO >>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>> 10:16:22,145 INFO >>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>>>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>>>> 10:16:24,077 INFO >>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>> org.hibernate.dialect.Oracle10gDialect >>>>> 10:16:28,669 INFO >>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>> 10:16:28,670 INFO >>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>> 10:16:29,687 INFO [org.keycloak.services.managers.ApplianceBootstrap] >>>>> (ServerService Thread Pool -- 51) Initializing master realm >>>>> 10:16:33,552 INFO >>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>> /WEB-INF/ups-realm.json >>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>> javax.ws.rs.core.Application >>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>> org.keycloak.services.resources.SocialResource from Application >>>>> javax.ws.rs.core.Application >>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>> org.keycloak.services.resources.RealmsResource from Application >>>>> javax.ws.rs.core.Application >>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>> javax.ws.rs.core.Application >>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>> "AheadCMS-Frontend.war") >>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>> "AheadCMS-Backend.war") >>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in >>>>> 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>> on-demand) >>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>> "ag-push.war") >>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>> removed in future versions without notice. >>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>> removed in future versions without notice. >>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>> changed or removed in future versions without notice. >>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>> changed or removed in future versions without notice. >>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>> be changed or removed in future versions without notice. >>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>> be changed or removed in future versions without notice. >>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >>>>> JBAS016002: Processing weld deployment ag-push.war >>>>> 10:16:47,154 INFO >>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>> are as follows: >>>>> >>>>> >>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>> >>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>> >>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>> java:module/ClientInstallationServiceImpl >>>>> >>>>> 10:16:47,155 INFO >>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>> as follows: >>>>> >>>>> >>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>> >>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>> >>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>> java:global/ag-push/GenericVariantServiceImpl >>>>> java:app/ag-push/GenericVariantServiceImpl >>>>> java:module/GenericVariantServiceImpl >>>>> >>>>> 10:16:47,155 INFO >>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>> as follows: >>>>> >>>>> >>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>> >>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>> >>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>> java:global/ag-push/PushApplicationServiceImpl >>>>> java:app/ag-push/PushApplicationServiceImpl >>>>> java:module/PushApplicationServiceImpl >>>>> >>>>> 10:16:47,156 INFO >>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>> "ag-push.war" are as follows: >>>>> >>>>> >>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>> >>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>> >>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>> >>>>> 10:16:47,156 INFO >>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>> follows: >>>>> >>>>> >>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>> >>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>> >>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>> java:global/ag-push/SenderServiceImpl >>>>> java:app/ag-push/SenderServiceImpl >>>>> java:module/SenderServiceImpl >>>>> >>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) >>>>> JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >>>>> WELD-000900 1.1.23 (redhat) >>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>>> 1-2) MSC000001: Failed to start service >>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>> org.jboss.msc.service.StartException in service >>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>> phase INSTALL of deployment "ag-push.war" >>>>> at >>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>> 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] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>> [rt.jar:1.7.0_75] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>> [rt.jar:1.7.0_75] >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>> Caused by: >>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>> JBAS018096: Error instantiating container component: >>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>> at >>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>> at >>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>> at >>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>> at >>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>> ... 5 more >>>>> Caused by: java.lang.ClassNotFoundException: >>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>> at >>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>> at >>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>> at >>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>> at >>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>> at >>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>> at >>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>> ... 8 more >>>>> >>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool -- >>>>> 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the >>>>> following failure message: >>>>> { >>>>> "JBAS014671: Failed services" => >>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>> "org.jboss.msc.service.StartException in service >>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>> Caused by: >>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>> JBAS018096: Error instantiating container component: >>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>> Caused by: java.lang.ClassNotFoundException: >>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>> } >>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>> ag-push.war) in 29ms >>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>> Pool -- 14) JBAS014774: Service status report >>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>> (missing) dependents: [service >>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>> JBAS014777: Services which failed to start: service >>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>> >>>>> >>>>> Thanks for help ... >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20150224/50d21ad4/attachment-0001.html From matzew at apache.org Tue Feb 24 04:50:16 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 10:50:16 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: yep, in here please :-) https://issues.jboss.org/browse/AGPUSH On Tue, Feb 24, 2015 at 10:46 AM, Ivan G?rtler wrote: > You mean in JIRA for AG ??? > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : > >> Ivan, >> >> can you file a JIRA ticket for this? >> >> On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf >> wrote: >> >>> yeah, I now see it: >>> >>> KeycloakAuthenticatorValve >>> Caused by: java.lang.ClassNotFoundException: >>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>> >>> >>> looks like an issue w/ the KC adapter for AS7, that comes with the 1.1.x >>> series of Keycloak - I will take a look in a bit >>> >>> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> yes ... I use AS7 version .. >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>>> >>>>> >>>>> >>>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I try to deploy 2 .war files ... build from master branch. I use >>>>>> JBoss EAP 6.3 in domain mode. Profile: default. >>>>>> >>>>>> I have problem with depolying ag-push.war... >>>>>> >>>>> >>>>> you used the one from the as7 server folder ? >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>>> point to a valid jar for a Class-Path reference. >>>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) >>>>>> JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>>> annotations but beans.xml was not found. >>>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>> serviceName={ >>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>> portName={ >>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>>> annotationWsdlLocation=null >>>>>> wsdlLocationOverride=null >>>>>> mtomEnabled=false >>>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>> serviceName={ >>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>> portName={ >>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>>> annotationWsdlLocation=null >>>>>> wsdlLocationOverride=null >>>>>> mtomEnabled=false >>>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>>> JBAS018210: Register web context: /AheadCMS-Frontend >>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>> removed in future versions without notice. >>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>> removed in future versions without notice. >>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>> changed or removed in future versions without notice. >>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>> changed or removed in future versions without notice. >>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>> be changed or removed in future versions without notice. >>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>> be changed or removed in future versions without notice. >>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>>>>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>>>>> unsupported module ("org.infinispan:main") which may be changed or removed >>>>>> in future versions without notice. >>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC service >>>>>> thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is using an >>>>>> unsupported module ("org.infinispan:main") which may be changed or removed >>>>>> in future versions without notice. >>>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>>> JBAS018210: Register web context: /EnvTest-1.0 >>>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>>> JBAS018210: Register web context: /auth >>>>>> 10:16:14,145 INFO >>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>> thread 1-2) Creating Service { >>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >>>>>> class com.aheaditec.cms.backend.webservice.WebApi >>>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>>> 4.3.1.Final-redhat-1 >>>>>> 10:16:14,958 INFO >>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>> Thread Pool -- 51) Load config from >>>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>>> thread 1-2) Setting the server's publish address to be >>>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>>> 1-2) JBWS024074: WSDL published to: >>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>>> 10:16:16,493 INFO >>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>> thread 1-2) Creating Service { >>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>>> thread 1-2) Setting the server's publish address to be >>>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>>> 1-2) JBWS024074: WSDL published to: >>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread >>>>>> 1-1) JBAS015539: Starting service jboss.ws.port-component-link >>>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread >>>>>> 1-1) JBAS015539: Starting service >>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread >>>>>> 1-2) JBAS015539: Starting service >>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- >>>>>> 50) JBAS011402: Starting Persistence Unit Service >>>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>>> Annotations {4.0.1.Final-redhat-2} >>>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread Pool >>>>>> -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>>> [ >>>>>> name: persistenceUnit >>>>>> ...] >>>>>> 10:16:17,838 INFO >>>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>>> connection provider: >>>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>> 10:16:18,983 INFO >>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>> 10:16:19,008 INFO >>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>>>>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>>> getCurrentSession() >>>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>>> JBAS018210: Register web context: /AheadCMS-Backend >>>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>> 10:16:22,141 INFO >>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>> 10:16:22,145 INFO >>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] (ServerService >>>>>> Thread Pool -- 50) Unrecognized value for "hibernate.hbm2ddl.auto": none >>>>>> 10:16:24,077 INFO >>>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>> 10:16:28,669 INFO >>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>> 10:16:28,670 INFO >>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>>> 10:16:29,687 INFO >>>>>> [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread >>>>>> Pool -- 51) Initializing master realm >>>>>> 10:16:33,552 INFO >>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>>> /WEB-INF/ups-realm.json >>>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>>> javax.ws.rs.core.Application >>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>> org.keycloak.services.resources.SocialResource from Application >>>>>> javax.ws.rs.core.Application >>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>> org.keycloak.services.resources.RealmsResource from Application >>>>>> javax.ws.rs.core.Application >>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>>> javax.ws.rs.core.Application >>>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>>> "AheadCMS-Frontend.war") >>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>>> "AheadCMS-Backend.war") >>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in >>>>>> 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>>> on-demand) >>>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>>> "ag-push.war") >>>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>> removed in future versions without notice. >>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>> removed in future versions without notice. >>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>> changed or removed in future versions without notice. >>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>> changed or removed in future versions without notice. >>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>> be changed or removed in future versions without notice. >>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>> be changed or removed in future versions without notice. >>>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) >>>>>> JBAS016002: Processing weld deployment ag-push.war >>>>>> 10:16:47,154 INFO >>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>>> are as follows: >>>>>> >>>>>> >>>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>> >>>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>> >>>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>>> java:module/ClientInstallationServiceImpl >>>>>> >>>>>> 10:16:47,155 INFO >>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>>> as follows: >>>>>> >>>>>> >>>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>> >>>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>> >>>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>> java:global/ag-push/GenericVariantServiceImpl >>>>>> java:app/ag-push/GenericVariantServiceImpl >>>>>> java:module/GenericVariantServiceImpl >>>>>> >>>>>> 10:16:47,155 INFO >>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>>> as follows: >>>>>> >>>>>> >>>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>> >>>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>> >>>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>> java:global/ag-push/PushApplicationServiceImpl >>>>>> java:app/ag-push/PushApplicationServiceImpl >>>>>> java:module/PushApplicationServiceImpl >>>>>> >>>>>> 10:16:47,156 INFO >>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>>> "ag-push.war" are as follows: >>>>>> >>>>>> >>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>> >>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>> >>>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>>> >>>>>> 10:16:47,156 INFO >>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>>> follows: >>>>>> >>>>>> >>>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>> >>>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>> >>>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>> java:global/ag-push/SenderServiceImpl >>>>>> java:app/ag-push/SenderServiceImpl >>>>>> java:module/SenderServiceImpl >>>>>> >>>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) >>>>>> JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >>>>>> WELD-000900 1.1.23 (redhat) >>>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>>>> 1-2) MSC000001: Failed to start service >>>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>>> org.jboss.msc.service.StartException in service >>>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>>> phase INSTALL of deployment "ag-push.war" >>>>>> at >>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>> 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] >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>> [rt.jar:1.7.0_75] >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>> [rt.jar:1.7.0_75] >>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>>> Caused by: >>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>> JBAS018096: Error instantiating container component: >>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>> at >>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>>> at >>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>>> at >>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>>> at >>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>> ... 5 more >>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>>> at >>>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>> at >>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>> at >>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>> at >>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>> at >>>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>> at >>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>>> ... 8 more >>>>>> >>>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool >>>>>> -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with >>>>>> the following failure message: >>>>>> { >>>>>> "JBAS014671: Failed services" => >>>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>>> "org.jboss.msc.service.StartException in service >>>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>>> Caused by: >>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>> JBAS018096: Error instantiating container component: >>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>>> } >>>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>>> ag-push.war) in 29ms >>>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>>> Pool -- 14) JBAS014774: Service status report >>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>>> (missing) dependents: [service >>>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>>> JBAS014777: Services which failed to start: service >>>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>>> >>>>>> >>>>>> Thanks for help ... >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20150224/fdf60d93/attachment-0001.html From matzew at apache.org Tue Feb 24 05:06:30 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 11:06:30 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: Hey Ivan, here is a branch that contains the fix: https://github.com/aerogear/aerogear-unifiedpush-server/tree/KC_master_package_renamed On Tue, Feb 24, 2015 at 10:50 AM, Matthias Wessendorf wrote: > yep, in here please :-) > https://issues.jboss.org/browse/AGPUSH > > On Tue, Feb 24, 2015 at 10:46 AM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> You mean in JIRA for AG ??? >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : >> >>> Ivan, >>> >>> can you file a JIRA ticket for this? >>> >>> On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf >> > wrote: >>> >>>> yeah, I now see it: >>>> >>>> KeycloakAuthenticatorValve >>>> Caused by: java.lang.ClassNotFoundException: >>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>> >>>> >>>> looks like an issue w/ the KC adapter for AS7, that comes with the >>>> 1.1.x series of Keycloak - I will take a look in a bit >>>> >>>> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >>>> ivan.gurtler at ahead-itec.com> wrote: >>>> >>>>> yes ... I use AS7 version .. >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>>>> >>>>>> >>>>>> >>>>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I try to deploy 2 .war files ... build from master branch. I use >>>>>>> JBoss EAP 6.3 in domain mode. Profile: default. >>>>>>> >>>>>>> I have problem with depolying ag-push.war... >>>>>>> >>>>>> >>>>>> you used the one from the as7 server folder ? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>>>> point to a valid jar for a Class-Path reference. >>>>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread >>>>>>> 1-2) JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>>>> annotations but beans.xml was not found. >>>>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>> serviceName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>> portName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>>>> annotationWsdlLocation=null >>>>>>> wsdlLocationOverride=null >>>>>>> mtomEnabled=false >>>>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>> serviceName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>> portName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>>>> annotationWsdlLocation=null >>>>>>> wsdlLocationOverride=null >>>>>>> mtomEnabled=false >>>>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>>>> JBAS018210: Register web context: /AheadCMS-Frontend >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>>>> JBAS018210: Register web context: /EnvTest-1.0 >>>>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>>>> JBAS018210: Register web context: /auth >>>>>>> 10:16:14,145 INFO >>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>> thread 1-2) Creating Service { >>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >>>>>>> class com.aheaditec.cms.backend.webservice.WebApi >>>>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>>>> 4.3.1.Final-redhat-1 >>>>>>> 10:16:14,958 INFO >>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>> Thread Pool -- 51) Load config from >>>>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>>>> thread 1-2) Setting the server's publish address to be >>>>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>>>> 1-2) JBWS024074: WSDL published to: >>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>>>> 10:16:16,493 INFO >>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>> thread 1-2) Creating Service { >>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>>>> thread 1-2) Setting the server's publish address to be >>>>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>>>> 1-2) JBWS024074: WSDL published to: >>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>> 1-1) JBAS015539: Starting service jboss.ws.port-component-link >>>>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>> 1-1) JBAS015539: Starting service >>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>> 1-2) JBAS015539: Starting service >>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- >>>>>>> 50) JBAS011402: Starting Persistence Unit Service >>>>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>>>> Annotations {4.0.1.Final-redhat-2} >>>>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread >>>>>>> Pool -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>>>> [ >>>>>>> name: persistenceUnit >>>>>>> ...] >>>>>>> 10:16:17,838 INFO >>>>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>>>> connection provider: >>>>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>> 10:16:18,983 INFO >>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>> 10:16:19,008 INFO >>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>>>> getCurrentSession() >>>>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>>>> JBAS018210: Register web context: /AheadCMS-Backend >>>>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>> 10:16:22,141 INFO >>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>> 10:16:22,145 INFO >>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>> 10:16:24,077 INFO >>>>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>> 10:16:28,669 INFO >>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>> 10:16:28,670 INFO >>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>>>> 10:16:29,687 INFO >>>>>>> [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread >>>>>>> Pool -- 51) Initializing master realm >>>>>>> 10:16:33,552 INFO >>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>>>> /WEB-INF/ups-realm.json >>>>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.SocialResource from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.RealmsResource from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>>>> "AheadCMS-Frontend.war") >>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>>>> "AheadCMS-Backend.war") >>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started >>>>>>> in 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>>>> on-demand) >>>>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>>>> "ag-push.war") >>>>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>> 1-1) JBAS016002: Processing weld deployment ag-push.war >>>>>>> 10:16:47,154 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>>>> are as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>> >>>>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>> >>>>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>>>> java:module/ClientInstallationServiceImpl >>>>>>> >>>>>>> 10:16:47,155 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>> as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>> >>>>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>> >>>>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>> java:global/ag-push/GenericVariantServiceImpl >>>>>>> java:app/ag-push/GenericVariantServiceImpl >>>>>>> java:module/GenericVariantServiceImpl >>>>>>> >>>>>>> 10:16:47,155 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>> as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>> >>>>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>> >>>>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>> java:global/ag-push/PushApplicationServiceImpl >>>>>>> java:app/ag-push/PushApplicationServiceImpl >>>>>>> java:module/PushApplicationServiceImpl >>>>>>> >>>>>>> 10:16:47,156 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>>>> "ag-push.war" are as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>> >>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>> >>>>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>>>> >>>>>>> 10:16:47,156 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>>>> follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>> >>>>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>> >>>>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>> java:global/ag-push/SenderServiceImpl >>>>>>> java:app/ag-push/SenderServiceImpl >>>>>>> java:module/SenderServiceImpl >>>>>>> >>>>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>> 1-2) JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >>>>>>> WELD-000900 1.1.23 (redhat) >>>>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>>>>> 1-2) MSC000001: Failed to start service >>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>>>> org.jboss.msc.service.StartException in service >>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>>>> phase INSTALL of deployment "ag-push.war" >>>>>>> at >>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>> 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] >>>>>>> at >>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>> [rt.jar:1.7.0_75] >>>>>>> at >>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>> [rt.jar:1.7.0_75] >>>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>>>> Caused by: >>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>> JBAS018096: Error instantiating container component: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>>>> at >>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>> ... 5 more >>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>>>> at >>>>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>>>> ... 8 more >>>>>>> >>>>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool >>>>>>> -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with >>>>>>> the following failure message: >>>>>>> { >>>>>>> "JBAS014671: Failed services" => >>>>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>>>> "org.jboss.msc.service.StartException in service >>>>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>>>> Caused by: >>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>> JBAS018096: Error instantiating container component: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>>>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>>>> } >>>>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>>>> ag-push.war) in 29ms >>>>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>>>> Pool -- 14) JBAS014774: Service status report >>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>>>> (missing) dependents: [service >>>>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>>>> JBAS014777: Services which failed to start: service >>>>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>>>> >>>>>>> >>>>>>> Thanks for help ... >>>>>>> >>>>>>> *Mgr. Ivan G?rtler* >>>>>>> Mobile software developer >>>>>>> >>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>> 602 00 Brno (Czech Republic) >>>>>>> >>>>>>> www.ahead-itec.com | twitter | >>>>>>> mobile security solutions >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/14ed0514/attachment-0001.html From matzew at apache.org Tue Feb 24 05:11:55 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 11:11:55 +0100 Subject: [aerogear-dev] Release: New parent staged (was: Re: parent release ?) Message-ID: Hi, as discussed below, we need a new parent release to get the latest of APNs into master. I have executed the release procedure and staged the pom files at: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4932/ please give it a shot, otherwise I will release it late Thursday, so that we can update it shortly afterwards. Cheers, Matthias On Wed, Feb 18, 2015 at 1:55 PM, Matthias Wessendorf wrote: > Hi, > > becasuse of https://github.com/aerogear/aerogear-parent/pull/41 got > merged, I'd like to run another parent release - yay! > > However, just wondering, do any other folks have wishes to update some 3rd > party dependencies in there ? > > Thanks! > > > -- > 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/20150224/3055b770/attachment.html From ivan.gurtler at ahead-itec.com Tue Feb 24 05:13:20 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 11:13:20 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: is it ok ? ... https://issues.jboss.org/browse/AGPUSH-1294 *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-24 10:50 GMT+01:00 Matthias Wessendorf : > yep, in here please :-) > https://issues.jboss.org/browse/AGPUSH > > On Tue, Feb 24, 2015 at 10:46 AM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> You mean in JIRA for AG ??? >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : >> >>> Ivan, >>> >>> can you file a JIRA ticket for this? >>> >>> On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf >> > wrote: >>> >>>> yeah, I now see it: >>>> >>>> KeycloakAuthenticatorValve >>>> Caused by: java.lang.ClassNotFoundException: >>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>> >>>> >>>> looks like an issue w/ the KC adapter for AS7, that comes with the >>>> 1.1.x series of Keycloak - I will take a look in a bit >>>> >>>> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >>>> ivan.gurtler at ahead-itec.com> wrote: >>>> >>>>> yes ... I use AS7 version .. >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>>>> >>>>>> >>>>>> >>>>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I try to deploy 2 .war files ... build from master branch. I use >>>>>>> JBoss EAP 6.3 in domain mode. Profile: default. >>>>>>> >>>>>>> I have problem with depolying ag-push.war... >>>>>>> >>>>>> >>>>>> you used the one from the as7 server folder ? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>>>> point to a valid jar for a Class-Path reference. >>>>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread >>>>>>> 1-2) JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>>>> annotations but beans.xml was not found. >>>>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>> serviceName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>> portName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>>>> annotationWsdlLocation=null >>>>>>> wsdlLocationOverride=null >>>>>>> mtomEnabled=false >>>>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>> serviceName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>> portName={ >>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>>>> annotationWsdlLocation=null >>>>>>> wsdlLocationOverride=null >>>>>>> mtomEnabled=false >>>>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>>>> JBAS018210: Register web context: /AheadCMS-Frontend >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>>>> JBAS018210: Register web context: /EnvTest-1.0 >>>>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- 51) >>>>>>> JBAS018210: Register web context: /auth >>>>>>> 10:16:14,145 INFO >>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>> thread 1-2) Creating Service { >>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService from >>>>>>> class com.aheaditec.cms.backend.webservice.WebApi >>>>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>>>> 4.3.1.Final-redhat-1 >>>>>>> 10:16:14,958 INFO >>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>> Thread Pool -- 51) Load config from >>>>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>>>> thread 1-2) Setting the server's publish address to be >>>>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>>>> 1-2) JBWS024074: WSDL published to: >>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>>>> 10:16:16,493 INFO >>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>> thread 1-2) Creating Service { >>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service >>>>>>> thread 1-2) Setting the server's publish address to be >>>>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service thread >>>>>>> 1-2) JBWS024074: WSDL published to: >>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>> 1-1) JBAS015539: Starting service jboss.ws.port-component-link >>>>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>> 1-1) JBAS015539: Starting service >>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>> 1-2) JBAS015539: Starting service >>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- >>>>>>> 50) JBAS011402: Starting Persistence Unit Service >>>>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>>>> Annotations {4.0.1.Final-redhat-2} >>>>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread >>>>>>> Pool -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>>>> [ >>>>>>> name: persistenceUnit >>>>>>> ...] >>>>>>> 10:16:17,838 INFO >>>>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>>>> connection provider: >>>>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>> 10:16:18,983 INFO >>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>> 10:16:19,008 INFO >>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>>>> getCurrentSession() >>>>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- 50) >>>>>>> JBAS018210: Register web context: /AheadCMS-Backend >>>>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>> 10:16:22,141 INFO >>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>> 10:16:22,145 INFO >>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>> 10:16:24,077 INFO >>>>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>> 10:16:28,669 INFO >>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>> 10:16:28,670 INFO >>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>>>> 10:16:29,687 INFO >>>>>>> [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread >>>>>>> Pool -- 51) Initializing master realm >>>>>>> 10:16:33,552 INFO >>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>>>> /WEB-INF/ups-realm.json >>>>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.SocialResource from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.RealmsResource from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>>>> javax.ws.rs.core.Application >>>>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>>>> "AheadCMS-Frontend.war") >>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>>>> "AheadCMS-Backend.war") >>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started >>>>>>> in 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>>>> on-demand) >>>>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>>>> "ag-push.war") >>>>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>> removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>> changed or removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>> be changed or removed in future versions without notice. >>>>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>> 1-1) JBAS016002: Processing weld deployment ag-push.war >>>>>>> 10:16:47,154 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>>>> are as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>> >>>>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>> >>>>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>>>> java:module/ClientInstallationServiceImpl >>>>>>> >>>>>>> 10:16:47,155 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>> as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>> >>>>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>> >>>>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>> java:global/ag-push/GenericVariantServiceImpl >>>>>>> java:app/ag-push/GenericVariantServiceImpl >>>>>>> java:module/GenericVariantServiceImpl >>>>>>> >>>>>>> 10:16:47,155 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>> as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>> >>>>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>> >>>>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>> java:global/ag-push/PushApplicationServiceImpl >>>>>>> java:app/ag-push/PushApplicationServiceImpl >>>>>>> java:module/PushApplicationServiceImpl >>>>>>> >>>>>>> 10:16:47,156 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>>>> "ag-push.war" are as follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>> >>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>> >>>>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>>>> >>>>>>> 10:16:47,156 INFO >>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>>>> follows: >>>>>>> >>>>>>> >>>>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>> >>>>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>> >>>>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>> java:global/ag-push/SenderServiceImpl >>>>>>> java:app/ag-push/SenderServiceImpl >>>>>>> java:module/SenderServiceImpl >>>>>>> >>>>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>> 1-2) JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread 1-2) >>>>>>> WELD-000900 1.1.23 (redhat) >>>>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>>>>> 1-2) MSC000001: Failed to start service >>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>>>> org.jboss.msc.service.StartException in service >>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>>>> phase INSTALL of deployment "ag-push.war" >>>>>>> at >>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>> 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] >>>>>>> at >>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>> [rt.jar:1.7.0_75] >>>>>>> at >>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>> [rt.jar:1.7.0_75] >>>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>>>> Caused by: >>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>> JBAS018096: Error instantiating container component: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>>>> at >>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>> ... 5 more >>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>>>> at >>>>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>> at >>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>>>> ... 8 more >>>>>>> >>>>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool >>>>>>> -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with >>>>>>> the following failure message: >>>>>>> { >>>>>>> "JBAS014671: Failed services" => >>>>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>>>> "org.jboss.msc.service.StartException in service >>>>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>>>> Caused by: >>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>> JBAS018096: Error instantiating container component: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>>>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>>>> } >>>>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>>>> ag-push.war) in 29ms >>>>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>>>> Pool -- 14) JBAS014774: Service status report >>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>>>> (missing) dependents: [service >>>>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>>>> JBAS014777: Services which failed to start: service >>>>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>>>> >>>>>>> >>>>>>> Thanks for help ... >>>>>>> >>>>>>> *Mgr. Ivan G?rtler* >>>>>>> Mobile software developer >>>>>>> >>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>> 602 00 Brno (Czech Republic) >>>>>>> >>>>>>> www.ahead-itec.com | twitter | >>>>>>> mobile security solutions >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/804ae445/attachment-0001.html From ivan.gurtler at ahead-itec.com Tue Feb 24 05:15:18 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 11:15:18 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: Thanks ... I will try it ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-24 11:06 GMT+01:00 Matthias Wessendorf : > Hey Ivan, > > here is a branch that contains the fix: > > https://github.com/aerogear/aerogear-unifiedpush-server/tree/KC_master_package_renamed > > > On Tue, Feb 24, 2015 at 10:50 AM, Matthias Wessendorf > wrote: > >> yep, in here please :-) >> https://issues.jboss.org/browse/AGPUSH >> >> On Tue, Feb 24, 2015 at 10:46 AM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> You mean in JIRA for AG ??? >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : >>> >>>> Ivan, >>>> >>>> can you file a JIRA ticket for this? >>>> >>>> On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf < >>>> matzew at apache.org> wrote: >>>> >>>>> yeah, I now see it: >>>>> >>>>> KeycloakAuthenticatorValve >>>>> Caused by: java.lang.ClassNotFoundException: >>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>> >>>>> >>>>> looks like an issue w/ the KC adapter for AS7, that comes with the >>>>> 1.1.x series of Keycloak - I will take a look in a bit >>>>> >>>>> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> yes ... I use AS7 version .. >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I try to deploy 2 .war files ... build from master branch. I use >>>>>>>> JBoss EAP 6.3 in domain mode. Profile: default. >>>>>>>> >>>>>>>> I have problem with depolying ag-push.war... >>>>>>>> >>>>>>> >>>>>>> you used the one from the as7 server folder ? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>>>>> point to a valid jar for a Class-Path reference. >>>>>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread >>>>>>>> 1-2) JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>>>>> annotations but beans.xml was not found. >>>>>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>>> serviceName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>>> portName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>>>>> annotationWsdlLocation=null >>>>>>>> wsdlLocationOverride=null >>>>>>>> mtomEnabled=false >>>>>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>>> serviceName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>>> portName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>>>>> annotationWsdlLocation=null >>>>>>>> wsdlLocationOverride=null >>>>>>>> mtomEnabled=false >>>>>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 50) JBAS018210: Register web context: /AheadCMS-Frontend >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 51) JBAS018210: Register web context: /EnvTest-1.0 >>>>>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 51) JBAS018210: Register web context: /auth >>>>>>>> 10:16:14,145 INFO >>>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>>> thread 1-2) Creating Service { >>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>>> from class com.aheaditec.cms.backend.webservice.WebApi >>>>>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>>>>> 4.3.1.Final-redhat-1 >>>>>>>> 10:16:14,958 INFO >>>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>>> Thread Pool -- 51) Load config from >>>>>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC >>>>>>>> service thread 1-2) Setting the server's publish address to be >>>>>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service >>>>>>>> thread 1-2) JBWS024074: WSDL published to: >>>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>>>>> 10:16:16,493 INFO >>>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>>> thread 1-2) Creating Service { >>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC >>>>>>>> service thread 1-2) Setting the server's publish address to be >>>>>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service >>>>>>>> thread 1-2) JBWS024074: WSDL published to: >>>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>> 1-1) JBAS015539: Starting service jboss.ws.port-component-link >>>>>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>> 1-1) JBAS015539: Starting service >>>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>> 1-2) JBAS015539: Starting service >>>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- >>>>>>>> 50) JBAS011402: Starting Persistence Unit Service >>>>>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>>>>> Annotations {4.0.1.Final-redhat-2} >>>>>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread >>>>>>>> Pool -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>>>>> [ >>>>>>>> name: persistenceUnit >>>>>>>> ...] >>>>>>>> 10:16:17,838 INFO >>>>>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>>>>> connection provider: >>>>>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>> 10:16:18,983 INFO >>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>> 10:16:19,008 INFO >>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>>>>> getCurrentSession() >>>>>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 50) JBAS018210: Register web context: /AheadCMS-Backend >>>>>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>> 10:16:22,141 INFO >>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>> 10:16:22,145 INFO >>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>>> 10:16:24,077 INFO >>>>>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>> 10:16:28,669 INFO >>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>> 10:16:28,670 INFO >>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>> 10:16:29,687 INFO >>>>>>>> [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread >>>>>>>> Pool -- 51) Initializing master realm >>>>>>>> 10:16:33,552 INFO >>>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>>>>> /WEB-INF/ups-realm.json >>>>>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.SocialResource from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.RealmsResource from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>>>>> "AheadCMS-Frontend.war") >>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>>>>> "AheadCMS-Backend.war") >>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started >>>>>>>> in 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>>>>> on-demand) >>>>>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>>>>> "ag-push.war") >>>>>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>>> 1-1) JBAS016002: Processing weld deployment ag-push.war >>>>>>>> 10:16:47,154 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>>>>> are as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>> >>>>>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>> >>>>>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>>>>> java:module/ClientInstallationServiceImpl >>>>>>>> >>>>>>>> 10:16:47,155 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>>> as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>> >>>>>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>> >>>>>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>> java:global/ag-push/GenericVariantServiceImpl >>>>>>>> java:app/ag-push/GenericVariantServiceImpl >>>>>>>> java:module/GenericVariantServiceImpl >>>>>>>> >>>>>>>> 10:16:47,155 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>>> as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>> >>>>>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>> >>>>>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>> java:global/ag-push/PushApplicationServiceImpl >>>>>>>> java:app/ag-push/PushApplicationServiceImpl >>>>>>>> java:module/PushApplicationServiceImpl >>>>>>>> >>>>>>>> 10:16:47,156 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>>>>> "ag-push.war" are as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>> >>>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>> >>>>>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>>>>> >>>>>>>> 10:16:47,156 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>>>>> follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>> >>>>>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>> >>>>>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>> java:global/ag-push/SenderServiceImpl >>>>>>>> java:app/ag-push/SenderServiceImpl >>>>>>>> java:module/SenderServiceImpl >>>>>>>> >>>>>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>>> 1-2) JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread >>>>>>>> 1-2) WELD-000900 1.1.23 (redhat) >>>>>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>>>>>> 1-2) MSC000001: Failed to start service >>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>>>>> org.jboss.msc.service.StartException in service >>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>>>>> phase INSTALL of deployment "ag-push.war" >>>>>>>> at >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>>> 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] >>>>>>>> at >>>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>>> [rt.jar:1.7.0_75] >>>>>>>> at >>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>>> [rt.jar:1.7.0_75] >>>>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>>>>> Caused by: >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>>> JBAS018096: Error instantiating container component: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>>>>> at >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>>> ... 5 more >>>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>>>>> at >>>>>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>>>>> ... 8 more >>>>>>>> >>>>>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool >>>>>>>> -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with >>>>>>>> the following failure message: >>>>>>>> { >>>>>>>> "JBAS014671: Failed services" => >>>>>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>>>>> "org.jboss.msc.service.StartException in service >>>>>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>>>>> Caused by: >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>>> JBAS018096: Error instantiating container component: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>>>>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>>>>> } >>>>>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>>>>> ag-push.war) in 29ms >>>>>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>>>>> Pool -- 14) JBAS014774: Service status report >>>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>>>>> (missing) dependents: [service >>>>>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>>>>> JBAS014777: Services which failed to start: service >>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>>>>> >>>>>>>> >>>>>>>> Thanks for help ... >>>>>>>> >>>>>>>> *Mgr. Ivan G?rtler* >>>>>>>> Mobile software developer >>>>>>>> >>>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>>> 602 00 Brno (Czech Republic) >>>>>>>> >>>>>>>> www.ahead-itec.com | twitter | >>>>>>>> mobile security solutions >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matthias Wessendorf >>>>>>> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.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 >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150224/7e44d1c7/attachment-0001.html From matzew at apache.org Tue Feb 24 05:17:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 11:17:51 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: perfecto :) On Tue, Feb 24, 2015 at 11:13 AM, Ivan G?rtler wrote: > is it ok ? ... https://issues.jboss.org/browse/AGPUSH-1294 > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-24 10:50 GMT+01:00 Matthias Wessendorf : > >> yep, in here please :-) >> https://issues.jboss.org/browse/AGPUSH >> >> On Tue, Feb 24, 2015 at 10:46 AM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> You mean in JIRA for AG ??? >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : >>> >>>> Ivan, >>>> >>>> can you file a JIRA ticket for this? >>>> >>>> On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf < >>>> matzew at apache.org> wrote: >>>> >>>>> yeah, I now see it: >>>>> >>>>> KeycloakAuthenticatorValve >>>>> Caused by: java.lang.ClassNotFoundException: >>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>> >>>>> >>>>> looks like an issue w/ the KC adapter for AS7, that comes with the >>>>> 1.1.x series of Keycloak - I will take a look in a bit >>>>> >>>>> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> yes ... I use AS7 version .. >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I try to deploy 2 .war files ... build from master branch. I use >>>>>>>> JBoss EAP 6.3 in domain mode. Profile: default. >>>>>>>> >>>>>>>> I have problem with depolying ag-push.war... >>>>>>>> >>>>>>> >>>>>>> you used the one from the as7 server folder ? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>>>>> point to a valid jar for a Class-Path reference. >>>>>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread >>>>>>>> 1-2) JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>>>>> annotations but beans.xml was not found. >>>>>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>>> serviceName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>>> portName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>>>>> annotationWsdlLocation=null >>>>>>>> wsdlLocationOverride=null >>>>>>>> mtomEnabled=false >>>>>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>>> serviceName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>>> portName={ >>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>>>>> annotationWsdlLocation=null >>>>>>>> wsdlLocationOverride=null >>>>>>>> mtomEnabled=false >>>>>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 50) JBAS018210: Register web context: /AheadCMS-Frontend >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 51) JBAS018210: Register web context: /EnvTest-1.0 >>>>>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 51) JBAS018210: Register web context: /auth >>>>>>>> 10:16:14,145 INFO >>>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>>> thread 1-2) Creating Service { >>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>>> from class com.aheaditec.cms.backend.webservice.WebApi >>>>>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>>>>> 4.3.1.Final-redhat-1 >>>>>>>> 10:16:14,958 INFO >>>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>>> Thread Pool -- 51) Load config from >>>>>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC >>>>>>>> service thread 1-2) Setting the server's publish address to be >>>>>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service >>>>>>>> thread 1-2) JBWS024074: WSDL published to: >>>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>>>>> 10:16:16,493 INFO >>>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>>> thread 1-2) Creating Service { >>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC >>>>>>>> service thread 1-2) Setting the server's publish address to be >>>>>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service >>>>>>>> thread 1-2) JBWS024074: WSDL published to: >>>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>> 1-1) JBAS015539: Starting service jboss.ws.port-component-link >>>>>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>> 1-1) JBAS015539: Starting service >>>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>> 1-2) JBAS015539: Starting service >>>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- >>>>>>>> 50) JBAS011402: Starting Persistence Unit Service >>>>>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>>>>> Annotations {4.0.1.Final-redhat-2} >>>>>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread >>>>>>>> Pool -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>>>>> [ >>>>>>>> name: persistenceUnit >>>>>>>> ...] >>>>>>>> 10:16:17,838 INFO >>>>>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>>>>> connection provider: >>>>>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>> 10:16:18,983 INFO >>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>> 10:16:19,008 INFO >>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>>>>> getCurrentSession() >>>>>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>> 50) JBAS018210: Register web context: /AheadCMS-Backend >>>>>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>> 10:16:22,141 INFO >>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>> 10:16:22,145 INFO >>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>>> 10:16:24,077 INFO >>>>>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>> 10:16:28,669 INFO >>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>> 10:16:28,670 INFO >>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>> 10:16:29,687 INFO >>>>>>>> [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread >>>>>>>> Pool -- 51) Initializing master realm >>>>>>>> 10:16:33,552 INFO >>>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>>>>> /WEB-INF/ups-realm.json >>>>>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.SocialResource from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.RealmsResource from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>>>>> javax.ws.rs.core.Application >>>>>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>>>>> "AheadCMS-Frontend.war") >>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>>>>> "AheadCMS-Backend.war") >>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started >>>>>>>> in 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>>>>> on-demand) >>>>>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>>>>> "ag-push.war") >>>>>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>> removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>> changed or removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>> be changed or removed in future versions without notice. >>>>>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>>> 1-1) JBAS016002: Processing weld deployment ag-push.war >>>>>>>> 10:16:47,154 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>>>>> are as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>> >>>>>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>> >>>>>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>>>>> java:module/ClientInstallationServiceImpl >>>>>>>> >>>>>>>> 10:16:47,155 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>>> as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>> >>>>>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>> >>>>>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>> java:global/ag-push/GenericVariantServiceImpl >>>>>>>> java:app/ag-push/GenericVariantServiceImpl >>>>>>>> java:module/GenericVariantServiceImpl >>>>>>>> >>>>>>>> 10:16:47,155 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>>> as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>> >>>>>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>> >>>>>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>> java:global/ag-push/PushApplicationServiceImpl >>>>>>>> java:app/ag-push/PushApplicationServiceImpl >>>>>>>> java:module/PushApplicationServiceImpl >>>>>>>> >>>>>>>> 10:16:47,156 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>>>>> "ag-push.war" are as follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>> >>>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>> >>>>>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>>>>> >>>>>>>> 10:16:47,156 INFO >>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>>>>> follows: >>>>>>>> >>>>>>>> >>>>>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>> >>>>>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>> >>>>>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>> java:global/ag-push/SenderServiceImpl >>>>>>>> java:app/ag-push/SenderServiceImpl >>>>>>>> java:module/SenderServiceImpl >>>>>>>> >>>>>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>>> 1-2) JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread >>>>>>>> 1-2) WELD-000900 1.1.23 (redhat) >>>>>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>>>>>> 1-2) MSC000001: Failed to start service >>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>>>>> org.jboss.msc.service.StartException in service >>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>>>>> phase INSTALL of deployment "ag-push.war" >>>>>>>> at >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>>> 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] >>>>>>>> at >>>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>>> [rt.jar:1.7.0_75] >>>>>>>> at >>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>>> [rt.jar:1.7.0_75] >>>>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>>>>> Caused by: >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>>> JBAS018096: Error instantiating container component: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>>>>> at >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>>> ... 5 more >>>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>>>>> at >>>>>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>> at >>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>>>>> ... 8 more >>>>>>>> >>>>>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread Pool >>>>>>>> -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with >>>>>>>> the following failure message: >>>>>>>> { >>>>>>>> "JBAS014671: Failed services" => >>>>>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>>>>> "org.jboss.msc.service.StartException in service >>>>>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>>>>> Caused by: >>>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>>> JBAS018096: Error instantiating container component: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>>>> "JBAS014771: Services with missing/unavailable dependencies" => >>>>>>>> ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>>>>> } >>>>>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>>>>> ag-push.war) in 29ms >>>>>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>>>>> Pool -- 14) JBAS014774: Service status report >>>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>>>>> (missing) dependents: [service >>>>>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>>>>> JBAS014777: Services which failed to start: service >>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>>>>> >>>>>>>> >>>>>>>> Thanks for help ... >>>>>>>> >>>>>>>> *Mgr. Ivan G?rtler* >>>>>>>> Mobile software developer >>>>>>>> >>>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>>> 602 00 Brno (Czech Republic) >>>>>>>> >>>>>>>> www.ahead-itec.com | twitter | >>>>>>>> mobile security solutions >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matthias Wessendorf >>>>>>> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.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 >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/49ac1990/attachment-0001.html From matzew at apache.org Tue Feb 24 07:09:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 13:09:15 +0100 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: References: <20150213010218.GB65532@darkstar.local> <20150213120240.GF65532@darkstar.local> Message-ID: do we have a JIRA for this ? On Fri, Feb 13, 2015 at 1:17 PM, Matthias Wessendorf wrote: > yes, that's a bug in the test > > > On Friday, February 13, 2015, Douglas Campos wrote: > >> On Fri, Feb 13, 2015 at 12:01:07PM +0100, Matthias Wessendorf wrote: >> > Hi, >> > >> > I agree w/ Erik - however, I think the test has a bug, if the >> installations >> > are not directly associated with a Variant. Should be easy to fix. >> That's my point - this test should never pass - hence the "bug" >> suspicion. >> >> > >> > BTW. qmx, you mentioned the "setDeviceType()", but that is really just >> > plain text metadata, like here: >> > >> https://github.com/aerogear/aerogear-push-helloworld/blob/master/ios/HelloWorld/AGAppDelegate.m#L106 >> > >> > >> > The validator is triggered by the actual variant type (installation >> > .getVariant().getType()) >> > >> > -Matthias >> > >> > >> > >> > On Fri, Feb 13, 2015 at 8:17 AM, Erik Jan de Wit >> wrote: >> > >> > > Hi, >> > > >> > > Don?t know if it?s really a bug, but in order to validate that a >> device >> > > token is valid we need to know what variant type it belongs to. It >> makes no >> > > sense for a installation to be persisted without a Variant, because >> then >> > > you cannot send any messages to that device. So if you try to persist >> a >> > > installation without a variant the device token is not valid seems to >> be to >> > > be a valid statement. >> > > >> > > This was introduced when we added cordova, there it?s easy to make a >> > > mistake and have the wrong variantID / secret in your settings. >> Resulting >> > > in a iOS device registering under an android variant. With the >> deviceToken >> > > validation this can no longer happen. >> > > >> > > Does this make sense? >> > > >> > > Cheers, >> > > Erik Jan >> > > >> > > On 13 Feb,2015, at 2:02 , Douglas Campos wrote: >> > > >> > > > Howdy! >> > > > >> > > > I was doing the migration work and found out something funny: >> > > > >> > > > For Installations, we have `installation.setDeviceType()`, but >> during >> > > > Installation `persist()`, the DeviceTokenValidator is called, which >> in >> > > > turn looks for a Variant. >> > > > >> > > > So after fiddling with some orm settings suddenly a bunch of tests >> > > > started to break, which led me to this snippet[1]: >> > > > >> > > > // disabled >> > > > Installation android3 = new Installation(); >> > > > android3.setAlias("foo at bar.org"); >> > > > >> > > >> android3.setDeviceToken("543234234890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"); >> > > > android3.setDeviceType("Android Tablet"); >> > > > android3.setEnabled(false); >> > > > >> > > > installationDao.create(android3); >> > > > >> > > > See, our tests are creating an installation without associating it >> to a >> > > > variant first, then it blows up here[2]: >> > > > >> > > > // DeviceTokenValidator#isValid() >> > > > if (installation.getVariant() == null || >> > > installation.getVariant().getType() == null || deviceToken == null) { >> > > > return false; >> > > > } >> > > > >> > > > This is smelling like a bug to me - kinda like the validator wasn't >> > > > actually running during tests. Am I crazy? >> > > > >> > > > [1]: >> > > >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/InstallationDaoTest.java#L133-L140 >> > > > [2]: >> > > >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L60 >> > > > >> > > > -- >> > > > qmx >> > > > _______________________________________________ >> > > > aerogear-dev mailing list >> > > > aerogear-dev at lists.jboss.org >> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > >> > > >> > > _______________________________________________ >> > > aerogear-dev mailing list >> > > aerogear-dev at lists.jboss.org >> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > >> > >> > >> > >> > -- >> > Matthias Wessendorf >> > >> > blog: http://matthiaswessendorf.wordpress.com/ >> > sessions: http://www.slideshare.net/mwessendorf >> > twitter: http://twitter.com/mwessendorf >> >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> -- >> qmx >> _______________________________________________ >> 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/20150224/bfe44942/attachment.html From qmx at qmx.me Tue Feb 24 07:22:29 2015 From: qmx at qmx.me (Douglas Campos) Date: Tue, 24 Feb 2015 09:22:29 -0300 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: References: <20150213010218.GB65532@darkstar.local> <20150213120240.GF65532@darkstar.local> Message-ID: <1424780549.835625.231687389.0D383ED0@webmail.messagingengine.com> On Tue, Feb 24, 2015, at 09:09 AM, Matthias Wessendorf wrote: > do we have a JIRA for this ?? Not needed, already fixed it on the migration PR -- qmx From matzew at apache.org Tue Feb 24 07:34:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 13:34:54 +0100 Subject: [aerogear-dev] UPS bug - am I crazy? In-Reply-To: <1424780549.835625.231687389.0D383ED0@webmail.messagingengine.com> References: <20150213010218.GB65532@darkstar.local> <20150213120240.GF65532@darkstar.local> <1424780549.835625.231687389.0D383ED0@webmail.messagingengine.com> Message-ID: ah! cool On Tue, Feb 24, 2015 at 1:22 PM, Douglas Campos wrote: > On Tue, Feb 24, 2015, at 09:09 AM, Matthias Wessendorf wrote: > > do we have a JIRA for this ? > Not needed, already fixed it on the migration PR > > -- > 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/20150224/50b0872f/attachment.html From edewit at redhat.com Tue Feb 24 11:07:33 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 24 Feb 2015 17:07:33 +0100 Subject: [aerogear-dev] Cordova OAuth2 1.0.2 released Message-ID: <16D6B7D9-8CC8-473E-A23A-A6651B6F06B7@redhat.com> Hi, It?s a pleasure to annouce that the Cordova OAuth2 plugin version 1.0.2 has been released changelog: AGCORDOVA-58 - Update OAuth2 swift lib to version 0.2.0 AGCORDOVA-65 - Update OAuth2 plugin to AGDROID 2.0 AGCORDOVA-46 - Add windows support Oauth2 Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/e23817c2/attachment.html From matzew at apache.org Tue Feb 24 11:17:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 17:17:27 +0100 Subject: [aerogear-dev] Cordova OAuth2 1.0.2 released In-Reply-To: <16D6B7D9-8CC8-473E-A23A-A6651B6F06B7@redhat.com> References: <16D6B7D9-8CC8-473E-A23A-A6651B6F06B7@redhat.com> Message-ID: hey Erik, great job getting this out ! On Tue, Feb 24, 2015 at 5:07 PM, Erik Jan de Wit wrote: > Hi, > > It?s a pleasure to annouce that the Cordova OAuth2 plugin version 1.0.2 > has been released changelog: > > AGCORDOVA-58 - Update > OAuth2 swift lib to version 0.2.0 > AGCORDOVA-65 - Update > OAuth2 plugin to AGDROID 2.0 > AGCORDOVA-46 - Add windows > support Oauth2 > > 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/20150224/41c10c1a/attachment-0001.html From ivan.gurtler at ahead-itec.com Tue Feb 24 11:17:50 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 17:17:50 +0100 Subject: [aerogear-dev] Aerogear Unifiedpush with oracle DB ... longer parameters problems Message-ID: Hi, we use aerogear with oracle ... when AG used parameter with length longer than 4000 ... for example in table INSTALLATION and parameter DEVICETOKEN ... or in master branch ... table IOSVARIANT and parameter CERT_DATA .. it becomes problem because oracle has Varchar2 with max length 4000 and when parameter is longer it needs LOB ... We changed in table INSTALLATION parameter DEVICETOKEN as VARCHAR2(4000) ... it is temporary solution .. but in IOSVARIANT parameter CERT_DATA has length 100000 and it is too large. In version 1.0.x certificate was LOB and it was ok for oracle. Object with large length as CERT_DATA makes it impossible to support oracle. Is it possible to keep database schema the way it would support oracle??? Or do you have any idea how to support oracle with current schema? Thanks for help ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/5b6b4160/attachment.html From matzew at apache.org Tue Feb 24 11:29:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 17:29:27 +0100 Subject: [aerogear-dev] Aerogear Unifiedpush with oracle DB ... longer parameters problems In-Reply-To: References: Message-ID: On Tue, Feb 24, 2015 at 5:17 PM, Ivan G?rtler wrote: > Hi, > > we use aerogear with oracle ... when AG used parameter with length longer > than 4000 ... for example in table INSTALLATION and parameter DEVICETOKEN > ... or in master branch ... table IOSVARIANT and parameter CERT_DATA .. it > becomes problem because oracle has Varchar2 with max length 4000 and when > parameter is longer it needs LOB ... > > We changed in table INSTALLATION parameter DEVICETOKEN as VARCHAR2(4000) > ... it is temporary solution .. but in IOSVARIANT parameter CERT_DATA has > length 100000 and it is too large. In version 1.0.x certificate was LOB and > it was ok for oracle. > > Object with large length as CERT_DATA makes it impossible to support > oracle. Is it possible to keep database schema the way it would support > oracle??? Or do you have any idea how to support oracle with current schema? > Ok, on last release (1.0.2) is was a byte array: * https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L40 * https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/jpa/src/main/resources/META-INF/orm.xml#L66-L68 but yeah, in this branch it's a string: * https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L43 * https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/jpa/src/main/resources/META-INF/orm.xml#L76-L78 I think there was a Postgres bug that lead us to that implementation: https://issues.jboss.org/browse/AGPUSH-1144 But now, since causes some fun on the ORCL side of things ;-( Greetings > > Thanks for help ... > > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/67ec6e47/attachment.html From matzew at apache.org Tue Feb 24 11:33:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 17:33:41 +0100 Subject: [aerogear-dev] Aerogear Unifiedpush with oracle DB ... longer parameters problems In-Reply-To: References: Message-ID: Ivan, btw. can you create a JIRA ticket for this as well ? Thanks for all the valuable feedback from you guys On Tue, Feb 24, 2015 at 5:29 PM, Matthias Wessendorf wrote: > > > On Tue, Feb 24, 2015 at 5:17 PM, Ivan G?rtler > wrote: > >> Hi, >> >> we use aerogear with oracle ... when AG used parameter with length longer >> than 4000 ... for example in table INSTALLATION and parameter DEVICETOKEN >> ... or in master branch ... table IOSVARIANT and parameter CERT_DATA .. it >> becomes problem because oracle has Varchar2 with max length 4000 and when >> parameter is longer it needs LOB ... >> >> We changed in table INSTALLATION parameter DEVICETOKEN as VARCHAR2(4000) >> ... it is temporary solution .. but in IOSVARIANT parameter CERT_DATA has >> length 100000 and it is too large. In version 1.0.x certificate was LOB and >> it was ok for oracle. >> >> Object with large length as CERT_DATA makes it impossible to support >> oracle. Is it possible to keep database schema the way it would support >> oracle??? Or do you have any idea how to support oracle with current schema? >> > > Ok, on last release (1.0.2) is was a byte array: > * > https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L40 > * > https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/jpa/src/main/resources/META-INF/orm.xml#L66-L68 > > but yeah, in this branch it's a string: > * > https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L43 > * > https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/jpa/src/main/resources/META-INF/orm.xml#L76-L78 > > I think there was a Postgres bug that lead us to that implementation: > https://issues.jboss.org/browse/AGPUSH-1144 > > But now, since causes some fun on the ORCL side of things ;-( > > Greetings > > >> >> Thanks for help ... >> >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150224/486b509c/attachment.html From ivan.gurtler at ahead-itec.com Tue Feb 24 11:46:39 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 24 Feb 2015 17:46:39 +0100 Subject: [aerogear-dev] Aerogear Unifiedpush with oracle DB ... longer parameters problems In-Reply-To: References: Message-ID: yes, here it is ... https://issues.jboss.org/browse/AGPUSH-1297 .. is ok ? *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-24 17:33 GMT+01:00 Matthias Wessendorf : > Ivan, btw. can you create a JIRA ticket for this as well ? > > Thanks for all the valuable feedback from you guys > > On Tue, Feb 24, 2015 at 5:29 PM, Matthias Wessendorf > wrote: > >> >> >> On Tue, Feb 24, 2015 at 5:17 PM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> Hi, >>> >>> we use aerogear with oracle ... when AG used parameter with length >>> longer than 4000 ... for example in table INSTALLATION and parameter >>> DEVICETOKEN ... or in master branch ... table IOSVARIANT and parameter >>> CERT_DATA .. it becomes problem because oracle has Varchar2 with max length >>> 4000 and when parameter is longer it needs LOB ... >>> >>> We changed in table INSTALLATION parameter DEVICETOKEN as VARCHAR2(4000) >>> ... it is temporary solution .. but in IOSVARIANT parameter CERT_DATA has >>> length 100000 and it is too large. In version 1.0.x certificate was LOB and >>> it was ok for oracle. >>> >>> Object with large length as CERT_DATA makes it impossible to support >>> oracle. Is it possible to keep database schema the way it would support >>> oracle??? Or do you have any idea how to support oracle with current schema? >>> >> >> Ok, on last release (1.0.2) is was a byte array: >> * >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L40 >> * >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/jpa/src/main/resources/META-INF/orm.xml#L66-L68 >> >> but yeah, in this branch it's a string: >> * >> https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L43 >> * >> https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/jpa/src/main/resources/META-INF/orm.xml#L76-L78 >> >> I think there was a Postgres bug that lead us to that implementation: >> https://issues.jboss.org/browse/AGPUSH-1144 >> >> But now, since causes some fun on the ORCL side of things ;-( >> >> Greetings >> >> >>> >>> Thanks for help ... >>> >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20150224/2dd1e15f/attachment-0001.html From matzew at apache.org Tue Feb 24 11:53:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 17:53:07 +0100 Subject: [aerogear-dev] Aerogear Unifiedpush with oracle DB ... longer parameters problems In-Reply-To: References: Message-ID: perfect, thanks! On Tue, Feb 24, 2015 at 5:46 PM, Ivan G?rtler wrote: > yes, here it is ... https://issues.jboss.org/browse/AGPUSH-1297 .. is ok ? > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-02-24 17:33 GMT+01:00 Matthias Wessendorf : > >> Ivan, btw. can you create a JIRA ticket for this as well ? >> >> Thanks for all the valuable feedback from you guys >> >> On Tue, Feb 24, 2015 at 5:29 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Tue, Feb 24, 2015 at 5:17 PM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> Hi, >>>> >>>> we use aerogear with oracle ... when AG used parameter with length >>>> longer than 4000 ... for example in table INSTALLATION and parameter >>>> DEVICETOKEN ... or in master branch ... table IOSVARIANT and parameter >>>> CERT_DATA .. it becomes problem because oracle has Varchar2 with max length >>>> 4000 and when parameter is longer it needs LOB ... >>>> >>>> We changed in table INSTALLATION parameter DEVICETOKEN as >>>> VARCHAR2(4000) ... it is temporary solution .. but in IOSVARIANT parameter >>>> CERT_DATA has length 100000 and it is too large. In version 1.0.x >>>> certificate was LOB and it was ok for oracle. >>>> >>>> Object with large length as CERT_DATA makes it impossible to support >>>> oracle. Is it possible to keep database schema the way it would support >>>> oracle??? Or do you have any idea how to support oracle with current schema? >>>> >>> >>> Ok, on last release (1.0.2) is was a byte array: >>> * >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L40 >>> * >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.2/model/jpa/src/main/resources/META-INF/orm.xml#L66-L68 >>> >>> but yeah, in this branch it's a string: >>> * >>> https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/iOSVariant.java#L43 >>> * >>> https://github.com/qmx/aerogear-unified-push-server/blob/certificate_data_changes/model/jpa/src/main/resources/META-INF/orm.xml#L76-L78 >>> >>> I think there was a Postgres bug that lead us to that implementation: >>> https://issues.jboss.org/browse/AGPUSH-1144 >>> >>> But now, since causes some fun on the ORCL side of things ;-( >>> >>> Greetings >>> >>> >>>> >>>> Thanks for help ... >>>> >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20150224/6bc2a160/attachment.html From lholmqui at redhat.com Tue Feb 24 12:26:44 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 24 Feb 2015 12:26:44 -0500 Subject: [aerogear-dev] AeroGear.js Message-ID: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> While i was getting things together for the 2.1.0 release, I started to think about the structure of AeroGear.js. Lets take DataManager as an example. var dataManager = new AeroGear.DataManager(); Basically, the resulting datamanger object is a fancy array. We can add new stores to it: dataManager.add('memoryStoreThing'); dataManager.add({{ name: "indexDBStore", type: "IndexedDB" }}); I'm not sure what the reason for this was historically. I think this concept was initally created when we were doing Pipeline. But sticking to this example, i'm wondering if it adds any value though. would someone create a Datamanager that has more than one store in it? It's possible i guess if someone wanted to store the same info in a IndexedDB and WebSQL database at the same, for example, but there is currently no way to sync data between the two With the next release, 2.1.0, we will be deprecating Notifier, which uses this pattern. So Datamanager and Sync would be the only things using this pattern. Which i'm not sure makes sense anymore. The remaining parts of the Library, Crypto, UnifiedPush, and to some extent SimplePush(currenlty coupled with Notifier) don't do this. I am leaning toward proposing we get rid of this pattern and just make a DataManager object hold 1 store/adapter( sync woud follow suit ) This change though would be a 3.0 thing since it would be changing the way the API works. I'm also wondering if it would make sense to separate the differnt parts of the library into different repo's. I think one of the main reasons this wasn't done in the past was because AeroGear.Core was shared across many pieces of the library and it would be a lot of code duplication. But something like the UnifiedPush Client SDK, might make sense in a separate repo. For distribution, i've actually created a AeroGear Component GH organization, that has pieces of the library, https://github.com/orgs/AeroGear-Components/dashboard I think i've started to ramble, so i'll stop here and look for comments -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/17568093/attachment.html From bruno at abstractj.org Tue Feb 24 13:11:22 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 24 Feb 2015 15:11:22 -0300 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> Message-ID: <20150224181122.GA4922@abstractj.org> On 2015-02-24, Lucas Holmquist wrote: > While i was getting things together for the 2.1.0 release, I started to think about the structure of AeroGear.js. > > Lets take DataManager as an example. > > var dataManager = new AeroGear.DataManager(); > Basically, the resulting datamanger object is a fancy array. We can add new stores to it: > > dataManager.add('memoryStoreThing'); > > dataManager.add({{ > name: "indexDBStore", > type: "IndexedDB" > }}); > I'm not sure what the reason for this was historically. I think this concept was initally created when we were doing Pipeline. > > But sticking to this example, i'm wondering if it adds any value though. would someone create a Datamanager that has more than one store in it? It's possible i guess if someone wanted to store the same info in a IndexedDB and WebSQL database at the same, for example, but there is currently no way to sync data between the two > > With the next release, 2.1.0, we will be deprecating Notifier, which uses this pattern. Agreed with you, it doesn't make sense to me either. > > So Datamanager and Sync would be the only things using this pattern. Which i'm not sure makes sense anymore. > > The remaining parts of the Library, Crypto, UnifiedPush, and to some extent SimplePush(currenlty coupled with Notifier) don't do this. > > I am leaning toward proposing we get rid of this pattern and just make a DataManager object hold 1 store/adapter( sync woud follow suit ) +1 go ahead > > This change though would be a 3.0 thing since it would be changing the way the API works. > > I'm also wondering if it would make sense to separate the differnt parts of the library into different repo's. Do you mean separate all the libraries? How our libraries would make use of AeroGear.Core? Bower? > > I think one of the main reasons this wasn't done in the past was because AeroGear.Core was shared across many pieces of the library and it would be a lot of code duplication. > > But something like the UnifiedPush Client SDK, might make sense in a separate repo. I couldn't see the real need of a separated repo, but probably I'm missing the context. > > For distribution, i've actually created a AeroGear Component GH organization, that has pieces of the library, https://github.com/orgs/AeroGear-Components/dashboard > I think i've started to ramble, so i'll stop here and look for comments > _______________________________________________ > 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 Feb 24 13:26:32 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 24 Feb 2015 13:26:32 -0500 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <20150224181122.GA4922@abstractj.org> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> <20150224181122.GA4922@abstractj.org> Message-ID: <242EE819-D489-4CA0-A62F-FEE40F9656F4@redhat.com> > On Feb 24, 2015, at 1:11 PM, Bruno Oliveira wrote: > > On 2015-02-24, Lucas Holmquist wrote: >> While i was getting things together for the 2.1.0 release, I started to think about the structure of AeroGear.js. >> >> Lets take DataManager as an example. >> >> var dataManager = new AeroGear.DataManager(); >> Basically, the resulting datamanger object is a fancy array. We can add new stores to it: >> >> dataManager.add('memoryStoreThing'); >> >> dataManager.add({{ >> name: "indexDBStore", >> type: "IndexedDB" >> }}); >> I'm not sure what the reason for this was historically. I think this concept was initally created when we were doing Pipeline. >> >> But sticking to this example, i'm wondering if it adds any value though. would someone create a Datamanager that has more than one store in it? It's possible i guess if someone wanted to store the same info in a IndexedDB and WebSQL database at the same, for example, but there is currently no way to sync data between the two >> >> With the next release, 2.1.0, we will be deprecating Notifier, which uses this pattern. > > Agreed with you, it doesn't make sense to me either. > >> >> So Datamanager and Sync would be the only things using this pattern. Which i'm not sure makes sense anymore. >> >> The remaining parts of the Library, Crypto, UnifiedPush, and to some extent SimplePush(currenlty coupled with Notifier) don't do this. >> >> I am leaning toward proposing we get rid of this pattern and just make a DataManager object hold 1 store/adapter( sync woud follow suit ) > > +1 go ahead > >> >> This change though would be a 3.0 thing since it would be changing the way the API works. >> >> I'm also wondering if it would make sense to separate the differnt parts of the library into different repo's. > > Do you mean separate all the libraries? How our libraries would make use > of AeroGear.Core? Bower? I think AeroGear.Core would essentially go away since it is only providing, the ?add? and ?remove? methods for the ?Fancy Arrays?, if we stop doing that pattern, then i don?t think this would be needed. Thinking a little bit more, we don?t need separte repo?s for each feature. Thats what we can use AeroGear-Components thingy to distribute via bower. We can script that shizzell, to create custom feature builds > >> >> I think one of the main reasons this wasn't done in the past was because AeroGear.Core was shared across many pieces of the library and it would be a lot of code duplication. >> >> But something like the UnifiedPush Client SDK, might make sense in a separate repo. > > I couldn't see the real need of a separated repo, but probably I'm > missing the context. >> >> For distribution, i've actually created a AeroGear Component GH organization, that has pieces of the library, https://github.com/orgs/AeroGear-Components/dashboard > >> I think i've started to ramble, so i'll stop here and look for comments > >> _______________________________________________ >> 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/20150224/f4cb5eb9/attachment.html From matzew at apache.org Tue Feb 24 13:28:23 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 24 Feb 2015 19:28:23 +0100 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> Message-ID: On Tuesday, February 24, 2015, Lucas Holmquist wrote: > While i was getting things together for the 2.1.0 release, I started to > think about the structure of AeroGear.js. > > Lets take DataManager as an example. > > var dataManager = new AeroGear.DataManager(); > > Basically, the resulting datamanger object is a fancy array. We can add > new stores to it: > > dataManager.add('memoryStoreThing'); > > dataManager.add({{ > name: "indexDBStore", > type: "IndexedDB" > }}); > > I'm not sure what the reason for this was historically. I think this > concept was initally created when we were doing Pipeline. > > But sticking to this example, i'm wondering if it adds any value though. > would someone create a Datamanager that has more than one store in it? It's > possible i guess if someone wanted to store the same info in a IndexedDB > and WebSQL database at the same, for example, but there is currently no way > to sync data between the two > > With the next release, 2.1.0, we will be deprecating Notifier, which uses > this pattern. > > So Datamanager and Sync would be the only things using this pattern. Which > i'm not sure makes sense anymore. > > I agree > > The remaining parts of the Library, Crypto, UnifiedPush, and to some extent > SimplePush(currenlty coupled with Notifier) don't do this. > > I am leaning toward proposing we get rid of this pattern and just make a > DataManager object hold 1 store/adapter( sync woud follow suit ) > > This change though would be a 3.0 thing since it would be changing the way > the API works. > yeah, lets do that for 3.0 > I'm also wondering if it would make sense to separate the differnt parts > of the library into different repo's. > worth to evaluate this > I think one of the main reasons this wasn't done in the past was because > AeroGear.Core was shared across many pieces of the library and it would > be a lot of code duplication. > but we could get it via dependency, right? > But something like the UnifiedPush Client SDK, might make sense in a > separate repo. > I like this approach > For distribution, i've actually created a AeroGear Component GH > organization, that has pieces of the library, > https://github.com/orgs/AeroGear-Components/dashboard > > I think i've started to ramble, so i'll stop here and look for comments > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/cfd0ed13/attachment-0001.html From scm.blanc at gmail.com Tue Feb 24 13:31:37 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 24 Feb 2015 19:31:37 +0100 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> Message-ID: On Tue, Feb 24, 2015 at 6:26 PM, Lucas Holmquist wrote: > While i was getting things together for the 2.1.0 release, I started to > think about the structure of AeroGear.js. > > Lets take DataManager as an example. > > var dataManager = new AeroGear.DataManager(); > > Basically, the resulting datamanger object is a fancy array. We can add > new stores to it: > > dataManager.add('memoryStoreThing'); > > dataManager.add({{ > name: "indexDBStore", > type: "IndexedDB" > }}); > > I'm not sure what the reason for this was historically. I think this > concept was initally created when we were doing Pipeline. > > But sticking to this example, i'm wondering if it adds any value though. > would someone create a Datamanager that has more than one store in it? It's > possible i guess if someone wanted to store the same info in a IndexedDB > and WebSQL database at the same, for example, but there is currently no way > to sync data between the two > > With the next release, 2.1.0, we will be deprecating Notifier, which uses > this pattern. > > So Datamanager and Sync would be the only things using this pattern. Which > i'm not sure makes sense anymore. > > The remaining parts of the Library, Crypto, UnifiedPush, and to some > extent SimplePush(currenlty coupled with Notifier) don't do this. > > I am leaning toward proposing we get rid of this pattern and just make a > DataManager object hold 1 store/adapter( sync woud follow suit ) > > This change though would be a 3.0 thing since it would be changing the way > the API works. > > I'm also wondering if it would make sense to separate the differnt parts > of the library into different repo's. > That would make Bower distribution easier right ? > I think one of the main reasons this wasn't done in the past was because > AeroGear.Core was shared across many pieces of the library and it would > be a lot of code duplication. > > But something like the UnifiedPush Client SDK, might make sense in a > separate repo. > > For distribution, i've actually created a AeroGear Component GH > organization, that has pieces of the library, > https://github.com/orgs/AeroGear-Components/dashboard > > I think i've started to ramble, so i'll stop here and look for comments > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/e5f47522/attachment.html From lholmqui at redhat.com Tue Feb 24 13:34:17 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 24 Feb 2015 13:34:17 -0500 Subject: [aerogear-dev] AeroGear.js In-Reply-To: References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> Message-ID: <374BB173-6E14-40A0-B0E5-AAB3BFF37988@redhat.com> not sure if it came through, yet, but my after thinking about the separate repo thing, ?Thinking a little bit more, we don?t need separte repo?s for each feature. Thats what we can use AeroGear-Components thingy to distribute via bower. We can script that shizzell, to create custom feature builds? > On Feb 24, 2015, at 1:31 PM, Sebastien Blanc wrote: > > > > On Tue, Feb 24, 2015 at 6:26 PM, Lucas Holmquist > wrote: > While i was getting things together for the 2.1.0 release, I started to think about the structure of AeroGear.js. > > Lets take DataManager as an example. > > var dataManager = new AeroGear.DataManager(); > Basically, the resulting datamanger object is a fancy array. We can add new stores to it: > > dataManager.add('memoryStoreThing'); > > dataManager.add({{ > name: "indexDBStore", > type: "IndexedDB" > }}); > I'm not sure what the reason for this was historically. I think this concept was initally created when we were doing Pipeline. > > But sticking to this example, i'm wondering if it adds any value though. would someone create a Datamanager that has more than one store in it? It's possible i guess if someone wanted to store the same info in a IndexedDB and WebSQL database at the same, for example, but there is currently no way to sync data between the two > > With the next release, 2.1.0, we will be deprecating Notifier, which uses this pattern. > > So Datamanager and Sync would be the only things using this pattern. Which i'm not sure makes sense anymore. > > The remaining parts of the Library, Crypto, UnifiedPush, and to some extent SimplePush(currenlty coupled with Notifier) don't do this. > > I am leaning toward proposing we get rid of this pattern and just make a DataManager object hold 1 store/adapter( sync woud follow suit ) > > This change though would be a 3.0 thing since it would be changing the way the API works. > > I'm also wondering if it would make sense to separate the differnt parts of the library into different repo's. > > That would make Bower distribution easier right ? > I think one of the main reasons this wasn't done in the past was because AeroGear.Core was shared across many pieces of the library and it would be a lot of code duplication. > > But something like the UnifiedPush Client SDK, might make sense in a separate repo. > > For distribution, i've actually created a AeroGear Component GH organization, that has pieces of the library, https://github.com/orgs/AeroGear-Components/dashboard > I think i've started to ramble, so i'll stop here and look for comments > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150224/18d83dcf/attachment-0001.html From scm.blanc at gmail.com Tue Feb 24 13:41:13 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 24 Feb 2015 19:41:13 +0100 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <374BB173-6E14-40A0-B0E5-AAB3BFF37988@redhat.com> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> <374BB173-6E14-40A0-B0E5-AAB3BFF37988@redhat.com> Message-ID: Jaja , sorry ! I should read answers before answering :) On Tue, Feb 24, 2015 at 7:34 PM, Lucas Holmquist wrote: > not sure if it came through, yet, but my after thinking about the > separate repo thing, > > ?Thinking a little bit more, we don?t need separte repo?s for each > feature. Thats what we can use AeroGear-Components thingy to distribute > via bower. We can script that shizzell, to create custom feature builds? > > > On Feb 24, 2015, at 1:31 PM, Sebastien Blanc wrote: > > > > On Tue, Feb 24, 2015 at 6:26 PM, Lucas Holmquist > wrote: > >> While i was getting things together for the 2.1.0 release, I started to >> think about the structure of AeroGear.js. >> >> Lets take DataManager as an example. >> >> var dataManager = new AeroGear.DataManager(); >> >> Basically, the resulting datamanger object is a fancy array. We can add >> new stores to it: >> >> dataManager.add('memoryStoreThing'); >> >> dataManager.add({{ >> name: "indexDBStore", >> type: "IndexedDB" >> }}); >> >> I'm not sure what the reason for this was historically. I think this >> concept was initally created when we were doing Pipeline. >> >> But sticking to this example, i'm wondering if it adds any value though. >> would someone create a Datamanager that has more than one store in it? It's >> possible i guess if someone wanted to store the same info in a IndexedDB >> and WebSQL database at the same, for example, but there is currently no way >> to sync data between the two >> >> With the next release, 2.1.0, we will be deprecating Notifier, which uses >> this pattern. >> >> So Datamanager and Sync would be the only things using this pattern. >> Which i'm not sure makes sense anymore. >> >> The remaining parts of the Library, Crypto, UnifiedPush, and to some >> extent SimplePush(currenlty coupled with Notifier) don't do this. >> >> I am leaning toward proposing we get rid of this pattern and just make a >> DataManager object hold 1 store/adapter( sync woud follow suit ) >> >> This change though would be a 3.0 thing since it would be changing the >> way the API works. >> >> I'm also wondering if it would make sense to separate the differnt parts >> of the library into different repo's. >> > That would make Bower distribution easier right ? > >> I think one of the main reasons this wasn't done in the past was because >> AeroGear.Core was shared across many pieces of the library and it would >> be a lot of code duplication. >> >> But something like the UnifiedPush Client SDK, might make sense in a >> separate repo. >> >> For distribution, i've actually created a AeroGear Component GH >> organization, that has pieces of the library, >> https://github.com/orgs/AeroGear-Components/dashboard >> >> I think i've started to ramble, so i'll stop here and look for comments >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150224/e4d87a84/attachment.html From bleathem at gmail.com Tue Feb 24 13:46:34 2015 From: bleathem at gmail.com (Brian Leathem) Date: Tue, 24 Feb 2015 10:46:34 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services Message-ID: <54ECC70A.8040100@gmail.com> Hey gear-heads, I recently wrote a Cordova plugin that retrieves a Oauth2 token on Android using Google Play Services. The advantage of this approach is it leverages the single-sign-on capabilities of android, and the app can retrieve the Oauth2 token without requiring Authentication from the user. I blogged about it here: http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html Using a promise-based API it's fairly trivial to fallback to a traditional Web authentication/authorisation for the Oauth2 token when the google-play-services approach isn't supported. I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's not clear to me if the google-play-services integration is supported. If the Aerogeam would find it useful, I'd be more than happy to provide a PR to the aerogear cordova plugin providing such integration. Thoughts? Brian [1] http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html From scm.blanc at gmail.com Tue Feb 24 14:01:54 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 24 Feb 2015 20:01:54 +0100 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54ECC70A.8040100@gmail.com> References: <54ECC70A.8040100@gmail.com> Message-ID: Cool stuff Brian ! The AeroGear OAuth2 Cordova plugin relies on the Native AeroGear OAuth2 Libraries, so maybe Summers and/or Daniel could tell more about it. Sebi On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem wrote: > Hey gear-heads, > > I recently wrote a Cordova plugin that retrieves a Oauth2 token on > Android using Google Play Services. The advantage of this approach is > it leverages the single-sign-on capabilities of android, and the app can > retrieve the Oauth2 token without requiring Authentication from the > user. I blogged about it here: > > http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html > > Using a promise-based API it's fairly trivial to fallback to a > traditional Web authentication/authorisation for the Oauth2 token when > the google-play-services approach isn't supported. > > I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's > not clear to me if the google-play-services integration is supported. > If the Aerogeam would find it useful, I'd be more than happy to provide > a PR to the aerogear cordova plugin providing such integration. > > Thoughts? > Brian > > [1] > > http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/c4279dd1/attachment.html From daniel at passos.me Tue Feb 24 18:46:29 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 24 Feb 2015 20:46:29 -0300 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> Message-ID: No, we are not using Google Play services API for now for OAuth2 in Android land. But feel free create a new AuthzModule[1] for it ;) [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java -- Passos On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc wrote: > Cool stuff Brian ! > The AeroGear OAuth2 Cordova plugin relies on the Native AeroGear OAuth2 > Libraries, so maybe Summers and/or Daniel could tell more about it. > Sebi > > > On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem wrote: > >> Hey gear-heads, >> >> I recently wrote a Cordova plugin that retrieves a Oauth2 token on >> Android using Google Play Services. The advantage of this approach is >> it leverages the single-sign-on capabilities of android, and the app can >> retrieve the Oauth2 token without requiring Authentication from the >> user. I blogged about it here: >> >> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >> >> Using a promise-based API it's fairly trivial to fallback to a >> traditional Web authentication/authorisation for the Oauth2 token when >> the google-play-services approach isn't supported. >> >> I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's >> not clear to me if the google-play-services integration is supported. >> If the Aerogeam would find it useful, I'd be more than happy to provide >> a PR to the aerogear cordova plugin providing such integration. >> >> Thoughts? >> Brian >> >> [1] >> >> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150224/cd1abe85/attachment-0001.html From matzew at apache.org Tue Feb 24 22:25:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 25 Feb 2015 04:25:41 +0100 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> Message-ID: On Wednesday, February 25, 2015, Daniel Passos wrote: > No, we are not using Google Play services API for now for OAuth2 in > Android land. > > But feel free create a new AuthzModule[1] for it ;) > +1 > > [1] > https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java > > -- Passos > > > On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc > wrote: > >> Cool stuff Brian ! >> The AeroGear OAuth2 Cordova plugin relies on the Native AeroGear OAuth2 >> Libraries, so maybe Summers and/or Daniel could tell more about it. >> Sebi >> >> >> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem > > wrote: >> >>> Hey gear-heads, >>> >>> I recently wrote a Cordova plugin that retrieves a Oauth2 token on >>> Android using Google Play Services. The advantage of this approach is >>> it leverages the single-sign-on capabilities of android, and the app can >>> retrieve the Oauth2 token without requiring Authentication from the >>> user. I blogged about it here: >>> >>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>> >>> Using a promise-based API it's fairly trivial to fallback to a >>> traditional Web authentication/authorisation for the Oauth2 token when >>> the google-play-services approach isn't supported. >>> >>> I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's >>> not clear to me if the google-play-services integration is supported. >>> If the Aerogeam would find it useful, I'd be more than happy to provide >>> a PR to the aerogear cordova plugin providing such integration. >>> >>> Thoughts? >>> Brian >>> >>> [1] >>> >>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/53b64a31/attachment.html From edewit at redhat.com Wed Feb 25 02:01:31 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 25 Feb 2015 08:01:31 +0100 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54ECC70A.8040100@gmail.com> References: <54ECC70A.8040100@gmail.com> Message-ID: <81FA1D7E-C30F-48CA-BB9E-EB49EECDC0CA@redhat.com> Hi Brian, Cool stuff, seems like your javascript api is very similar to what we have on the cordova plugin. Would be great if you could add it. Cheers, Erik Jan > On 24 Feb,2015, at 19:46 , Brian Leathem wrote: > > Hey gear-heads, > > I recently wrote a Cordova plugin that retrieves a Oauth2 token on > Android using Google Play Services. The advantage of this approach is > it leverages the single-sign-on capabilities of android, and the app can > retrieve the Oauth2 token without requiring Authentication from the > user. I blogged about it here: > > http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html > > Using a promise-based API it's fairly trivial to fallback to a > traditional Web authentication/authorisation for the Oauth2 token when > the google-play-services approach isn't supported. > > I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's > not clear to me if the google-play-services integration is supported. > If the Aerogeam would find it useful, I'd be more than happy to provide > a PR to the aerogear cordova plugin providing such integration. > > Thoughts? > Brian > > [1] > http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html > _______________________________________________ > 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 Feb 25 02:58:57 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 25 Feb 2015 08:58:57 +0100 Subject: [aerogear-dev] Release: New parent staged (was: Re: parent release ?) In-Reply-To: References: Message-ID: I tested the new parent with UPS Master, could push and receive a iOS notifications +1 On Tue, Feb 24, 2015 at 11:11 AM, Matthias Wessendorf wrote: > Hi, > > as discussed below, we need a new parent release to get the latest of APNs > into master. > > I have executed the release procedure and staged the pom files at: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4932/ > > please give it a shot, otherwise I will release it late Thursday, so that > we can update it shortly afterwards. > > Cheers, > Matthias > > On Wed, Feb 18, 2015 at 1:55 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> becasuse of https://github.com/aerogear/aerogear-parent/pull/41 got >> merged, I'd like to run another parent release - yay! >> >> However, just wondering, do any other folks have wishes to update some >> 3rd party dependencies in there ? >> >> Thanks! >> >> >> -- >> 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/20150225/13bd3a0e/attachment.html From matzew at apache.org Wed Feb 25 03:22:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 25 Feb 2015 09:22:02 +0100 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <81FA1D7E-C30F-48CA-BB9E-EB49EECDC0CA@redhat.com> References: <54ECC70A.8040100@gmail.com> <81FA1D7E-C30F-48CA-BB9E-EB49EECDC0CA@redhat.com> Message-ID: +1 on joing forces :-) (see also passos' hint) hehe On Wed, Feb 25, 2015 at 8:01 AM, Erik Jan de Wit wrote: > Hi Brian, > > Cool stuff, seems like your javascript api is very similar to what we have > on the cordova plugin. Would be great if you could add it. > > Cheers, > Erik Jan > > > On 24 Feb,2015, at 19:46 , Brian Leathem wrote: > > > > Hey gear-heads, > > > > I recently wrote a Cordova plugin that retrieves a Oauth2 token on > > Android using Google Play Services. The advantage of this approach is > > it leverages the single-sign-on capabilities of android, and the app can > > retrieve the Oauth2 token without requiring Authentication from the > > user. I blogged about it here: > > > > http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html > > > > Using a promise-based API it's fairly trivial to fallback to a > > traditional Web authentication/authorisation for the Oauth2 token when > > the google-play-services approach isn't supported. > > > > I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's > > not clear to me if the google-play-services integration is supported. > > If the Aerogeam would find it useful, I'd be more than happy to provide > > a PR to the aerogear cordova plugin providing such integration. > > > > Thoughts? > > Brian > > > > [1] > > > http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/c8e8025f/attachment.html From scm.blanc at gmail.com Wed Feb 25 03:39:06 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 25 Feb 2015 09:39:06 +0100 Subject: [aerogear-dev] deployment problem - master branch In-Reply-To: References: Message-ID: Ivan, Thanks again for the feedback, the PR has been merged now. Sebi On Tue, Feb 24, 2015 at 11:17 AM, Matthias Wessendorf wrote: > perfecto :) > > On Tue, Feb 24, 2015 at 11:13 AM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> is it ok ? ... https://issues.jboss.org/browse/AGPUSH-1294 >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-24 10:50 GMT+01:00 Matthias Wessendorf : >> >>> yep, in here please :-) >>> https://issues.jboss.org/browse/AGPUSH >>> >>> On Tue, Feb 24, 2015 at 10:46 AM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> You mean in JIRA for AG ??? >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> 2015-02-24 10:34 GMT+01:00 Matthias Wessendorf : >>>> >>>>> Ivan, >>>>> >>>>> can you file a JIRA ticket for this? >>>>> >>>>> On Tue, Feb 24, 2015 at 10:34 AM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> yeah, I now see it: >>>>>> >>>>>> KeycloakAuthenticatorValve >>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>> >>>>>> >>>>>> looks like an issue w/ the KC adapter for AS7, that comes with the >>>>>> 1.1.x series of Keycloak - I will take a look in a bit >>>>>> >>>>>> On Tue, Feb 24, 2015 at 10:32 AM, Ivan G?rtler < >>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>> >>>>>>> yes ... I use AS7 version .. >>>>>>> >>>>>>> *Mgr. Ivan G?rtler* >>>>>>> Mobile software developer >>>>>>> >>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>> 602 00 Brno (Czech Republic) >>>>>>> >>>>>>> www.ahead-itec.com | twitter | >>>>>>> mobile security solutions >>>>>>> >>>>>>> 2015-02-24 10:29 GMT+01:00 Matthias Wessendorf : >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Feb 24, 2015 at 10:24 AM, Ivan G?rtler < >>>>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I try to deploy 2 .war files ... build from master branch. I use >>>>>>>>> JBoss EAP 6.3 in domain mode. Profile: default. >>>>>>>>> >>>>>>>>> I have problem with depolying ag-push.war... >>>>>>>>> >>>>>>>> >>>>>>>> you used the one from the as7 server folder ? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> 10:16:11,208 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>>>> JBAS011401: Read persistence.xml for persistenceUnit >>>>>>>>> 10:16:11,446 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-2) JBAS015960: Class Path entry lib/snakeyaml-1.13.jar in >>>>>>>>> /content/auth-server.war/WEB-INF/lib/liquibase-core-3.2.2.jar does not >>>>>>>>> point to a valid jar for a Class-Path reference. >>>>>>>>> 10:16:11,911 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>>>>>>> JBAS011401: Read persistence.xml for keycloak-default >>>>>>>>> 10:16:12,801 WARN [org.jboss.weld.deployer] (MSC service thread >>>>>>>>> 1-2) JBAS016012: Deployment deployment "AheadCMS-Backend.war" contains CDI >>>>>>>>> annotations but beans.xml was not found. >>>>>>>>> 10:16:12,959 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>>>> id=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>>>> address=http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>>>> implementor=com.aheaditec.cms.backend.webservice.WebApiImpl >>>>>>>>> serviceName={ >>>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>>>> portName={ >>>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplPort >>>>>>>>> annotationWsdlLocation=null >>>>>>>>> wsdlLocationOverride=null >>>>>>>>> mtomEnabled=false >>>>>>>>> 10:16:12,968 INFO [org.jboss.ws.cxf.metadata] (MSC service thread >>>>>>>>> 1-2) JBWS024061: Adding service endpoint metadata: >>>>>>>>> id=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>>>> address=http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>>>> implementor=com.aheaditec.cms.backend.webservice.MobileApiImpl >>>>>>>>> serviceName={ >>>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>>>> portName={ >>>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplPort >>>>>>>>> annotationWsdlLocation=null >>>>>>>>> wsdlLocationOverride=null >>>>>>>>> mtomEnabled=false >>>>>>>>> 10:16:13,182 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>>> 50) JBAS018210: Register web context: /AheadCMS-Frontend >>>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>>> removed in future versions without notice. >>>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>>> removed in future versions without notice. >>>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>>> changed or removed in future versions without notice. >>>>>>>>> 10:16:13,372 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>>> changed or removed in future versions without notice. >>>>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>>> be changed or removed in future versions without notice. >>>>>>>>> 10:16:13,373 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-1) JBAS018567: Deployment "deployment.auth-server.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>>> be changed or removed in future versions without notice. >>>>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>>>> removed in future versions without notice. >>>>>>>>> 10:16:13,381 WARN [org.jboss.as.dependency.unsupported] (MSC >>>>>>>>> service thread 1-1) JBAS018568: Deployment "deployment.auth-server.war" is >>>>>>>>> using an unsupported module ("org.infinispan:main") which may be changed or >>>>>>>>> removed in future versions without notice. >>>>>>>>> 10:16:13,391 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>>> 51) JBAS018210: Register web context: /EnvTest-1.0 >>>>>>>>> 10:16:13,613 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>>> 51) JBAS018210: Register web context: /auth >>>>>>>>> 10:16:14,145 INFO >>>>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>>>> thread 1-2) Creating Service { >>>>>>>>> http://webservice.backend.cms.aheaditec.com/}WebApiImplService >>>>>>>>> from class com.aheaditec.cms.backend.webservice.WebApi >>>>>>>>> 10:16:14,401 INFO [org.hibernate.validator.internal.util.Version] >>>>>>>>> (ServerService Thread Pool -- 51) HV000001: Hibernate Validator >>>>>>>>> 4.3.1.Final-redhat-1 >>>>>>>>> 10:16:14,958 INFO >>>>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>>>> Thread Pool -- 51) Load config from >>>>>>>>> vfs:/content/auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json >>>>>>>>> 10:16:16,081 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC >>>>>>>>> service thread 1-2) Setting the server's publish address to be >>>>>>>>> http://localhost:8080/AheadCMS-Backend/WebApiImpl >>>>>>>>> 10:16:16,492 INFO [org.jboss.ws.cxf.deployment] (MSC service >>>>>>>>> thread 1-2) JBWS024074: WSDL published to: >>>>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/WebApiImplService.wsdl >>>>>>>>> 10:16:16,493 INFO >>>>>>>>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service >>>>>>>>> thread 1-2) Creating Service { >>>>>>>>> http://webservice.backend.cms.aheaditec.com/}MobileApiImplService >>>>>>>>> from class com.aheaditec.cms.backend.webservice.MobileApi >>>>>>>>> 10:16:16,664 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC >>>>>>>>> service thread 1-2) Setting the server's publish address to be >>>>>>>>> http://localhost:8080/AheadCMS-Backend/MobileApiImpl >>>>>>>>> 10:16:16,763 INFO [org.jboss.ws.cxf.deployment] (MSC service >>>>>>>>> thread 1-2) JBWS024074: WSDL published to: >>>>>>>>> file:/opt/jboss/domain/servers/server-A/data/wsdl/AheadCMS-Backend.war/MobileApiImplService.wsdl >>>>>>>>> 10:16:16,772 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>>> 1-1) JBAS015539: Starting service jboss.ws.port-component-link >>>>>>>>> 10:16:16,779 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>>> 1-1) JBAS015539: Starting service >>>>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.WebApiImpl" >>>>>>>>> 10:16:16,788 INFO [org.jboss.as.webservices] (MSC service thread >>>>>>>>> 1-2) JBAS015539: Starting service >>>>>>>>> jboss.ws.endpoint."AheadCMS-Backend.war"."com.aheaditec.cms.backend.webservice.MobileApiImpl" >>>>>>>>> 10:16:16,795 INFO [org.jboss.as.jpa] (ServerService Thread Pool >>>>>>>>> -- 50) JBAS011402: Starting Persistence Unit Service >>>>>>>>> 'AheadCMS-Backend.war#persistenceUnit' >>>>>>>>> 10:16:17,190 INFO [org.hibernate.annotations.common.Version] >>>>>>>>> (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons >>>>>>>>> Annotations {4.0.1.Final-redhat-2} >>>>>>>>> 10:16:17,214 INFO [org.hibernate.Version] (ServerService Thread >>>>>>>>> Pool -- 50) HHH000412: Hibernate Core {4.2.14.SP1-redhat-1} >>>>>>>>> 10:16:17,222 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>>>> Thread Pool -- 50) HHH000206: hibernate.properties not found >>>>>>>>> 10:16:17,226 INFO [org.hibernate.cfg.Environment] (ServerService >>>>>>>>> Thread Pool -- 50) HHH000021: Bytecode provider name : javassist >>>>>>>>> 10:16:17,323 INFO [org.hibernate.ejb.Ejb3Configuration] >>>>>>>>> (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo >>>>>>>>> [ >>>>>>>>> name: persistenceUnit >>>>>>>>> ...] >>>>>>>>> 10:16:17,838 INFO >>>>>>>>> [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] >>>>>>>>> (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit >>>>>>>>> connection provider: >>>>>>>>> org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >>>>>>>>> 10:16:18,177 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>>> 10:16:18,983 INFO >>>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>>> 10:16:19,008 INFO >>>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>>> 10:16:19,015 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>>>> 10:16:21,168 WARN [org.hibernate.internal.SessionFactoryImpl] >>>>>>>>> (ServerService Thread Pool -- 50) HHH000008: JTASessionContext being used >>>>>>>>> with JDBCTransactionFactory; auto-flush will not operate correctly with >>>>>>>>> getCurrentSession() >>>>>>>>> 10:16:21,329 INFO [org.jboss.web] (ServerService Thread Pool -- >>>>>>>>> 50) JBAS018210: Register web context: /AheadCMS-Backend >>>>>>>>> 10:16:22,048 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>>> Thread Pool -- 50) HHH000400: Using dialect: >>>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>>> 10:16:22,141 INFO >>>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>>> (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: >>>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>>> 10:16:22,145 INFO >>>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>>> Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>>> 10:16:22,145 WARN [org.hibernate.cfg.SettingsFactory] >>>>>>>>> (ServerService Thread Pool -- 50) Unrecognized value for >>>>>>>>> "hibernate.hbm2ddl.auto": none >>>>>>>>> 10:16:24,077 INFO >>>>>>>>> [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] >>>>>>>>> (ServerService Thread Pool -- 51) Initializing database schema >>>>>>>>> 10:16:28,355 INFO [org.hibernate.dialect.Dialect] (ServerService >>>>>>>>> Thread Pool -- 51) HHH000400: Using dialect: >>>>>>>>> org.hibernate.dialect.Oracle10gDialect >>>>>>>>> 10:16:28,669 INFO >>>>>>>>> [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] >>>>>>>>> (ServerService Thread Pool -- 51) HHH000268: Transaction strategy: >>>>>>>>> org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory >>>>>>>>> 10:16:28,670 INFO >>>>>>>>> [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService >>>>>>>>> Thread Pool -- 51) HHH000397: Using ASTQueryTranslatorFactory >>>>>>>>> 10:16:29,687 INFO >>>>>>>>> [org.keycloak.services.managers.ApplianceBootstrap] (ServerService Thread >>>>>>>>> Pool -- 51) Initializing master realm >>>>>>>>> 10:16:33,552 INFO >>>>>>>>> [org.keycloak.services.resources.KeycloakApplication] (ServerService >>>>>>>>> Thread Pool -- 51) Imported realm aerogear from resource >>>>>>>>> /WEB-INF/ups-realm.json >>>>>>>>> 10:16:33,595 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>>> (ServerService Thread Pool -- 51) Deploying javax.ws.rs.core.Application: >>>>>>>>> class org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication >>>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>>> org.keycloak.services.resources.admin.AdminRoot from Application >>>>>>>>> javax.ws.rs.core.Application >>>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>>> org.keycloak.services.resources.SocialResource from Application >>>>>>>>> javax.ws.rs.core.Application >>>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>>> org.keycloak.services.resources.RealmsResource from Application >>>>>>>>> javax.ws.rs.core.Application >>>>>>>>> 10:16:33,596 INFO [org.jboss.resteasy.spi.ResteasyDeployment] >>>>>>>>> (ServerService Thread Pool -- 51) Adding singleton resource >>>>>>>>> org.keycloak.services.resources.ServerVersionResource from Application >>>>>>>>> javax.ws.rs.core.Application >>>>>>>>> 10:16:33,824 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>>> JBAS018559: Deployed "auth-server.war" (runtime-name : "auth-server.war") >>>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>>> JBAS018559: Deployed "AheadCMS-Frontend.war" (runtime-name : >>>>>>>>> "AheadCMS-Frontend.war") >>>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>>> JBAS018559: Deployed "AheadCMS-Backend.war" (runtime-name : >>>>>>>>> "AheadCMS-Backend.war") >>>>>>>>> 10:16:33,825 INFO [org.jboss.as.server] (Controller Boot Thread) >>>>>>>>> JBAS018559: Deployed "EnvTest-1.0.war" (runtime-name : "EnvTest-1.0.war") >>>>>>>>> 10:16:33,838 INFO [org.jboss.as] (Controller Boot Thread) >>>>>>>>> JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started >>>>>>>>> in 37203ms - Started 366 of 408 services (70 services are lazy, passive or >>>>>>>>> on-demand) >>>>>>>>> 10:16:44,198 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: >>>>>>>>> "ag-push.war") >>>>>>>>> 10:16:46,424 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,425 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,426 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyReader' >>>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,427 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,428 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' >>>>>>>>> for service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,429 WARN [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-1) JBAS015893: Encountered invalid class name >>>>>>>>> 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for >>>>>>>>> service type 'javax.ws.rs.ext.MessageBodyWriter' >>>>>>>>> 10:16:46,634 INFO [org.jboss.as.jpa] (MSC service thread 1-1) >>>>>>>>> JBAS011401: Read persistence.xml for unifiedpush-default >>>>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>>> removed in future versions without notice. >>>>>>>>> 10:16:46,796 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>>> private module ("org.apache.httpcomponents:main") which may be changed or >>>>>>>>> removed in future versions without notice. >>>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>>> changed or removed in future versions without notice. >>>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-core-asl:main") which may be >>>>>>>>> changed or removed in future versions without notice. >>>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>>> be changed or removed in future versions without notice. >>>>>>>>> 10:16:46,797 WARN [org.jboss.as.dependency.private] (MSC service >>>>>>>>> thread 1-2) JBAS018567: Deployment "deployment.ag-push.war" is using a >>>>>>>>> private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may >>>>>>>>> be changed or removed in future versions without notice. >>>>>>>>> 10:16:47,056 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>>>> 1-1) JBAS016002: Processing weld deployment ag-push.war >>>>>>>>> 10:16:47,154 INFO >>>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>>> ClientInstallationServiceImpl in deployment unit deployment "ag-push.war" >>>>>>>>> are as follows: >>>>>>>>> >>>>>>>>> >>>>>>>>> java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>>> >>>>>>>>> java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>>> >>>>>>>>> java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService >>>>>>>>> java:global/ag-push/ClientInstallationServiceImpl >>>>>>>>> java:app/ag-push/ClientInstallationServiceImpl >>>>>>>>> java:module/ClientInstallationServiceImpl >>>>>>>>> >>>>>>>>> 10:16:47,155 INFO >>>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>>> GenericVariantServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>>>> as follows: >>>>>>>>> >>>>>>>>> >>>>>>>>> java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>>> >>>>>>>>> java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>>> >>>>>>>>> java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService >>>>>>>>> java:global/ag-push/GenericVariantServiceImpl >>>>>>>>> java:app/ag-push/GenericVariantServiceImpl >>>>>>>>> java:module/GenericVariantServiceImpl >>>>>>>>> >>>>>>>>> 10:16:47,155 INFO >>>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>>> PushApplicationServiceImpl in deployment unit deployment "ag-push.war" are >>>>>>>>> as follows: >>>>>>>>> >>>>>>>>> >>>>>>>>> java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>>> >>>>>>>>> java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>>> >>>>>>>>> java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService >>>>>>>>> java:global/ag-push/PushApplicationServiceImpl >>>>>>>>> java:app/ag-push/PushApplicationServiceImpl >>>>>>>>> java:module/PushApplicationServiceImpl >>>>>>>>> >>>>>>>>> 10:16:47,156 INFO >>>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>>> DeleteOldPushMessageInformationScheduler in deployment unit deployment >>>>>>>>> "ag-push.war" are as follows: >>>>>>>>> >>>>>>>>> >>>>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>>> >>>>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>>> >>>>>>>>> java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler >>>>>>>>> java:global/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>>>> java:app/ag-push/DeleteOldPushMessageInformationScheduler >>>>>>>>> java:module/DeleteOldPushMessageInformationScheduler >>>>>>>>> >>>>>>>>> 10:16:47,156 INFO >>>>>>>>> [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] >>>>>>>>> (MSC service thread 1-1) JNDI bindings for session bean named >>>>>>>>> SenderServiceImpl in deployment unit deployment "ag-push.war" are as >>>>>>>>> follows: >>>>>>>>> >>>>>>>>> >>>>>>>>> java:global/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>>> >>>>>>>>> java:app/ag-push/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>>> >>>>>>>>> java:module/SenderServiceImpl!org.jboss.aerogear.unifiedpush.message.SenderService >>>>>>>>> java:global/ag-push/SenderServiceImpl >>>>>>>>> java:app/ag-push/SenderServiceImpl >>>>>>>>> java:module/SenderServiceImpl >>>>>>>>> >>>>>>>>> 10:16:47,544 INFO [org.jboss.weld.deployer] (MSC service thread >>>>>>>>> 1-2) JBAS016005: Starting Services for CDI deployment: ag-push.war >>>>>>>>> 10:16:47,655 INFO [org.jboss.weld.Version] (MSC service thread >>>>>>>>> 1-2) WELD-000900 1.1.23 (redhat) >>>>>>>>> 10:16:47,679 ERROR [org.jboss.msc.service.fail] (MSC service >>>>>>>>> thread 1-2) MSC000001: Failed to start service >>>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: >>>>>>>>> org.jboss.msc.service.StartException in service >>>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL: JBAS018733: Failed to process >>>>>>>>> phase INSTALL of deployment "ag-push.war" >>>>>>>>> at >>>>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) >>>>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>>>> 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] >>>>>>>>> at >>>>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>>>> [rt.jar:1.7.0_75] >>>>>>>>> at >>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>>>> [rt.jar:1.7.0_75] >>>>>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] >>>>>>>>> Caused by: >>>>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>>>> JBAS018096: Error instantiating container component: >>>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>>>> at >>>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:423) >>>>>>>>> at >>>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:231) >>>>>>>>> at >>>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126) >>>>>>>>> at >>>>>>>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) >>>>>>>>> [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] >>>>>>>>> ... 5 more >>>>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>>>> "deployment.ag-push.war:main" from Service Module Loader] >>>>>>>>> at >>>>>>>>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) >>>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>>> at >>>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) >>>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>>> at >>>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) >>>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>>> at >>>>>>>>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) >>>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>>> at >>>>>>>>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) >>>>>>>>> [jboss-modules.jar:1.3.3.Final-redhat-1] >>>>>>>>> at >>>>>>>>> org.jboss.as.web.deployment.WarDeploymentProcessor.getInstance(WarDeploymentProcessor.java:415) >>>>>>>>> ... 8 more >>>>>>>>> >>>>>>>>> 10:16:47,740 ERROR [org.jboss.as.server] (ServerService Thread >>>>>>>>> Pool -- 14) JBAS015870: Deploy of deployment "ag-push.war" was rolled back >>>>>>>>> with the following failure message: >>>>>>>>> { >>>>>>>>> "JBAS014671: Failed services" => >>>>>>>>> {"jboss.deployment.unit.\"ag-push.war\".INSTALL" => >>>>>>>>> "org.jboss.msc.service.StartException in service >>>>>>>>> jboss.deployment.unit.\"ag-push.war\".INSTALL: JBAS018733: Failed to >>>>>>>>> process phase INSTALL of deployment \"ag-push.war\" >>>>>>>>> Caused by: >>>>>>>>> org.jboss.as.server.deployment.DeploymentUnitProcessingException: >>>>>>>>> JBAS018096: Error instantiating container component: >>>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve >>>>>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>>>>> org.keycloak.adapters.as7.KeycloakAuthenticatorValve from [Module >>>>>>>>> \"deployment.ag-push.war:main\" from Service Module Loader]"}, >>>>>>>>> "JBAS014771: Services with missing/unavailable dependencies" >>>>>>>>> => ["jboss.deployment.unit.\"ag-push.war\".weld.weldClassIntrospector is >>>>>>>>> missing [jboss.deployment.unit.\"ag-push.war\".beanmanager]"] >>>>>>>>> } >>>>>>>>> 10:16:47,764 INFO [org.jboss.as.server.deployment] (MSC service >>>>>>>>> thread 1-2) JBAS015877: Stopped deployment ag-push.war (runtime-name: >>>>>>>>> ag-push.war) in 29ms >>>>>>>>> 10:16:47,769 INFO [org.jboss.as.controller] (ServerService Thread >>>>>>>>> Pool -- 14) JBAS014774: Service status report >>>>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>>>> service jboss.deployment.unit."ag-push.war".beanmanager >>>>>>>>> (missing) dependents: [service >>>>>>>>> jboss.deployment.unit."ag-push.war".weld.weldClassIntrospector] >>>>>>>>> JBAS014777: Services which failed to start: service >>>>>>>>> jboss.deployment.unit."ag-push.war".INSTALL >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks for help ... >>>>>>>>> >>>>>>>>> *Mgr. Ivan G?rtler* >>>>>>>>> Mobile software developer >>>>>>>>> >>>>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>>>> 602 00 Brno (Czech Republic) >>>>>>>>> >>>>>>>>> www.ahead-itec.com | twitter | >>>>>>>>> mobile security solutions >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Matthias Wessendorf >>>>>>>> >>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.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 >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150225/371e4cd3/attachment-0001.html From daniel.bevenius at gmail.com Wed Feb 25 04:53:20 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 25 Feb 2015 10:53:20 +0100 Subject: [aerogear-dev] Cordova OAuth2 1.0.2 released In-Reply-To: References: <16D6B7D9-8CC8-473E-A23A-A6651B6F06B7@redhat.com> Message-ID: +1 nice job! On 24 February 2015 at 17:17, Matthias Wessendorf wrote: > hey Erik, > > great job getting this out ! > > > > On Tue, Feb 24, 2015 at 5:07 PM, Erik Jan de Wit > wrote: > >> Hi, >> >> It?s a pleasure to annouce that the Cordova OAuth2 plugin version 1.0.2 >> has been released changelog: >> >> AGCORDOVA-58 - Update >> OAuth2 swift lib to version 0.2.0 >> AGCORDOVA-65 - Update >> OAuth2 plugin to AGDROID 2.0 >> AGCORDOVA-46 - Add >> windows support Oauth2 >> >> 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/20150225/565f40e7/attachment.html From matzew at apache.org Wed Feb 25 05:20:12 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 25 Feb 2015 11:20:12 +0100 Subject: [aerogear-dev] Roadmap: UPS - release dates Message-ID: Hi, based on recent work and found issues, I have adjusted the roadmap for our releases https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel Let me know if there are questions or concerns around the updates. 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/20150225/bbea0b62/attachment.html From lukas.fryc at gmail.com Wed Feb 25 06:54:57 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 25 Feb 2015 12:54:57 +0100 Subject: [aerogear-dev] Roadmap: UPS - release dates In-Reply-To: References: Message-ID: +1 Works fine with the UPS UX revamp (beta1) On Wed, Feb 25, 2015 at 11:20 AM, Matthias Wessendorf wrote: > Hi, > > based on recent work and found issues, I have adjusted the roadmap for our > releases > > > https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > Let me know if there are questions or concerns around the updates. > > Thanks, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/8acfe8bd/attachment.html From lukas.fryc at gmail.com Wed Feb 25 10:09:42 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 25 Feb 2015 16:09:42 +0100 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> Message-ID: On Tue, Feb 24, 2015 at 6:26 PM, Lucas Holmquist wrote: > I'm not sure what the reason for this was historically. I think this > concept was initally created when we were doing Pipeline. > Wasn't that because you want to share configuration of stores in one DataManager? But fully agree, it does not make much sense from user's perspective - you can share options object anyway. > I am leaning toward proposing we get rid of this pattern and just make a > DataManager object hold 1 store/adapter( sync woud follow suit ) > +1 agree -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/c95a85c5/attachment.html From lukas.fryc at gmail.com Wed Feb 25 10:11:30 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 25 Feb 2015 16:11:30 +0100 Subject: [aerogear-dev] AeroGear.js In-Reply-To: <242EE819-D489-4CA0-A62F-FEE40F9656F4@redhat.com> References: <91EBB6E9-8C24-484B-84AF-9CE2665D7310@redhat.com> <20150224181122.GA4922@abstractj.org> <242EE819-D489-4CA0-A62F-FEE40F9656F4@redhat.com> Message-ID: +1 I believe AeroGear-Components is a way to go - distribute the lib in several components, but built from one source code / repository. On Tue, Feb 24, 2015 at 7:26 PM, Lucas Holmquist wrote: > > I think AeroGear.Core would essentially go away since it is only > providing, the ?add? and ?remove? methods for the ?Fancy Arrays?, if we > stop doing that pattern, then i don?t think this would be needed. > > Thinking a little bit more, we don?t need separte repo?s for each > feature. Thats what we can use AeroGear-Components thingy to distribute > via bower. We can script that shizzell, to create custom feature builds > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/6ff34157/attachment.html From bleathem at gmail.com Wed Feb 25 10:21:33 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 07:21:33 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> <81FA1D7E-C30F-48CA-BB9E-EB49EECDC0CA@redhat.com> Message-ID: <54EDE87D.5060308@gmail.com> Thanks for the feedback guys, I'll look at creating a PR promptly. Brian On 2015-02-25 12:22 AM, Matthias Wessendorf wrote: > +1 on joing forces :-) (see also passos' hint) > hehe > > On Wed, Feb 25, 2015 at 8:01 AM, Erik Jan de Wit > wrote: > > Hi Brian, > > Cool stuff, seems like your javascript api is very similar to what > we have on the cordova plugin. Would be great if you could add it. > > Cheers, > Erik Jan > > > On 24 Feb,2015, at 19:46 , Brian Leathem > wrote: > > > > Hey gear-heads, > > > > I recently wrote a Cordova plugin that retrieves a Oauth2 token on > > Android using Google Play Services. The advantage of this > approach is > > it leverages the single-sign-on capabilities of android, and the > app can > > retrieve the Oauth2 token without requiring Authentication from the > > user. I blogged about it here: > > > > > http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html > > > > Using a promise-based API it's fairly trivial to fallback to a > > traditional Web authentication/authorisation for the Oauth2 > token when > > the google-play-services approach isn't supported. > > > > I'm aware the aerogear team has a Oauth2 cordova plugin [1], but > it's > > not clear to me if the google-play-services integration is > supported. > > If the Aerogeam would find it useful, I'd be more than happy to > provide > > a PR to the aerogear cordova plugin providing such integration. > > > > Thoughts? > > Brian > > > > [1] > > > http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150225/2d97ffb0/attachment-0001.html From lukas.fryc at gmail.com Wed Feb 25 11:29:16 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 25 Feb 2015 17:29:16 +0100 Subject: [aerogear-dev] New Site - Home Page user testing Message-ID: Hey guys, moving a discussions about The Home Page from IRC to the aerogear-dev: This is a current test version: http://staging-aerogearsite.rhcloud.com/ What we have done from the previous state? Removed a lot of stuff: http://staging-aerogearsite.rhcloud.com/lfryc/new-design-build/ 1. animation 2. Cross-platform section 3. What is happening section What you guys think? Like / dislike? ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/574322e8/attachment.html From scm.blanc at gmail.com Wed Feb 25 11:32:56 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 25 Feb 2015 17:32:56 +0100 Subject: [aerogear-dev] New Site - Home Page user testing In-Reply-To: References: Message-ID: Like I said on IRC : The "Hey Listen" banner is way too big/large and and it's duplicated with the first item of "latest news" On Wed, Feb 25, 2015 at 5:29 PM, Luk?? Fry? wrote: > Hey guys, > > moving a discussions about The Home Page from IRC to the aerogear-dev: > > This is a current test version: > > http://staging-aerogearsite.rhcloud.com/ > > > What we have done from the previous state? Removed a lot of stuff: > http://staging-aerogearsite.rhcloud.com/lfryc/new-design-build/ > > 1. animation > 2. Cross-platform section > 3. What is happening section > > > What you guys think? Like / dislike? > > > ~ 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/20150225/497dd41b/attachment.html From lukas.fryc at gmail.com Wed Feb 25 11:34:38 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 25 Feb 2015 17:34:38 +0100 Subject: [aerogear-dev] New Site - Home Page user testing In-Reply-To: References: Message-ID: Shift+F5 please, you have old version :-) On Wed, Feb 25, 2015 at 5:32 PM, Sebastien Blanc wrote: > Like I said on IRC : > The "Hey Listen" banner is way too big/large and and it's duplicated with > the first item of "latest news" > > > On Wed, Feb 25, 2015 at 5:29 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> moving a discussions about The Home Page from IRC to the aerogear-dev: >> >> This is a current test version: >> >> http://staging-aerogearsite.rhcloud.com/ >> >> >> What we have done from the previous state? Removed a lot of stuff: >> http://staging-aerogearsite.rhcloud.com/lfryc/new-design-build/ >> >> 1. animation >> 2. Cross-platform section >> 3. What is happening section >> >> >> What you guys think? Like / dislike? >> >> >> ~ 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/20150225/879be79a/attachment.html From corinnekrych at gmail.com Wed Feb 25 12:33:56 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 25 Feb 2015 18:33:56 +0100 Subject: [aerogear-dev] AeroGearHttpStub is gone, long live OHHTTPStubs Message-ID: <9D91D000-0B6C-4B00-B60E-6B3777230010@gmail.com> Hello iOS folk, Early February, I met Olivier (creator of OHHTTPStubs [1]) at dotSwift conference in Paris. We had a nice discussion about mocking libraries using dynamic features like obj-c Swizzling [2]. In Swift, runtime introspecting is very limited (some MirrorType - but really meant for IDE). In fact, to achieve dynamic mocking you have to use Obj-C/Swift bridging. For mocking object like NSURLSession (inheriting from NSObject) using the bridge is just fine. Therefore, keeping the HTTP stub layer an Obj-C lib fits the needs (so far). Further improvement could be done via wrapping. Following Olivier suggestion to join the effort in maintening OHHTTPStubs librarie [3], we deprecated AeroGearHttpStubs today [4], let?s work together on improving http mocking experience. Stay tune for more PR. ++ Corinne [1] https://github.com/AliSoftware/OHHTTPStubs [2] http://corinnekrych.blogspot.fr/2014/07/http-stubs-lets-go-swift-swizzling.html [3] https://github.com/aerogear/aerogear-ios-httpstub/issues/15 [4] https://github.com/aerogear/aerogear-ios-httpstub From lukas.fryc at gmail.com Wed Feb 25 13:14:41 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 25 Feb 2015 19:14:41 +0100 Subject: [aerogear-dev] AeroGear Site 2.0 - Dashboard Message-ID: Hey guys, just wanted to share we are using this dashboard to track the development of new Site: https://issues.jboss.org/secure/Dashboard.jspa?selectPageId=12318207&_sscc=t Feel free to take anything in category Unassigned. Cheers! ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/2d4e3234/attachment.html From bleathem at gmail.com Wed Feb 25 13:30:31 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 10:30:31 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> Message-ID: <54EE14C7.8090007@gmail.com> ... and the devil is in the details. It seems as though all the current AuzthzModules use an http based approach to requesting an Oauth2 token. I see this being done in OAuth2WebFragmentFetchAutorization#doAuthorization method, where an OAuthWebViewDialog is used to trigger the Oauth2 token request. To use Google Play services to trigger an Oauth2 token request, we won't use an http approach, but rather we start an activity to select an account and request an Oauth2 token. Once the token is retrieved it can then be used with the standard http Oauth2 API. (One caveat: the google play services token response doesn't provide a refresh token. I believe this to be a non-issue as the token request process is trivial when using google play services (no authentication step)). I see to ways to implement this feature: 1) Generalize the OAuth2WebFragmentFetchAutorization into an interface, and have one implementation to handle http-based token requests, and second implementation to handle intent-based token requests. 2) Add a OAuth2AuthorizationConfiguration option to use intents instead of http, and trigger a different workflow within the OAuth2WebFragmentFetchAutorization#doAuthorization method if that config is set. My preference is for 2) because it's a) simpler, and b) it is really only during the #doAuthorization method that we have a different approach. Thoughts? I'll start with implementing approach (2) unless I hear otherwise. Brian On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: > > > On Wednesday, February 25, 2015, Daniel Passos > wrote: > > No, we are not using Google Play services API for now for OAuth2 > in Android land. > > But feel free create a new AuthzModule[1] for it ;) > > > +1 > > > > [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java > > -- Passos > > > On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc > > wrote: > > Cool stuff Brian ! > The AeroGear OAuth2 Cordova plugin relies on the Native > AeroGear OAuth2 Libraries, so maybe Summers and/or Daniel > could tell more about it. > Sebi > > > On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem > > wrote: > > Hey gear-heads, > > I recently wrote a Cordova plugin that retrieves a Oauth2 > token on > Android using Google Play Services. The advantage of this > approach is > it leverages the single-sign-on capabilities of android, > and the app can > retrieve the Oauth2 token without requiring Authentication > from the > user. I blogged about it here: > > http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html > > Using a promise-based API it's fairly trivial to fallback to a > traditional Web authentication/authorisation for the > Oauth2 token when > the google-play-services approach isn't supported. > > I'm aware the aerogear team has a Oauth2 cordova plugin > [1], but it's > not clear to me if the google-play-services integration is > supported. > If the Aerogeam would find it useful, I'd be more than > happy to provide > a PR to the aerogear cordova plugin providing such > integration. > > Thoughts? > Brian > > [1] > http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > 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/20150225/dfd4373c/attachment-0001.html From daniel at passos.me Wed Feb 25 13:44:28 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 25 Feb 2015 15:44:28 -0300 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EE14C7.8090007@gmail.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> Message-ID: Hey Brian, You can. but not necessarily need do that.. You can create your own workflow. Just implement your own: - OAuth2AuthroizationConfigurationProvider - AuthorizationConfiguration - AuthzModule.java And let the AuthorizationManager know[1] your new Authz AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 -- Passos ? On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem wrote: > ... and the devil is in the details. > > It seems as though all the current AuzthzModules use an http based > approach to requesting an Oauth2 token. I see this being done in > OAuth2WebFragmentFetchAutorization#doAuthorization method, where an > OAuthWebViewDialog is used to trigger the Oauth2 token request. > > To use Google Play services to trigger an Oauth2 token request, we won't > use an http approach, but rather we start an activity to select an account > and request an Oauth2 token. Once the token is retrieved it can then be > used with the standard http Oauth2 API. > > (One caveat: the google play services token response doesn't provide a > refresh token. I believe this to be a non-issue as the token request > process is trivial when using google play services (no authentication > step)). > > I see to ways to implement this feature: > > 1) Generalize the OAuth2WebFragmentFetchAutorization into an interface, > and have one implementation to handle http-based token requests, and second > implementation to handle intent-based token requests. > > 2) Add a OAuth2AuthorizationConfiguration option to use intents instead of > http, and trigger a different workflow within the > OAuth2WebFragmentFetchAutorization#doAuthorization method if that config is > set. > > My preference is for 2) because it's a) simpler, and b) it is really only > during the #doAuthorization method that we have a different approach. > > Thoughts? I'll start with implementing approach (2) unless I hear > otherwise. > > Brian > > > On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: > > > > On Wednesday, February 25, 2015, Daniel Passos wrote: > >> No, we are not using Google Play services API for now for OAuth2 in >> Android land. >> >> But feel free create a new AuthzModule[1] for it ;) >> > > +1 > > >> >> [1] >> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >> >> -- Passos >> >> >> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >> wrote: >> >>> Cool stuff Brian ! >>> The AeroGear OAuth2 Cordova plugin relies on the Native AeroGear OAuth2 >>> Libraries, so maybe Summers and/or Daniel could tell more about it. >>> Sebi >>> >>> >>> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >>> wrote: >>> >>>> Hey gear-heads, >>>> >>>> I recently wrote a Cordova plugin that retrieves a Oauth2 token on >>>> Android using Google Play Services. The advantage of this approach is >>>> it leverages the single-sign-on capabilities of android, and the app can >>>> retrieve the Oauth2 token without requiring Authentication from the >>>> user. I blogged about it here: >>>> >>>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>>> >>>> Using a promise-based API it's fairly trivial to fallback to a >>>> traditional Web authentication/authorisation for the Oauth2 token when >>>> the google-play-services approach isn't supported. >>>> >>>> I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's >>>> not clear to me if the google-play-services integration is supported. >>>> If the Aerogeam would find it useful, I'd be more than happy to provide >>>> a PR to the aerogear cordova plugin providing such integration. >>>> >>>> Thoughts? >>>> Brian >>>> >>>> [1] >>>> >>>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > Sent from Gmail Mobile > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/0103f065/attachment.html From bleathem at gmail.com Wed Feb 25 13:59:21 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 10:59:21 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> Message-ID: <54EE1B89.3010502@gmail.com> Great, thanks for the insight David, I'll go bark up that tree for a while. Brian On 2015-02-25 10:44 AM, Daniel Passos wrote: > > Hey Brian, > > You can. but not necessarily need do that.. You can create your own > workflow. > > Just implement your own: > > * > > OAuth2AuthroizationConfigurationProvider > > * > > AuthorizationConfiguration > > * AuthzModule.java > > And let the |AuthorizationManager| know[1] your new Authz > > |AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) > | > > [1] > https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 > > -- Passos > > > ? > > On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem > wrote: > > ... and the devil is in the details. > > It seems as though all the current AuzthzModules use an http based > approach to requesting an Oauth2 token. I see this being done in > OAuth2WebFragmentFetchAutorization#doAuthorization method, where > an OAuthWebViewDialog is used to trigger the Oauth2 token request. > > To use Google Play services to trigger an Oauth2 token request, we > won't use an http approach, but rather we start an activity to > select an account and request an Oauth2 token. Once the token is > retrieved it can then be used with the standard http Oauth2 API. > > (One caveat: the google play services token response doesn't > provide a refresh token. I believe this to be a non-issue as the > token request process is trivial when using google play services > (no authentication step)). > > I see to ways to implement this feature: > > 1) Generalize the OAuth2WebFragmentFetchAutorization into an > interface, and have one implementation to handle http-based token > requests, and second implementation to handle intent-based token > requests. > > 2) Add a OAuth2AuthorizationConfiguration option to use intents > instead of http, and trigger a different workflow within the > OAuth2WebFragmentFetchAutorization#doAuthorization method if that > config is set. > > My preference is for 2) because it's a) simpler, and b) it is > really only during the #doAuthorization method that we have a > different approach. > > Thoughts? I'll start with implementing approach (2) unless I hear > otherwise. > > Brian > > > On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: >> >> >> On Wednesday, February 25, 2015, Daniel Passos > > wrote: >> >> No, we are not using Google Play services API for now for >> OAuth2 in Android land. >> >> But feel free create a new AuthzModule[1] for it ;) >> >> >> +1 >> >> >> >> [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >> >> -- Passos >> >> >> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >> wrote: >> >> Cool stuff Brian ! >> The AeroGear OAuth2 Cordova plugin relies on the Native >> AeroGear OAuth2 Libraries, so maybe Summers and/or >> Daniel could tell more about it. >> Sebi >> >> >> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >> wrote: >> >> Hey gear-heads, >> >> I recently wrote a Cordova plugin that retrieves a >> Oauth2 token on >> Android using Google Play Services. The advantage of >> this approach is >> it leverages the single-sign-on capabilities of >> android, and the app can >> retrieve the Oauth2 token without requiring >> Authentication from the >> user. I blogged about it here: >> >> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >> >> Using a promise-based API it's fairly trivial to >> fallback to a >> traditional Web authentication/authorisation for the >> Oauth2 token when >> the google-play-services approach isn't supported. >> >> I'm aware the aerogear team has a Oauth2 cordova >> plugin [1], but it's >> not clear to me if the google-play-services >> integration is supported. >> If the Aerogeam would find it useful, I'd be more >> than happy to provide >> a PR to the aerogear cordova plugin providing such >> integration. >> >> Thoughts? >> Brian >> >> [1] >> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Sent from Gmail Mobile >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/35a9b128/attachment-0001.html From matzew at apache.org Wed Feb 25 14:11:00 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 25 Feb 2015 20:11:00 +0100 Subject: [aerogear-dev] New Site - Home Page user testing In-Reply-To: References: Message-ID: looks very good On Wed, Feb 25, 2015 at 5:34 PM, Luk?? Fry? wrote: > Shift+F5 please, you have old version :-) > > On Wed, Feb 25, 2015 at 5:32 PM, Sebastien Blanc > wrote: > >> Like I said on IRC : >> The "Hey Listen" banner is way too big/large and and it's duplicated with >> the first item of "latest news" >> >> >> On Wed, Feb 25, 2015 at 5:29 PM, Luk?? Fry? wrote: >> >>> Hey guys, >>> >>> moving a discussions about The Home Page from IRC to the aerogear-dev: >>> >>> This is a current test version: >>> >>> http://staging-aerogearsite.rhcloud.com/ >>> >>> >>> What we have done from the previous state? Removed a lot of stuff: >>> http://staging-aerogearsite.rhcloud.com/lfryc/new-design-build/ >>> >>> 1. animation >>> 2. Cross-platform section >>> 3. What is happening section >>> >>> >>> What you guys think? Like / dislike? >>> >>> >>> ~ 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/2a655a0b/attachment.html From supittma at redhat.com Wed Feb 25 14:14:46 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 25 Feb 2015 14:14:46 -0500 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EE1B89.3010502@gmail.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE1B89.3010502@gmail.com> Message-ID: <54EE1F26.30802@redhat.com> On 02/25/2015 01:59 PM, Brian Leathem wrote: > Great, thanks for the insight David, I'll go bark up that tree for a > while. https://issues.jboss.org/browse/AGDROID-319?jql=project%20%3D%20AGDROID%20AND%20fixVersion%20%3D%202.2.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC This will probably be necessary to implement to get what you want done. > > Brian > > On 2015-02-25 10:44 AM, Daniel Passos wrote: >> >> Hey Brian, >> >> You can. but not necessarily need do that.. You can create your own >> workflow. >> >> Just implement your own: >> >> * >> >> OAuth2AuthroizationConfigurationProvider >> >> * >> >> AuthorizationConfiguration >> >> * AuthzModule.java >> >> And let the |AuthorizationManager| know[1] your new Authz >> >> |AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) >> | >> >> [1] >> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 >> >> -- Passos >> >> >> ? >> >> On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem > > wrote: >> >> ... and the devil is in the details. >> >> It seems as though all the current AuzthzModules use an http >> based approach to requesting an Oauth2 token. I see this being >> done in OAuth2WebFragmentFetchAutorization#doAuthorization >> method, where an OAuthWebViewDialog is used to trigger the Oauth2 >> token request. >> >> To use Google Play services to trigger an Oauth2 token request, >> we won't use an http approach, but rather we start an activity to >> select an account and request an Oauth2 token. Once the token is >> retrieved it can then be used with the standard http Oauth2 API. >> >> (One caveat: the google play services token response doesn't >> provide a refresh token. I believe this to be a non-issue as the >> token request process is trivial when using google play services >> (no authentication step)). >> >> I see to ways to implement this feature: >> >> 1) Generalize the OAuth2WebFragmentFetchAutorization into an >> interface, and have one implementation to handle http-based token >> requests, and second implementation to handle intent-based token >> requests. >> >> 2) Add a OAuth2AuthorizationConfiguration option to use intents >> instead of http, and trigger a different workflow within the >> OAuth2WebFragmentFetchAutorization#doAuthorization method if that >> config is set. >> >> My preference is for 2) because it's a) simpler, and b) it is >> really only during the #doAuthorization method that we have a >> different approach. >> >> Thoughts? I'll start with implementing approach (2) unless I >> hear otherwise. >> >> Brian >> >> >> On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: >>> >>> >>> On Wednesday, February 25, 2015, Daniel Passos >> > wrote: >>> >>> No, we are not using Google Play services API for now for >>> OAuth2 in Android land. >>> >>> But feel free create a new AuthzModule[1] for it ;) >>> >>> >>> +1 >>> >>> >>> [1] >>> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >>> >>> -- Passos >>> >>> >>> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >>> wrote: >>> >>> Cool stuff Brian ! >>> The AeroGear OAuth2 Cordova plugin relies on the Native >>> AeroGear OAuth2 Libraries, so maybe Summers and/or >>> Daniel could tell more about it. >>> Sebi >>> >>> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >>> wrote: >>> >>> Hey gear-heads, >>> >>> I recently wrote a Cordova plugin that retrieves a >>> Oauth2 token on >>> Android using Google Play Services. The advantage >>> of this approach is >>> it leverages the single-sign-on capabilities of >>> android, and the app can >>> retrieve the Oauth2 token without requiring >>> Authentication from the >>> user. I blogged about it here: >>> >>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>> >>> Using a promise-based API it's fairly trivial to >>> fallback to a >>> traditional Web authentication/authorisation for the >>> Oauth2 token when >>> the google-play-services approach isn't supported. >>> >>> I'm aware the aerogear team has a Oauth2 cordova >>> plugin [1], but it's >>> not clear to me if the google-play-services >>> integration is supported. >>> If the Aerogeam would find it useful, I'd be more >>> than happy to provide >>> a PR to the aerogear cordova plugin providing such >>> integration. >>> >>> Thoughts? >>> Brian >>> >>> [1] >>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- 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/20150225/368fa5ab/attachment-0001.html From bleathem at gmail.com Wed Feb 25 15:41:46 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 12:41:46 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EE1B89.3010502@gmail.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE1B89.3010502@gmail.com> Message-ID: <54EE338A.70509@gmail.com> s/David/Daniel/ :-P Brian On 2015-02-25 10:59 AM, Brian Leathem wrote: > Great, thanks for the insight David, I'll go bark up that tree for a > while. > > Brian > > On 2015-02-25 10:44 AM, Daniel Passos wrote: >> >> Hey Brian, >> >> You can. but not necessarily need do that.. You can create your own >> workflow. >> >> Just implement your own: >> >> * >> >> OAuth2AuthroizationConfigurationProvider >> >> * >> >> AuthorizationConfiguration >> >> * AuthzModule.java >> >> And let the |AuthorizationManager| know[1] your new Authz >> >> |AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) >> | >> >> [1] >> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 >> >> -- Passos >> >> >> ? >> >> On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem > > wrote: >> >> ... and the devil is in the details. >> >> It seems as though all the current AuzthzModules use an http >> based approach to requesting an Oauth2 token. I see this being >> done in OAuth2WebFragmentFetchAutorization#doAuthorization >> method, where an OAuthWebViewDialog is used to trigger the Oauth2 >> token request. >> >> To use Google Play services to trigger an Oauth2 token request, >> we won't use an http approach, but rather we start an activity to >> select an account and request an Oauth2 token. Once the token is >> retrieved it can then be used with the standard http Oauth2 API. >> >> (One caveat: the google play services token response doesn't >> provide a refresh token. I believe this to be a non-issue as the >> token request process is trivial when using google play services >> (no authentication step)). >> >> I see to ways to implement this feature: >> >> 1) Generalize the OAuth2WebFragmentFetchAutorization into an >> interface, and have one implementation to handle http-based token >> requests, and second implementation to handle intent-based token >> requests. >> >> 2) Add a OAuth2AuthorizationConfiguration option to use intents >> instead of http, and trigger a different workflow within the >> OAuth2WebFragmentFetchAutorization#doAuthorization method if that >> config is set. >> >> My preference is for 2) because it's a) simpler, and b) it is >> really only during the #doAuthorization method that we have a >> different approach. >> >> Thoughts? I'll start with implementing approach (2) unless I >> hear otherwise. >> >> Brian >> >> >> On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: >>> >>> >>> On Wednesday, February 25, 2015, Daniel Passos >> > wrote: >>> >>> No, we are not using Google Play services API for now for >>> OAuth2 in Android land. >>> >>> But feel free create a new AuthzModule[1] for it ;) >>> >>> >>> +1 >>> >>> >>> >>> [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >>> >>> -- Passos >>> >>> >>> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >>> wrote: >>> >>> Cool stuff Brian ! >>> The AeroGear OAuth2 Cordova plugin relies on the Native >>> AeroGear OAuth2 Libraries, so maybe Summers and/or >>> Daniel could tell more about it. >>> Sebi >>> >>> >>> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >>> wrote: >>> >>> Hey gear-heads, >>> >>> I recently wrote a Cordova plugin that retrieves a >>> Oauth2 token on >>> Android using Google Play Services. The advantage >>> of this approach is >>> it leverages the single-sign-on capabilities of >>> android, and the app can >>> retrieve the Oauth2 token without requiring >>> Authentication from the >>> user. I blogged about it here: >>> >>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>> >>> Using a promise-based API it's fairly trivial to >>> fallback to a >>> traditional Web authentication/authorisation for the >>> Oauth2 token when >>> the google-play-services approach isn't supported. >>> >>> I'm aware the aerogear team has a Oauth2 cordova >>> plugin [1], but it's >>> not clear to me if the google-play-services >>> integration is supported. >>> If the Aerogeam would find it useful, I'd be more >>> than happy to provide >>> a PR to the aerogear cordova plugin providing such >>> integration. >>> >>> Thoughts? >>> Brian >>> >>> [1] >>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/60521e7b/attachment.html From bleathem at gmail.com Wed Feb 25 15:47:20 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 12:47:20 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EE1F26.30802@redhat.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE1B89.3010502@gmail.com> <54EE1F26.30802@redhat.com> Message-ID: <54EE34D8.9060601@gmail.com> Thanks Summers. Having looked closely at this I think it's related, but non-blocking to using google-play-services as an oauth2 token provider. I'll see if I can perhaps resolve the Dialog -> Intent replacement after cutting my teeth on the google-play-services implementation. Brian On 2015-02-25 11:14 AM, Summers Pittman wrote: > On 02/25/2015 01:59 PM, Brian Leathem wrote: >> Great, thanks for the insight David, I'll go bark up that tree for a >> while. > https://issues.jboss.org/browse/AGDROID-319?jql=project%20%3D%20AGDROID%20AND%20fixVersion%20%3D%202.2.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > This will probably be necessary to implement to get what you want done. >> >> Brian >> >> On 2015-02-25 10:44 AM, Daniel Passos wrote: >>> >>> Hey Brian, >>> >>> You can. but not necessarily need do that.. You can create your own >>> workflow. >>> >>> Just implement your own: >>> >>> * >>> >>> OAuth2AuthroizationConfigurationProvider >>> >>> * >>> >>> AuthorizationConfiguration >>> >>> * AuthzModule.java >>> >>> And let the |AuthorizationManager| know[1] your new Authz >>> >>> |AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) >>> | >>> >>> [1] >>> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 >>> >>> -- Passos >>> >>> >>> ? >>> >>> On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem >> > wrote: >>> >>> ... and the devil is in the details. >>> >>> It seems as though all the current AuzthzModules use an http >>> based approach to requesting an Oauth2 token. I see this being >>> done in OAuth2WebFragmentFetchAutorization#doAuthorization >>> method, where an OAuthWebViewDialog is used to trigger the >>> Oauth2 token request. >>> >>> To use Google Play services to trigger an Oauth2 token request, >>> we won't use an http approach, but rather we start an activity >>> to select an account and request an Oauth2 token. Once the >>> token is retrieved it can then be used with the standard http >>> Oauth2 API. >>> >>> (One caveat: the google play services token response doesn't >>> provide a refresh token. I believe this to be a non-issue as >>> the token request process is trivial when using google play >>> services (no authentication step)). >>> >>> I see to ways to implement this feature: >>> >>> 1) Generalize the OAuth2WebFragmentFetchAutorization into an >>> interface, and have one implementation to handle http-based >>> token requests, and second implementation to handle intent-based >>> token requests. >>> >>> 2) Add a OAuth2AuthorizationConfiguration option to use intents >>> instead of http, and trigger a different workflow within the >>> OAuth2WebFragmentFetchAutorization#doAuthorization method if >>> that config is set. >>> >>> My preference is for 2) because it's a) simpler, and b) it is >>> really only during the #doAuthorization method that we have a >>> different approach. >>> >>> Thoughts? I'll start with implementing approach (2) unless I >>> hear otherwise. >>> >>> Brian >>> >>> >>> On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: >>>> >>>> >>>> On Wednesday, February 25, 2015, Daniel Passos >>>> > wrote: >>>> >>>> No, we are not using Google Play services API for now for >>>> OAuth2 in Android land. >>>> >>>> But feel free create a new AuthzModule[1] for it ;) >>>> >>>> >>>> +1 >>>> >>>> >>>> >>>> [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >>>> >>>> -- Passos >>>> >>>> >>>> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >>>> wrote: >>>> >>>> Cool stuff Brian ! >>>> The AeroGear OAuth2 Cordova plugin relies on the Native >>>> AeroGear OAuth2 Libraries, so maybe Summers and/or >>>> Daniel could tell more about it. >>>> Sebi >>>> >>>> >>>> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >>>> wrote: >>>> >>>> Hey gear-heads, >>>> >>>> I recently wrote a Cordova plugin that retrieves a >>>> Oauth2 token on >>>> Android using Google Play Services. The advantage >>>> of this approach is >>>> it leverages the single-sign-on capabilities of >>>> android, and the app can >>>> retrieve the Oauth2 token without requiring >>>> Authentication from the >>>> user. I blogged about it here: >>>> >>>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>>> >>>> Using a promise-based API it's fairly trivial to >>>> fallback to a >>>> traditional Web authentication/authorisation for >>>> the Oauth2 token when >>>> the google-play-services approach isn't supported. >>>> >>>> I'm aware the aerogear team has a Oauth2 cordova >>>> plugin [1], but it's >>>> not clear to me if the google-play-services >>>> integration is supported. >>>> If the Aerogeam would find it useful, I'd be more >>>> than happy to provide >>>> a PR to the aerogear cordova plugin providing such >>>> integration. >>>> >>>> Thoughts? >>>> Brian >>>> >>>> [1] >>>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > 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/20150225/4d952a3b/attachment-0001.html From bleathem at gmail.com Wed Feb 25 19:35:18 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 16:35:18 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> Message-ID: <54EE6A46.2070203@gmail.com> Hello all, So I've gotten pretty close in my implementation, but I've got one blocker: The account selection and Oath2 token request are initiated using an intent. The result is then retrieved by implementing the #onActivityResult method of the initial activity. The problem I'm facing is the original activity exists in the user's application. Nesting activities isn't a solution, as I still don't have access to the top-level activity. Implementing this purely as a cordova plugin is trivial, as I can just @Override the #onActivityResult of the CordovaPlugin class. Do any Android experts have a recommendation on how I can implement this as a generic Android library in android-authz? Alternatively if we implement this directly in the oauth2-codova plugin I have everything we need already complete. Brian On 2015-02-25 10:44 AM, Daniel Passos wrote: > > Hey Brian, > > You can. but not necessarily need do that.. You can create your own > workflow. > > Just implement your own: > > * > > OAuth2AuthroizationConfigurationProvider > > * > > AuthorizationConfiguration > > * AuthzModule.java > > And let the |AuthorizationManager| know[1] your new Authz > > |AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) > | > > [1] > https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 > > -- Passos > > > ? > > On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem > wrote: > > ... and the devil is in the details. > > It seems as though all the current AuzthzModules use an http based > approach to requesting an Oauth2 token. I see this being done in > OAuth2WebFragmentFetchAutorization#doAuthorization method, where > an OAuthWebViewDialog is used to trigger the Oauth2 token request. > > To use Google Play services to trigger an Oauth2 token request, we > won't use an http approach, but rather we start an activity to > select an account and request an Oauth2 token. Once the token is > retrieved it can then be used with the standard http Oauth2 API. > > (One caveat: the google play services token response doesn't > provide a refresh token. I believe this to be a non-issue as the > token request process is trivial when using google play services > (no authentication step)). > > I see to ways to implement this feature: > > 1) Generalize the OAuth2WebFragmentFetchAutorization into an > interface, and have one implementation to handle http-based token > requests, and second implementation to handle intent-based token > requests. > > 2) Add a OAuth2AuthorizationConfiguration option to use intents > instead of http, and trigger a different workflow within the > OAuth2WebFragmentFetchAutorization#doAuthorization method if that > config is set. > > My preference is for 2) because it's a) simpler, and b) it is > really only during the #doAuthorization method that we have a > different approach. > > Thoughts? I'll start with implementing approach (2) unless I hear > otherwise. > > Brian > > > On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: >> >> >> On Wednesday, February 25, 2015, Daniel Passos > > wrote: >> >> No, we are not using Google Play services API for now for >> OAuth2 in Android land. >> >> But feel free create a new AuthzModule[1] for it ;) >> >> >> +1 >> >> >> >> [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >> >> -- Passos >> >> >> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >> wrote: >> >> Cool stuff Brian ! >> The AeroGear OAuth2 Cordova plugin relies on the Native >> AeroGear OAuth2 Libraries, so maybe Summers and/or >> Daniel could tell more about it. >> Sebi >> >> >> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >> wrote: >> >> Hey gear-heads, >> >> I recently wrote a Cordova plugin that retrieves a >> Oauth2 token on >> Android using Google Play Services. The advantage of >> this approach is >> it leverages the single-sign-on capabilities of >> android, and the app can >> retrieve the Oauth2 token without requiring >> Authentication from the >> user. I blogged about it here: >> >> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >> >> Using a promise-based API it's fairly trivial to >> fallback to a >> traditional Web authentication/authorisation for the >> Oauth2 token when >> the google-play-services approach isn't supported. >> >> I'm aware the aerogear team has a Oauth2 cordova >> plugin [1], but it's >> not clear to me if the google-play-services >> integration is supported. >> If the Aerogeam would find it useful, I'd be more >> than happy to provide >> a PR to the aerogear cordova plugin providing such >> integration. >> >> Thoughts? >> Brian >> >> [1] >> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Sent from Gmail Mobile >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/1372d01d/attachment.html From bleathem at gmail.com Thu Feb 26 02:13:56 2015 From: bleathem at gmail.com (Brian Leathem) Date: Wed, 25 Feb 2015 23:13:56 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EE6A46.2070203@gmail.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE6A46.2070203@gmail.com> Message-ID: One way to make this work would be to move the Aerogear Oauth2 API altogether to an intent based one. Users would start an intent to retrieve an Oauth2 token, which we would deliver to their #onActivityResult method, regardless of the mechanism we use. This would also allow us to resolve AGDROID-319 elegantly. Hello all, So I've gotten pretty close in my implementation, but I've got one blocker: The account selection and Oath2 token request are initiated using an intent. The result is then retrieved by implementing the #onActivityResult method of the initial activity. The problem I'm facing is the original activity exists in the user's application. Nesting activities isn't a solution, as I still don't have access to the top-level activity. Implementing this purely as a cordova plugin is trivial, as I can just @Override the #onActivityResult of the CordovaPlugin class. Do any Android experts have a recommendation on how I can implement this as a generic Android library in android-authz? Alternatively if we implement this directly in the oauth2-codova plugin I have everything we need already complete. Brian On 2015-02-25 10:44 AM, Daniel Passos wrote: Hey Brian, You can. but not necessarily need do that.. You can create your own workflow. Just implement your own: - OAuth2AuthroizationConfigurationProvider - AuthorizationConfiguration - AuthzModule.java And let the AuthorizationManager know[1] your new Authz AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) [1] https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 -- Passos ? On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem wrote: > ... and the devil is in the details. > > It seems as though all the current AuzthzModules use an http based > approach to requesting an Oauth2 token. I see this being done in > OAuth2WebFragmentFetchAutorization#doAuthorization method, where an > OAuthWebViewDialog is used to trigger the Oauth2 token request. > > To use Google Play services to trigger an Oauth2 token request, we won't > use an http approach, but rather we start an activity to select an account > and request an Oauth2 token. Once the token is retrieved it can then be > used with the standard http Oauth2 API. > > (One caveat: the google play services token response doesn't provide a > refresh token. I believe this to be a non-issue as the token request > process is trivial when using google play services (no authentication > step)). > > I see to ways to implement this feature: > > 1) Generalize the OAuth2WebFragmentFetchAutorization into an interface, > and have one implementation to handle http-based token requests, and second > implementation to handle intent-based token requests. > > 2) Add a OAuth2AuthorizationConfiguration option to use intents instead of > http, and trigger a different workflow within the > OAuth2WebFragmentFetchAutorization#doAuthorization method if that config is > set. > > My preference is for 2) because it's a) simpler, and b) it is really only > during the #doAuthorization method that we have a different approach. > > Thoughts? I'll start with implementing approach (2) unless I hear > otherwise. > > Brian > > > On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: > > > > On Wednesday, February 25, 2015, Daniel Passos wrote: > >> No, we are not using Google Play services API for now for OAuth2 in >> Android land. >> >> But feel free create a new AuthzModule[1] for it ;) >> > > +1 > > >> >> [1] >> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >> >> -- Passos >> >> >> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >> wrote: >> >>> Cool stuff Brian ! >>> The AeroGear OAuth2 Cordova plugin relies on the Native AeroGear OAuth2 >>> Libraries, so maybe Summers and/or Daniel could tell more about it. >>> Sebi >>> >>> >>> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >>> wrote: >>> >>>> Hey gear-heads, >>>> >>>> I recently wrote a Cordova plugin that retrieves a Oauth2 token on >>>> Android using Google Play Services. The advantage of this approach is >>>> it leverages the single-sign-on capabilities of android, and the app can >>>> retrieve the Oauth2 token without requiring Authentication from the >>>> user. I blogged about it here: >>>> >>>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>>> >>>> Using a promise-based API it's fairly trivial to fallback to a >>>> traditional Web authentication/authorisation for the Oauth2 token when >>>> the google-play-services approach isn't supported. >>>> >>>> I'm aware the aerogear team has a Oauth2 cordova plugin [1], but it's >>>> not clear to me if the google-play-services integration is supported. >>>> If the Aerogeam would find it useful, I'd be more than happy to provide >>>> a PR to the aerogear cordova plugin providing such integration. >>>> >>>> Thoughts? >>>> Brian >>>> >>>> [1] >>>> >>>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > Sent from Gmail Mobile > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150225/4f50b2bf/attachment-0001.html From matzew at apache.org Thu Feb 26 03:44:03 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 26 Feb 2015 09:44:03 +0100 Subject: [aerogear-dev] Outdated repos on aerogear GH org ? Message-ID: Hello, when assisting Lukas with the project info template, I found a few repos, where I am not sure if we really need them anymore. what do you think, could we just delete these repos? * https://github.com/aerogear/aerogear-android-integration-tests * https://github.com/aerogear/aerogear-ios-integration * https://github.com/aerogear/aerogear-jaxrs-demo * https://github.com/aerogear/jdf-stack * https://github.com/aerogear/aerogear-haml * https://github.com/aerogear/aerogear-forge-scaffold For this one I am not sure if it is needed or not. My feeling is this could be just moved inside the cookbooks and delete the repos afterwards. * https://github.com/aerogear/aerogear-crypto-android-demo Here are two repos that I'd like to add a deprecation note on it. I am not sure we should remove them, now. * https://github.com/aerogear/aerogear-controller * https://github.com/aerogear/aerogear-security-picketbox Let me know what you think about them! Thanks a lot -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/20150226/a2d8b8e4/attachment.html From daniel.bevenius at gmail.com Thu Feb 26 03:56:09 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 26 Feb 2015 09:56:09 +0100 Subject: [aerogear-dev] Outdated repos on aerogear GH org ? In-Reply-To: References: Message-ID: +1 On adding a deprection notice to https://github.com/aerogear/aerogear-controller On 26 February 2015 at 09:44, Matthias Wessendorf wrote: > Hello, > > when assisting Lukas with the project info template, I found a few repos, > where I am not sure if we really need them anymore. > > what do you think, could we just delete these repos? > * https://github.com/aerogear/aerogear-android-integration-tests > * https://github.com/aerogear/aerogear-ios-integration > * https://github.com/aerogear/aerogear-jaxrs-demo > * https://github.com/aerogear/jdf-stack > * https://github.com/aerogear/aerogear-haml > * https://github.com/aerogear/aerogear-forge-scaffold > > For this one I am not sure if it is needed or not. My feeling is this > could be just moved inside the cookbooks and delete the repos afterwards. > * https://github.com/aerogear/aerogear-crypto-android-demo > > > Here are two repos that I'd like to add a deprecation note on it. I am not > sure we should remove them, now. > * https://github.com/aerogear/aerogear-controller > * https://github.com/aerogear/aerogear-security-picketbox > > > Let me know what you think about them! > > Thanks a lot > -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/20150226/66303e9a/attachment.html From daniel at passos.me Thu Feb 26 07:45:32 2015 From: daniel at passos.me (Daniel Passos) Date: Thu, 26 Feb 2015 09:45:32 -0300 Subject: [aerogear-dev] Outdated repos on aerogear GH org ? In-Reply-To: References: Message-ID: On Thu, Feb 26, 2015 at 5:44 AM, Matthias Wessendorf wrote: > Hello, > > when assisting Lukas with the project info template, I found a few repos, > where I am not sure if we really need them anymore. > > what do you think, could we just delete these repos? > * https://github.com/aerogear/aerogear-android-integration-tests > +1 > * https://github.com/aerogear/aerogear-ios-integration > * https://github.com/aerogear/aerogear-jaxrs-demo > * https://github.com/aerogear/jdf-stack > * https://github.com/aerogear/aerogear-haml > * https://github.com/aerogear/aerogear-forge-scaffold > > For this one I am not sure if it is needed or not. My feeling is this > could be just moved inside the cookbooks and delete the repos afterwards. > * https://github.com/aerogear/aerogear-crypto-android-demo > +1 Already moved => https://github.com/aerogear/aerogear-android-cookbook/pull/47 I'll also move the OTP demo soon => https://issues.jboss.org/browse/AGDROID-383 Here are two repos that I'd like to add a deprecation note on it. I am not > sure we should remove them, now. > * https://github.com/aerogear/aerogear-controller > * https://github.com/aerogear/aerogear-security-picketbox > > > Let me know what you think about them! > > Thanks a lot > -Matthias > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150226/1b341793/attachment.html From bruno at abstractj.org Thu Feb 26 07:58:42 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 26 Feb 2015 04:58:42 -0800 (PST) Subject: [aerogear-dev] Outdated repos on aerogear GH org ? In-Reply-To: References: Message-ID: <1424955521748.f92eb6c5@Nodemailer> Go ahead! ? abstractj PGP: 0x84DC9914 On Thu, Feb 26, 2015 at 5:44 AM, Matthias Wessendorf wrote: > Hello, > when assisting Lukas with the project info template, I found a few repos, > where I am not sure if we really need them anymore. > what do you think, could we just delete these repos? > * https://github.com/aerogear/aerogear-android-integration-tests > * https://github.com/aerogear/aerogear-ios-integration > * https://github.com/aerogear/aerogear-jaxrs-demo > * https://github.com/aerogear/jdf-stack > * https://github.com/aerogear/aerogear-haml > * https://github.com/aerogear/aerogear-forge-scaffold > For this one I am not sure if it is needed or not. My feeling is this could > be just moved inside the cookbooks and delete the repos afterwards. > * https://github.com/aerogear/aerogear-crypto-android-demo > Here are two repos that I'd like to add a deprecation note on it. I am not > sure we should remove them, now. > * https://github.com/aerogear/aerogear-controller > * https://github.com/aerogear/aerogear-security-picketbox > Let me know what you think about them! > Thanks a lot > -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/20150226/e5101882/attachment.html From supittma at redhat.com Thu Feb 26 10:13:13 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 26 Feb 2015 10:13:13 -0500 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE6A46.2070203@gmail.com> Message-ID: <54EF3809.4040104@redhat.com> On 02/26/2015 02:13 AM, Brian Leathem wrote: > > One way to make this work would be to move the Aerogear Oauth2 API > altogether to an intent based one. Users would start an intent to > retrieve an Oauth2 token, which we would deliver to their > #onActivityResult method, regardless of the mechanism we use. > > This would also allow us to resolve AGDROID-319 elegantly. > Yup. I made 319 while trying to do what you are currently doing. I really, really, REALLY wish Google hadn't made Android a class and had gone for an injection/composition programming model instead. It's like they weren't even paying any attention to academic and professional literature about OO and Java in 2006... > Hello all, > > So I've gotten pretty close in my implementation, but I've got one > blocker: > > The account selection and Oath2 token request are initiated using an > intent. The result is then retrieved by implementing the > #onActivityResult method of the initial activity. The problem I'm > facing is the original activity exists in the user's application. > Nesting activities isn't a solution, as I still don't have access to > the top-level activity. > > Implementing this purely as a cordova plugin is trivial, as I can just > @Override the #onActivityResult of the CordovaPlugin class. > > Do any Android experts have a recommendation on how I can implement > this as a generic Android library in android-authz? > > Alternatively if we implement this directly in the oauth2-codova > plugin I have everything we need already complete. > > Brian > > On 2015-02-25 10:44 AM, Daniel Passos wrote: >> >> Hey Brian, >> >> You can. but not necessarily need do that.. You can create your own >> workflow. >> >> Just implement your own: >> >> * >> >> OAuth2AuthroizationConfigurationProvider >> >> * >> >> AuthorizationConfiguration >> >> * AuthzModule.java >> >> And let the |AuthorizationManager| know[1] your new Authz >> >> |AuthorizationManager.registerConfigurationProvider(YourNewAuthorizationConfiguration, new YourNewOAuth2AuthroizationConfigurationProvider) >> | >> >> [1] >> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthorizationManager.java#L37-L41 >> >> -- Passos >> >> >> ? >> >> On Wed, Feb 25, 2015 at 3:30 PM, Brian Leathem > > wrote: >> >> ... and the devil is in the details. >> >> It seems as though all the current AuzthzModules use an http >> based approach to requesting an Oauth2 token. I see this being >> done in OAuth2WebFragmentFetchAutorization#doAuthorization >> method, where an OAuthWebViewDialog is used to trigger the Oauth2 >> token request. >> >> To use Google Play services to trigger an Oauth2 token request, >> we won't use an http approach, but rather we start an activity to >> select an account and request an Oauth2 token. Once the token is >> retrieved it can then be used with the standard http Oauth2 API. >> >> (One caveat: the google play services token response doesn't >> provide a refresh token. I believe this to be a non-issue as the >> token request process is trivial when using google play services >> (no authentication step)). >> >> I see to ways to implement this feature: >> >> 1) Generalize the OAuth2WebFragmentFetchAutorization into an >> interface, and have one implementation to handle http-based token >> requests, and second implementation to handle intent-based token >> requests. >> >> 2) Add a OAuth2AuthorizationConfiguration option to use intents >> instead of http, and trigger a different workflow within the >> OAuth2WebFragmentFetchAutorization#doAuthorization method if that >> config is set. >> >> My preference is for 2) because it's a) simpler, and b) it is >> really only during the #doAuthorization method that we have a >> different approach. >> >> Thoughts? I'll start with implementing approach (2) unless I >> hear otherwise. >> >> Brian >> >> >> On 2015-02-24 07:25 PM, Matthias Wessendorf wrote: >>> >>> >>> On Wednesday, February 25, 2015, Daniel Passos >> > wrote: >>> >>> No, we are not using Google Play services API for now for >>> OAuth2 in Android land. >>> >>> But feel free create a new AuthzModule[1] for it ;) >>> >>> >>> +1 >>> >>> >>> [1] >>> https://github.com/aerogear/aerogear-android-authz/blob/master/aerogear-android-authz/src/main/java/org/jboss/aerogear/android/authorization/AuthzModule.java >>> >>> -- Passos >>> >>> >>> On Tue, Feb 24, 2015 at 4:01 PM, Sebastien Blanc >>> wrote: >>> >>> Cool stuff Brian ! >>> The AeroGear OAuth2 Cordova plugin relies on the Native >>> AeroGear OAuth2 Libraries, so maybe Summers and/or >>> Daniel could tell more about it. >>> Sebi >>> >>> On Tue, Feb 24, 2015 at 7:46 PM, Brian Leathem >>> wrote: >>> >>> Hey gear-heads, >>> >>> I recently wrote a Cordova plugin that retrieves a >>> Oauth2 token on >>> Android using Google Play Services. The advantage >>> of this approach is >>> it leverages the single-sign-on capabilities of >>> android, and the app can >>> retrieve the Oauth2 token without requiring >>> Authentication from the >>> user. I blogged about it here: >>> >>> http://www.bleathem.ca/blog/2015/02/cordova-oauth-google-services.html >>> >>> Using a promise-based API it's fairly trivial to >>> fallback to a >>> traditional Web authentication/authorisation for the >>> Oauth2 token when >>> the google-play-services approach isn't supported. >>> >>> I'm aware the aerogear team has a Oauth2 cordova >>> plugin [1], but it's >>> not clear to me if the google-play-services >>> integration is supported. >>> If the Aerogeam would find it useful, I'd be more >>> than happy to provide >>> a PR to the aerogear cordova plugin providing such >>> integration. >>> >>> Thoughts? >>> Brian >>> >>> [1] >>> http://staging-aerogearsite.rhcloud.com/docs/specs/aerogear-cordova/OAuth2.html >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- 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/20150226/ca101b21/attachment-0001.html From supittma at redhat.com Thu Feb 26 10:17:37 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 26 Feb 2015 10:17:37 -0500 Subject: [aerogear-dev] Outdated repos on aerogear GH org ? In-Reply-To: References: Message-ID: <54EF3911.2060408@redhat.com> On 02/26/2015 07:45 AM, Daniel Passos wrote: > > > On Thu, Feb 26, 2015 at 5:44 AM, Matthias Wessendorf > > wrote: > > Hello, > > when assisting Lukas with the project info template, I found a few > repos, where I am not sure if we really need them anymore. > > what do you think, could we just delete these repos? > * https://github.com/aerogear/aerogear-android-integration-tests > > > +1 +1 to passos +1 > > * https://github.com/aerogear/aerogear-ios-integration > * https://github.com/aerogear/aerogear-jaxrs-demo > * https://github.com/aerogear/jdf-stack > * https://github.com/aerogear/aerogear-haml > * https://github.com/aerogear/aerogear-forge-scaffold > > For this one I am not sure if it is needed or not. My feeling is > this could be just moved inside the cookbooks and delete the repos > afterwards. > * https://github.com/aerogear/aerogear-crypto-android-demo > > > +1 Already moved => > https://github.com/aerogear/aerogear-android-cookbook/pull/47 > I'll also move the OTP demo soon => > https://issues.jboss.org/browse/AGDROID-383 > > Here are two repos that I'd like to add a deprecation note on it. > I am not sure we should remove them, now. > * https://github.com/aerogear/aerogear-controller > * https://github.com/aerogear/aerogear-security-picketbox > > > Let me know what you think about them! > > Thanks a lot > -Matthias > > > > _______________________________________________ > 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/20150226/eb5b914e/attachment.html From scm.blanc at gmail.com Thu Feb 26 10:24:05 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 26 Feb 2015 16:24:05 +0100 Subject: [aerogear-dev] master branch - maven install - error In-Reply-To: References: Message-ID: so FYI I just switch to Windows to do some WNS testing and I'm having the same issue as you when building :/ , that random factor make it really annoying ... On Mon, Feb 23, 2015 at 3:05 PM, Matthias Wessendorf wrote: > npm :-) > > On Mon, Feb 23, 2015 at 2:54 PM, Ivan G?rtler > wrote: > >> after download alpha1 version and mvn instal ... everything OK ... I >> downloaded master again .... and after import master and mvn install >> everthing is OK ... it was strange ... >> >> Thanks for your help >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-02-23 14:43 GMT+01:00 Sebastien Blanc : >> >>> I can build master under Windows 8.1, I did not have the issue. Really >>> strange and annoying issue. >>> >>> >>> On Mon, Feb 23, 2015 at 2:35 PM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> yes :D win 8.1 ... but when I downloaded lower version (alpha1) source >>>> code ... mvn install is ok ... >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> 2015-02-23 14:18 GMT+01:00 Matthias Wessendorf : >>>> >>>>> Oh, windows - I see ... >>>>> >>>>> On Mon, Feb 23, 2015 at 2:18 PM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Mon, Feb 23, 2015 at 2:06 PM, Ivan G?rtler < >>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>> >>>>>>> I try it 10 times :-D ... but always with error >>>>>>> >>>>>> >>>>>> lol - sorry to hear. >>>>>> >>>>>> what operating system are you on ? >>>>>> >>>>>> >>>>>>> >>>>>>> *Mgr. Ivan G?rtler* >>>>>>> Mobile software developer >>>>>>> >>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>> 602 00 Brno (Czech Republic) >>>>>>> >>>>>>> www.ahead-itec.com | twitter | >>>>>>> mobile security solutions >>>>>>> >>>>>>> 2015-02-23 13:54 GMT+01:00 Matthias Wessendorf : >>>>>>> >>>>>>>> the node/npm thing fails randomly for me as well. try running the >>>>>>>> mvn build again ;-( >>>>>>>> >>>>>>>> >>>>>>>> On Monday, February 23, 2015, Ivan G?rtler < >>>>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I downloaded zip from ... >>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server ... >>>>>>>>> import as maven project ... >>>>>>>>> but I am facing some problem ... when I run maven install... >>>>>>>>> >>>>>>>>> [INFO] >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> [INFO] Building UnifiedPush Server (Admin UI) >>>>>>>>> 1.1.0-alpha.2-SNAPSHOT >>>>>>>>> [INFO] >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>>>>> (enforce-java-version) @ unifiedpush-admin-ui --- >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce >>>>>>>>> (enforce-maven-version) @ unifiedpush-admin-ui --- >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-tools) @ >>>>>>>>> unifiedpush-admin-ui --- >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp >>>>>>>>> (get-build-timestamp) @ unifiedpush-admin-ui --- >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) >>>>>>>>> @ unifiedpush-admin-ui --- >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:install-node-and-npm >>>>>>>>> (install node and npm) @ unifiedpush-admin-ui --- >>>>>>>>> [INFO] Node v0.10.31 is already installed. >>>>>>>>> [INFO] Found NPM version 1.4.23 >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ >>>>>>>>> unifiedpush-admin-ui --- >>>>>>>>> [INFO] Running 'npm install --color=false' in >>>>>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>>>>> [INFO] npm WARN unmet dependency C:\Users\Ivan\Documents\Aerogear >>>>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui\node_modules\grunt-bower-task\node_modules\bower\node_modules\request\node_modules\form-data >>>>>>>>> requires mime@'~1.2.11' but will load >>>>>>>>> [INFO] npm WARN unmet dependency undefined, >>>>>>>>> [INFO] npm WARN unmet dependency which is version undefined >>>>>>>>> [INFO] >>>>>>>>> [INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ >>>>>>>>> unifiedpush-admin-ui --- >>>>>>>>> [INFO] Running 'grunt dist --no-color' in >>>>>>>>> C:\Users\Ivan\Documents\Aerogear >>>>>>>>> projects\aerogear-unifiedpush-server-master\admin-ui >>>>>>>>> [INFO] Loading "bower_task.js" tasks...ERROR >>>>>>>>> [INFO] >> Error: Cannot find module 'mime' >>>>>>>>> [INFO] >> Local Npm module "grunt-cli" not found. Is it installed? >>>>>>>>> [INFO] Warning: Task "bower:install" not found. Use --force to >>>>>>>>> continue. >>>>>>>>> [INFO] >>>>>>>>> [INFO] Aborted due to warnings. >>>>>>>>> [INFO] >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> [INFO] Reactor Summary: >>>>>>>>> [INFO] >>>>>>>>> [INFO] AeroGear UnifiedPush Server ........................ >>>>>>>>> SUCCESS [ 2.020 s] >>>>>>>>> [INFO] UnifiedPush Model Layer ............................ >>>>>>>>> SUCCESS [ 0.077 s] >>>>>>>>> [INFO] UnifiedPush Server Model API ....................... >>>>>>>>> SUCCESS [ 2.958 s] >>>>>>>>> [INFO] UnifiedPush Server Model JPA implementation ........ >>>>>>>>> SUCCESS [ 12.992 s] >>>>>>>>> [INFO] UnifiedPush Service Layer .......................... >>>>>>>>> SUCCESS [ 17.831 s] >>>>>>>>> [INFO] UnifiedPush Sender Module .......................... >>>>>>>>> SUCCESS [ 0.066 s] >>>>>>>>> [INFO] UnifiedPush Push Message Model ..................... >>>>>>>>> SUCCESS [ 2.369 s] >>>>>>>>> [INFO] UnifiedPush Push Notification Networks ............. >>>>>>>>> SUCCESS [ 3.585 s] >>>>>>>>> [INFO] UnifiedPush RESTful Endpoint ....................... >>>>>>>>> SUCCESS [ 5.240 s] >>>>>>>>> [INFO] UnifiedPush Server (Admin UI) ...................... >>>>>>>>> FAILURE [ 4.898 s] >>>>>>>>> [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: 53.305 s >>>>>>>>> [INFO] Finished at: 2015-02-23T13:01:24+01:00 >>>>>>>>> [INFO] Final Memory: 98M/635M >>>>>>>>> [INFO] >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> [ERROR] Failed to execute goal >>>>>>>>> com.github.eirslett:frontend-maven-plugin:0.0.16:grunt (grunt build) on >>>>>>>>> project unifiedpush-admin-ui: Failed to run task: 'grunt dist --no-color' >>>>>>>>> failed. (error code 3) -> [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/MojoFailureException >>>>>>>>> [ERROR] >>>>>>>>> [ERROR] After correcting the problems, you can resume the build >>>>>>>>> with the command >>>>>>>>> [ERROR] mvn -rf :unifiedpush-admin-ui >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks for help >>>>>>>>> >>>>>>>>> *Mgr. Ivan G?rtler* >>>>>>>>> Mobile software developer >>>>>>>>> >>>>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>>>> 602 00 Brno (Czech Republic) >>>>>>>>> >>>>>>>>> www.ahead-itec.com | twitter | >>>>>>>>> mobile security solutions >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20150226/77a37e69/attachment-0001.html From bleathem at gmail.com Thu Feb 26 10:58:15 2015 From: bleathem at gmail.com (Brian Leathem) Date: Thu, 26 Feb 2015 07:58:15 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EF3809.4040104@redhat.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE6A46.2070203@gmail.com> <54EF3809.4040104@redhat.com> Message-ID: <54EF4297.3080503@gmail.com> On 2015-02-26 07:13 AM, Summers Pittman wrote: > I really, really, REALLY wish Google hadn't made Android a class and > had gone for an injection/composition programming model instead. It's > like they weren't even paying any attention to academic and > professional literature about OO and Java in 2006... Agreed - it's a severe limitation indeed. In terms of landing the google-play-services oauth2-token request feature I am trying to implement, I see a number of paths forward: 1) Rewrite the Aeroegear Oauth2 API altogether to be intenet based, providing users the token via the #onActivityResult method. This would mostly just be adding a layer in front of the existing API, and shouldn't be too honerous. It would however be a breaking change for downstream applications. 2) Leave the google-play-services request out of android-authz (Android users can initiate the play-services intent themselves if they want). Instead I would implement this feature only in the oauth2-codova plugin where I can receive the intent response. 3) Explore using an Android Service to handle Oauth2 token requests. I believe we would be able to trigger an intent and retrieve the result from within the service, then provide it to the downstream application from the service. It's a little unclear as to whether starting intents from a Service is good practice. My vote would be to pursue 2) for now, with a note about 1) being added to AGDROID-319 to be treated in a future revision. Thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150226/d22ebefa/attachment.html From scm.blanc at gmail.com Thu Feb 26 12:57:15 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 26 Feb 2015 18:57:15 +0100 Subject: [aerogear-dev] Outdated repos on aerogear GH org ? In-Reply-To: References: Message-ID: On Thu, Feb 26, 2015 at 9:44 AM, Matthias Wessendorf wrote: > Hello, > > when assisting Lukas with the project info template, I found a few repos, > where I am not sure if we really need them anymore. > > what do you think, could we just delete these repos? > * https://github.com/aerogear/aerogear-android-integration-tests > * https://github.com/aerogear/aerogear-ios-integration > * https://github.com/aerogear/aerogear-jaxrs-demo > * https://github.com/aerogear/jdf-stack > * https://github.com/aerogear/aerogear-haml > * https://github.com/aerogear/aerogear-forge-scaffold > +1 , this one can be deleted > > For this one I am not sure if it is needed or not. My feeling is this > could be just moved inside the cookbooks and delete the repos afterwards. > * https://github.com/aerogear/aerogear-crypto-android-demo > > > Here are two repos that I'd like to add a deprecation note on it. I am not > sure we should remove them, now. > * https://github.com/aerogear/aerogear-controller > * https://github.com/aerogear/aerogear-security-picketbox > > > Let me know what you think about them! > > Thanks a lot > -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/20150226/35f6cb17/attachment.html From supittma at redhat.com Thu Feb 26 14:23:30 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 26 Feb 2015 14:23:30 -0500 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EF4297.3080503@gmail.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE6A46.2070203@gmail.com> <54EF3809.4040104@redhat.com> <54EF4297.3080503@gmail.com> Message-ID: <54EF72B2.2090602@redhat.com> On 02/26/2015 10:58 AM, Brian Leathem wrote: > On 2015-02-26 07:13 AM, Summers Pittman wrote: >> I really, really, REALLY wish Google hadn't made Android a class and >> had gone for an injection/composition programming model instead. >> It's like they weren't even paying any attention to academic and >> professional literature about OO and Java in 2006... > > Agreed - it's a severe limitation indeed. > > In terms of landing the google-play-services oauth2-token request > feature I am trying to implement, I see a number of paths forward: > > 1) Rewrite the Aeroegear Oauth2 API altogether to be intenet based, > providing users the token via the #onActivityResult method. This > would mostly just be adding a layer in front of the existing API, and > shouldn't be too honerous. It would however be a breaking change for > downstream applications. > > 2) Leave the google-play-services request out of android-authz > (Android users can initiate the play-services intent themselves if > they want). Instead I would implement this feature only in the > oauth2-codova plugin where I can receive the intent response. > > 3) Explore using an Android Service to handle Oauth2 token requests. > I believe we would be able to trigger an intent and retrieve the > result from within the service, then provide it to the downstream > application from the service. It's a little unclear as to whether > starting intents from a Service is good practice. > > My vote would be to pursue 2) for now, with a note about 1) being > added to AGDROID-319 to be treated in a future revision. I agree. For 1 we should leave the old implementation as an option. Not having your activity die during log in is a good feature and the dialog is the easiest way I can think of it and it keeps it from being a breaking change. > > Thoughts? -- 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/20150226/8439790c/attachment.html From lholmqui at redhat.com Thu Feb 26 20:07:31 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Thu, 26 Feb 2015 20:07:31 -0500 Subject: [aerogear-dev] Outdated repos on aerogear GH org ? In-Reply-To: References: Message-ID: <1F9ACBED-7F07-4CEA-8A4B-CE7B25456690@redhat.com> what about this one: https://github.com/aerogear/aerogear-otp-js i think that can be deprecated/deleted. I don?t think this makes sense anymore? this one also, https://github.com/aerogear/kitchensink-aerogear-js > On Feb 26, 2015, at 3:44 AM, Matthias Wessendorf wrote: > > Hello, > > when assisting Lukas with the project info template, I found a few repos, where I am not sure if we really need them anymore. > > what do you think, could we just delete these repos? > * https://github.com/aerogear/aerogear-android-integration-tests > * https://github.com/aerogear/aerogear-ios-integration > * https://github.com/aerogear/aerogear-jaxrs-demo > * https://github.com/aerogear/jdf-stack > * https://github.com/aerogear/aerogear-haml > * https://github.com/aerogear/aerogear-forge-scaffold > > For this one I am not sure if it is needed or not. My feeling is this could be just moved inside the cookbooks and delete the repos afterwards. > * https://github.com/aerogear/aerogear-crypto-android-demo > > > Here are two repos that I'd like to add a deprecation note on it. I am not sure we should remove them, now. > * https://github.com/aerogear/aerogear-controller > * https://github.com/aerogear/aerogear-security-picketbox > > > Let me know what you think about them! > > Thanks a lot > -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/20150226/bdfff8ed/attachment.html From bleathem at gmail.com Thu Feb 26 23:13:14 2015 From: bleathem at gmail.com (Brian Leathem) Date: Thu, 26 Feb 2015 20:13:14 -0800 Subject: [aerogear-dev] Cordova Ouath2 plugin using Google Play Services In-Reply-To: <54EF72B2.2090602@redhat.com> References: <54ECC70A.8040100@gmail.com> <54EE14C7.8090007@gmail.com> <54EE6A46.2070203@gmail.com> <54EF3809.4040104@redhat.com> <54EF4297.3080503@gmail.com> <54EF72B2.2090602@redhat.com> Message-ID: <54EFEEDA.7030502@gmail.com> Hello all, I've created a PR adding google-play-services oauth2 token requests to the aerogear-oauth2-cordova plugin: https://github.com/aerogear/aerogear-oauth2-cordova/pull/11 Feedback appreciated. Brian On 2015-02-26 11:23 AM, Summers Pittman wrote: > On 02/26/2015 10:58 AM, Brian Leathem wrote: >> On 2015-02-26 07:13 AM, Summers Pittman wrote: >>> I really, really, REALLY wish Google hadn't made Android a class and >>> had gone for an injection/composition programming model instead. >>> It's like they weren't even paying any attention to academic and >>> professional literature about OO and Java in 2006... >> >> Agreed - it's a severe limitation indeed. >> >> In terms of landing the google-play-services oauth2-token request >> feature I am trying to implement, I see a number of paths forward: >> >> 1) Rewrite the Aeroegear Oauth2 API altogether to be intenet based, >> providing users the token via the #onActivityResult method. This >> would mostly just be adding a layer in front of the existing API, and >> shouldn't be too honerous. It would however be a breaking change for >> downstream applications. >> >> 2) Leave the google-play-services request out of android-authz >> (Android users can initiate the play-services intent themselves if >> they want). Instead I would implement this feature only in the >> oauth2-codova plugin where I can receive the intent response. >> >> 3) Explore using an Android Service to handle Oauth2 token requests. >> I believe we would be able to trigger an intent and retrieve the >> result from within the service, then provide it to the downstream >> application from the service. It's a little unclear as to whether >> starting intents from a Service is good practice. >> >> My vote would be to pursue 2) for now, with a note about 1) being >> added to AGDROID-319 to be treated in a future revision. > I agree. For 1 we should leave the old implementation as an option. > Not having your activity die during log in is a good feature and the > dialog is the easiest way I can think of it and it keeps it from being > a breaking change. >> >> Thoughts? > > > -- > 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/20150226/d988e3d5/attachment-0001.html From edewit at redhat.com Fri Feb 27 04:54:03 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 27 Feb 2015 10:54:03 +0100 Subject: [aerogear-dev] Cordova plugin release Message-ID: Hi, After finding a critical bug in the oauth2 1.0.2 release we?ve release 1.0.3 today to fix it AGCORDOVA-69 The plugin gives compilation errors on gradle build Sorry for the inconvenience and thanks to everyone that helped with testing Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/c33b3c88/attachment.html From daniel.bevenius at gmail.com Fri Feb 27 05:17:57 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 27 Feb 2015 11:17:57 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150302 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/2c7f74a7/attachment.html From daniel at passos.me Fri Feb 27 05:39:54 2015 From: daniel at passos.me (Daniel Passos) Date: Fri, 27 Feb 2015 07:39:54 -0300 Subject: [aerogear-dev] Cordova plugin release In-Reply-To: References: Message-ID: +1 On Fri, Feb 27, 2015 at 6:54 AM, Erik Jan de Wit wrote: > Hi, > > After finding a critical bug in the oauth2 1.0.2 release we?ve release > 1.0.3 today to fix it > > [image: Bug] AGCORDOVA-69 The > plugin gives compilation errors on gradle build > > Sorry for the inconvenience and thanks to everyone that helped with testing > > 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/20150227/50d69fef/attachment.html From ivan.gurtler at ahead-itec.com Fri Feb 27 07:25:22 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 27 Feb 2015 13:25:22 +0100 Subject: [aerogear-dev] loging with slf4j + logback Message-ID: Hi, we replaced default logging with logback and slf4j ... we found this issue https://issues.jboss.org/browse/AGPUSH-1086 and if you would also like to use our logging approach it is possible to create pull request ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/42338464/attachment.html From scm.blanc at gmail.com Fri Feb 27 07:36:29 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 27 Feb 2015 13:36:29 +0100 Subject: [aerogear-dev] loging with slf4j + logback In-Reply-To: References: Message-ID: Hi Ivan ! Sure you can provide a pull request :) Thanks again for your commitment. Sebi On Fri, Feb 27, 2015 at 1:25 PM, Ivan G?rtler wrote: > Hi, > > we replaced default logging with logback and slf4j ... we found this issue > https://issues.jboss.org/browse/AGPUSH-1086 and if you would also like to > use our logging approach it is possible to create pull request ... > > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/08b8b926/attachment.html From matzew at apache.org Fri Feb 27 08:08:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 27 Feb 2015 14:08:25 +0100 Subject: [aerogear-dev] loging with slf4j + logback In-Reply-To: References: Message-ID: +1 a pr would be really nice :-)) On Friday, February 27, 2015, Sebastien Blanc wrote: > Hi Ivan ! > > Sure you can provide a pull request :) > > Thanks again for your commitment. > > Sebi > > > On Fri, Feb 27, 2015 at 1:25 PM, Ivan G?rtler > wrote: > >> Hi, >> >> we replaced default logging with logback and slf4j ... we found this >> issue https://issues.jboss.org/browse/AGPUSH-1086 and if you would also >> like to use our logging approach it is possible to create pull request ... >> >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/ded52960/attachment.html From lholmqui at redhat.com Fri Feb 27 08:42:24 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Fri, 27 Feb 2015 08:42:24 -0500 (EST) Subject: [aerogear-dev] AeroGear JS 2.1.0 In-Reply-To: <295158829.17175089.1425044141567.JavaMail.zimbra@redhat.com> Message-ID: <808768674.17181150.1425044544073.JavaMail.zimbra@redhat.com> Hello All, I had planned a release for the AeroGear.js library(2.1.0) next week, but i might push it back a week. This release is mostly about the work we have been doing regarding the client libraries for the Sync Server, https://github.com/aerogear/aerogear-sync-server. The reason for the push back is i want to refactor the code slightly to not use the "Array Pattern"(for lack of a better word) that it currently uses, this was also discussed in general for the whole library here: http://lists.jboss.org/pipermail/aerogear-dev/2015-February/010894.html even those this api is experimental and is ok to change without a major release, i would like to start it using the new pattern than we discussed in the above linked thread. -Luke From scm.blanc at gmail.com Fri Feb 27 08:59:31 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 27 Feb 2015 14:59:31 +0100 Subject: [aerogear-dev] AeroGear's Google+ Page Message-ID: Hi ! While clicking through the website I landed on our Google+ Page : https://plus.google.com/106588661437153585722/about It's pretty empty and outdated, what should we do about it ? We could gather there all our screencasts maybe ? Or just close it. wdyt ? Sebi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/6cdc60f3/attachment-0001.html From bruno at abstractj.org Fri Feb 27 09:49:08 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 27 Feb 2015 11:49:08 -0300 Subject: [aerogear-dev] Heads-up about the deliverables of AGSEC 1.4.1 Message-ID: <20150227144908.GA47315@abstractj.org> Good morning, the deliverables of AGSEC 1.4.1 were programmed for today, but will be delayed in 1 week. The reason is the fact that I'm still work in some items. The overall documentation will be released and coordinated with the release of our new website. Thanks for understanding. -- abstractj PGP: 0x84DC9914 From matzew at apache.org Fri Feb 27 10:11:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 27 Feb 2015 16:11:19 +0100 Subject: [aerogear-dev] AeroGear's Google+ Page In-Reply-To: References: Message-ID: screencasts, sounds good On Friday, February 27, 2015, Sebastien Blanc wrote: > Hi ! > While clicking through the website I landed on our Google+ Page : > https://plus.google.com/106588661437153585722/about > > It's pretty empty and outdated, what should we do about it ? We could > gather there all our screencasts maybe ? Or just close it. > > wdyt ? > > Sebi > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/a6603a4e/attachment.html From ivan.gurtler at ahead-itec.com Fri Feb 27 10:14:45 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 27 Feb 2015 16:14:45 +0100 Subject: [aerogear-dev] loging with slf4j + logback In-Reply-To: References: Message-ID: ok i try PR ... https://github.com/aerogear/aerogear-unifiedpush-server/pull/507 ... tested on EAP 6.3 ... (wildfly not tested ... sorry) *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-02-27 14:08 GMT+01:00 Matthias Wessendorf : > +1 a pr would be really nice :-)) > > > On Friday, February 27, 2015, Sebastien Blanc wrote: > >> Hi Ivan ! >> >> Sure you can provide a pull request :) >> >> Thanks again for your commitment. >> >> Sebi >> >> >> On Fri, Feb 27, 2015 at 1:25 PM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> Hi, >>> >>> we replaced default logging with logback and slf4j ... we found this >>> issue https://issues.jboss.org/browse/AGPUSH-1086 and if you would also >>> like to use our logging approach it is possible to create pull request ... >>> >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> _______________________________________________ >>> 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/20150227/6d4c1588/attachment.html From lukas.fryc at gmail.com Fri Feb 27 11:25:53 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 27 Feb 2015 17:25:53 +0100 Subject: [aerogear-dev] AeroGear JS 2.1.0 In-Reply-To: <808768674.17181150.1425044544073.JavaMail.zimbra@redhat.com> References: <295158829.17175089.1425044141567.JavaMail.zimbra@redhat.com> <808768674.17181150.1425044544073.JavaMail.zimbra@redhat.com> Message-ID: +1 sounds good I will probably finish my Ionic demo and release a blog to accompany that release. :-) On Fri, Feb 27, 2015 at 2:42 PM, Luke Holmquist wrote: > Hello All, > > I had planned a release for the AeroGear.js library(2.1.0) next week, but > i might push it back a week. > > This release is mostly about the work we have been doing regarding the > client libraries for the Sync Server, > https://github.com/aerogear/aerogear-sync-server. > > > The reason for the push back is i want to refactor the code slightly to > not use the "Array Pattern"(for lack of a better word) that it currently > uses, this was also discussed in general for the whole library here: > http://lists.jboss.org/pipermail/aerogear-dev/2015-February/010894.html > > even those this api is experimental and is ok to change without a major > release, i would like to start it using the new pattern than we discussed > in the above linked thread. > > > > > > -Luke > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150227/8cb3c335/attachment.html From supittma at redhat.com Sat Feb 28 09:01:15 2015 From: supittma at redhat.com (Summers Pittman) Date: Sat, 28 Feb 2015 09:01:15 -0500 Subject: [aerogear-dev] AeroGear's Google+ Page In-Reply-To: References: Message-ID: <54F1CA2B.9020406@redhat.com> On 02/27/2015 10:11 AM, Matthias Wessendorf wrote: > screencasts, sounds good If someone gives me the bits I'll update it. At the very least I can bang all of our twitter and mailing list demos together from the last few weeks and make a regularly updating stream o crap. > > On Friday, February 27, 2015, Sebastien Blanc > wrote: > > Hi ! > While clicking through the website I landed on our Google+ Page : > https://plus.google.com/106588661437153585722/about > > It's pretty empty and outdated, what should we do about it ? We > could gather there all our screencasts maybe ? Or just close it. > > wdyt ? > > Sebi > > > > -- > Sent from Gmail Mobile > > > _______________________________________________ > 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/20150228/6f6a0830/attachment.html From bruno at abstractj.org Sat Feb 28 19:27:04 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Sat, 28 Feb 2015 16:27:04 -0800 (PST) Subject: [aerogear-dev] AeroGear's Google+ Page In-Reply-To: <54F1CA2B.9020406@redhat.com> References: <54F1CA2B.9020406@redhat.com> Message-ID: <1425169623225.0a635697@Nodemailer> Why not? Get the keys of the gates and go ahead ? abstractj PGP: 0x84DC9914 On Sat, Feb 28, 2015 at 11:01 AM, Summers Pittman wrote: > On 02/27/2015 10:11 AM, Matthias Wessendorf wrote: >> screencasts, sounds good > If someone gives me the bits I'll update it. At the very least I can > bang all of our twitter and mailing list demos together from the last > few weeks and make a regularly updating stream o crap. >> >> On Friday, February 27, 2015, Sebastien Blanc > > wrote: >> >> Hi ! >> While clicking through the website I landed on our Google+ Page : >> https://plus.google.com/106588661437153585722/about >> >> It's pretty empty and outdated, what should we do about it ? We >> could gather there all our screencasts maybe ? Or just close it. >> >> wdyt ? >> >> Sebi >> >> >> >> -- >> Sent from Gmail Mobile >> >> >> _______________________________________________ >> 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/20150228/c90291d5/attachment-0001.html