Updated Sender API
by Lucas Holmquist
i know the api specs on the website haven't been updated yet, but i'm trying to update the node sender client and i'm not seeing how to send a simple push "message" without specifying "simple-push" as an Object.
basically the first example doesn't seem to work for simplePush anymore
I'm not sure if this was overlooked when updating the UPS?
//No criteria, just a normal send( what use to be broadcast )
{
message: {
alert: "...",
sound: "...",
badge: "...",
"simple-push": "version=123"
}
}
//With Criteria
{
variants: [..., ...],
deviceType: [..., ...]
message: {
alert: "...",
sound: "...",
badge: "...",
"simple-push": "version=123"
},
"simple-push": {
"someCategory": "...."
}
}
10 years, 6 months
Release of Java Sender Client 0.2.2
by Sebastien Blanc
Hi !
Java Sender Client 0.2.2 has been staged :
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
Changelog :
*Add javadoc comments in ValidationUtils
af3b321dc2
*Remove unnecessary imports
0b3960dff7
*Add validation utils
704a9d8d9a
*Fix selectedPayloadObject category
1de991a99e
*Add some more validation
a21f0074c2
*Adding check for redirect response code and perform the redirect if n… …
fe5f82a780
*Adding jsse.enableSNIExtension workaround notice, for Java7 clients
af26584fa9
*name and links update
309a1d4d94
*Fixing typo...
957335616c
regards,
Seb
10 years, 6 months
How we failed to collect code coverage results with Groovy
by Karel Piwko
Hi All,
here are the details of the story:
We have some unit tests written in Java and integration tests written in
Groovy. We collect results using Jacaco in "appending" mode. That means we are
able to run unit tests with instrumented code and integration tests with
instrumented AS JVM. Then we can merge results together or not, depends on what
we want.
So, where are the problems with Groovy compiler? Simply, it generates a
different bytecode than Javac. So, when running integration tests, we are
constructing microdeployments, that contain classes or archives, deploy them to
AS, using what's available on classpath or in Maven repositories (or, Maven
Reactor for multimodule projects). And we actually need those classes to be
compiled by the *same* compiler all the time so jacoco can match results.
So, what are the options?
1/ Use groovyc to compile all the code we need to instrument. However, that
means that we would need to change remote repository to a proxy repository where
binaries are build via groovy and rebuild all aerogear with groovy before code
coverage gathering happens. I did that for the first round of CC results, and
it was simply a too much mess to cope with despite the fact that I skipped
workaround for Maven and thus I got I bit underestimate results.
2/ Use javac everywhere. So, we need to remove groovy.
3/ Use groovyc to compile only tests. This unfortunately does not work, as
maven-compiler-plugin ignores includes/excludes. Tadeas can provide
upstream issue #. Moreover, it takes *years* to get something fixed in Maven.
4/ Migrate to Gradle, where include/exclude might work correctly
So, the option is 2/.
Karel
10 years, 6 months
Query on Aergear-Android Applications
by Anand Kumar
Good morning Aerogear team,
I am trying to integrate with my android application with Aerogear-Unified
push server.But i failed to get the result in it.Could you please help me
to resolve this problem???
Regards
Anand.K
10 years, 6 months
