AeroGear Controller 1.0.2 staged
by Bruno Oliveira
Good morning peeps,
Just to let you know AG Controller 1.0.2 was staged.
- Changelog
* Preparing to release AeroGear Controller 1.0.2
* Merge branch 'charset'
* Added JUnit test to verify ParameterExtractor.extractArguments
handles content-types with charset definitions properly
* Made ParameterExtractor ignore charset information when looking for
a Consumer
I would like to thank Tobias Getrost for these changes.
- Instructions to test it
* Add this repository to your settings.xml:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
Ex: https://gist.github.com/abstractj/b8359b1b824ff8dfcf0c
* Raise your hand! Most part of the time abstractj wait 2 days or 3 for
feedback and press the button, so if you are testing it, please let me
know.
--
abstractj
10 years, 9 months
Security Policy on AeroGear
by Bruno Oliveira
Good morning peeps.
I had some conversation with Matthias about the encourage the usage of
SSL into Unified Push server, after some minutes thinking would be
better if we could make it no only for AGPUSH.
So here is the whole and simple idea:
- Include a Security Policy on AeroGear site.
Ex: http://emberjs.com/security/ or http://www.ovirt.org/Security (David
Jorm pointed me out for that)
I already got in touch with security response team from Red Hat
- Create an alias security(a)aerogear.org which redirects to our incident
response team on Red Hat
- Make things crystal clear into our projects via SECURITY.md file
Ex: https://github.com/andyet/andbang.js/blob/master/SECURITY.md
And also include recommendations to make use of SSL with HSTS.
Once it affects the whole project, your feedback is welcome.
--
abstractj
10 years, 9 months
Unified Push on OpenShift
by Daniel Passos
We have AeroDoc (backend) and Unified Push Server deployed on OpenShift?
--
Daniel Passos
10 years, 9 months
Android Push Tutorial
by Tommy McCarthy
Hello again, everyone!
I recently pushed some more changes to the Android Push Tutorial to my Github. It is viewable at
https://github.com/tmccarthy9/aerogear.org/tree/master/docs/guides/aeroge...
I incorporated some styling and formatting changes that were suggested, and added a new page about setting up Eclipse with the application projects. I also added information about using an emulator and how to set that up with the Google APIs. Finally, I added some instructions how to configure an actual physical device to be able to have the application(s) pushed directly on the device.
One thing to note is that I created it based off of the "PushEEDemo" application, which is now incompatible with the latest version of aerogear-android. Specifically, (as I'm sure many of you know) the "unifiedpush" package is now gone, which the PushEEDemo required for it's Registrar, and PushConfig. The PushEEDemo will need to be updated in order to use the tutorial without modifying the code.
I look forward to any more feedback or suggestions!
---
Tommy McCarthy
10 years, 9 months
my experience with aerogear-android push
by Marc Sluiter
Hi all,
I'm a Java and Android developer from Germany, Münster area. Matze pointed me to
the aerogear-android framework and unified push, so I was curious and wanted to
give it a try.
Until it worked I had some little issues, which I want to share, maybe it helps
to improve documentation, and I was not sure if I should just start a pull
request about it...
I started with forking and cloning aerogear-android,
aerogear-unified-push-server and PushEEDemo to my local development environment.
For aerogear-android I followed the instructions on github and on
http://aerogear.org/docs/guides/GetStartedAndroidIntellij/.
Worked nice, I even didn't have to uncomment the extra modules for the
maven-android-sdk-deployer, after updating all libs in the Android SDK Manager
it just worked.
The problem with "Could not find tool 'aapt'" was solved by updating the
android-maven-plugin to version 3.6, so also no need to create a link to it. But
then it was missing the platform version, so my pom looks like this now:
<plugin>
<groupId>com.jayway.maven.plugins.android.generation2</groupId>
<artifactId>android-maven-plugin</artifactId>
<version>3.6.0</version>
<configuration>
<sdk>
<platform>17</platform>
</sdk>
<undeployBeforeDeploy>true</undeployBeforeDeploy>
</configuration>
<extensions>true</extensions>
</plugin>
I also had to increase the version number of the support lib:
<dependency>
<groupId>android.support</groupId>
<artifactId>compatibility-v4</artifactId>
<version>13</version>
</dependency>
Finally I had to add 2 lines in proguard.cfg in order to let maven build
successfully:
-dontwarn android.support.**
-dontwarn com.google.android.gms.**
The aerogear-unified-push-server did run out of the box. But when I followed the
instructions on http://aerogear.org/docs/specs/aerogear-server-push/, I always
got something like "Authorization failed" when trying to register a push
application. I found on the github page that I have to login and use cookies
with the curl requests, with that it worked.
But then I got auth errors when the PushEEDemo app tried to register on the
unified push server. Finally I got the hint from Matze to use the
"quickstart-base" branch of the server, which skips authorization. With that I
successfully sent a notification to my Nexus 4 :) Maybe it would useful to point
to that branch in the docs.
Last but not least I wanted to test it on an older device with Android 2.3.7.,
for that I had to change the manifest of the PushEEDemo app. I already started a
pull request about it (since it does not seem to be an official aerogear repo ;)
): https://github.com/secondsun/PushEEDemo/pull/1. With that changes it worked, too.
When I have some time, I will have a look into the other features of Aerogear
too, interesting project :)
Thx for reading this far & greetings,
Marc
@slintes
10 years, 9 months
"application/json; charset=utf-8" not supported
by Corinne Krych
Hello Guys
Writing code for ProDoctor demo, on client side, I'm using Xcode template
for AGPush which is based on AFNetworking 121
When doing my login request in iOS I bumped into the issue of having
content type set to "application/json; charset=utf-8" whereas on routes
(backend) only "application/json" is set which causes this exception:
[application/json].': java.lang.RuntimeException: AG_CONTROLLER000012: No
Consumer found for Parameter: 'Parameter[type=ENTITY, type=class
org.aerogear.prodoctor.model.SaleAgent]'. The registered Consumers were:
'[JsonConsumer[mediaType=application/json]]'. Please add a Consumer for one
the media types supported by the route: [application/json].
at
org.jboss.aerogear.controller.util.ParameterExtractor.getConsumer(ParameterExtractor.java:152)
[aerogear-controller-1.0.1.jar:1.0.1]
at
org.jboss.aerogear.controller.util.ParameterExtractor.extractArguments(ParameterExtractor.java:70)
[aerogear-controller-1.0.1.jar:1.0.1]
I think we should support both "application/json; charset=utf-8" and
"application/json". /shall we open a JIRA on AeroGear Controller to
support both?
wdyt?
Corinne
10 years, 9 months
[aerogear-unified-push-server] Problem with ProdCerts branch iOS variant addition
by Yavuz Selim YILMAZ
Hi all,
I'm trying out the ProdCerts branch on aerogear-unified-push-server to enable AeroGear powered push notifications on my production iOS application.
When I am trying to add an iOS variant, I am getting:
HTTP/1.1 400 Bad Request
…
The request sent by the client was syntactically incorrect ().
…
The curl command I am using is here:
$curl -i -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: multipart/form-data" -F "developmentCertificate=(a)/Users/yavuz/Documents/Certificates.p12" -F "developmentPassphrase=pass" -X POST http://localhost:8080/ag-push/rest/applications/8055d0a9-ed30-463c-9ac3-b...
As far as I could see, Bad Request is returned if developmentCertificate and/or developmentPassphrase is null (in my case, productionCertificate/Passphrase are already null). Therefore, in order to make sure my Certificates.p12 does not read null , I switched to master branch, and executed the following command successfully and add my variant:
$curl -i -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: multipart/form-data" -F "certificate=(a)/Users/yavuz/Documents/Certificates.p12" -F "passphrase=pass" -X POST http://localhost:8080/ag-push/rest/applications/688d0fe1-4cc2-4606-ab10-0...
Any ideas why I might be getting this error, or any suggestions/directions are most appreciated.
Kind regards,
---
Yavuz Selim Yilmaz
SUNY at Buffalo
Computer Science and Engineering
PhD Candidate
10 years, 9 months
[Java Sender API] future of AsyncHttpClient
by Sebastien Blanc
Hi Folks !
As you know the current Java Sender API comes today with 2 different
implementations :
- Resteasy client (used by default)
- AsyncHttpClient
I discussed a bit with Matzew and we agreed that we should probably remove
the AsyncHttpClient implementation and just keep the resteasy client, wdyt
?
Seb
10 years, 9 months
