AeroGear.org
by Bruno Oliveira
Good morning peeps, I’m planning to push to production the latest changes on aerogear.org tomorrow. Any problems?
--
abstractj
11 years, 6 months
OpenShift cartridge: UPS Part (was Re: Staging of UnifiedPush Server 0.10.1)
by Matthias Wessendorf
Hello,
after staging the release bits, I also updated our OpenShift cartridge:
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/comm...
I created a fork and merged the bits into my master (for an easier testing):
https://github.com/matzew/openshift-origin-cartridge-aerogear-push
For testing the 0.10.1 version our our cartridge, simply execute the
following command:
rhc app create --no-git <YOUR APP NAME>
https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshif...
Greetings,
Matthias
On Tue, Mar 11, 2014 at 3:36 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
> Hello,
>
> for the upcoming release we have a few, but important, tickets solved:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188
>
>
> Before finishing the release, let's see if there are issues w/ the server,
> hence I have staged the WAR file on my private webspace:
>
>
>
> http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unif...
>
>
> If they aren't any objections or remarks I will release the bits to
> bintray on Friday morning
>
>
> Greetings,
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
11 years, 6 months
Release process
by Matthias Wessendorf
Hello,
for the Java bits we do have a solid release process ([1]). The main
benefit is we stage the artifacts on a repo and give the community a
heads-up for testing. Based on this vote we release (or may not release).
This is a great way to engage the entire community to double check and give
feedback. The release process is a shared thing inside of the community.
For the other bits we currently do not have a similar process (my feeling).
I'd actually prefer if we establish something like that on all the other
platforms as well. This gives the community a chance to test the bits
before we push them to the repos.
IMO, if we start 'silently' release bits to the actual repositories it's
kinda bypassing the community's feedback on a particular release candiate.
Sure all the projects have tests, but manual testing, by the community is
IMO a very positive thing
-Matthias
[1] https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
11 years, 7 months
iOS Passphrases for UPS
by Bruno Oliveira
Good morning guys, for this issue https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole UPS code and thinking about include two fields for iOSVariant class: skey (secret key) and pKey (public key). What’s the idea?
1. Each application has its own key pair
2. Before the addition of the iOS variant, the client sends a request asking for the public keys
3. The server sends an HTTP response with the public key for encryption
4. The client make use of the public key to encrypt the certificate + the passphrase
5. Server stores it encrypted
6. When necessary to send push messages, the server make use of the private key to decrypt that data and send fancy messages.
Does it make sense to you?
--
abstractj
JBoss, a division of Red Hat
11 years, 7 months
Do AeroGear UnifiedPushServer can be installed on JBOSS 5/6 ?
by malliq9
Hi,
I am installed the AeroGear UnifiedPushServer version 0.80 on JBOSS 7.1
Final, it is working fine. But as I want to use JBOSS 5.1 GA for cluster
setup and want AeroGear UFPS to be installed on JBOSS 5.1 GA, where I am
getting below error. I am thinking this is due to incompatability with the
JBOSS Server.
Appreciate any answer/work around for my query
Showing below trace in log
------------------------------------------------------------------------
vfszip:/D:/SNG/Softwares/jboss-5.1.0.GA_ORIGINAL/server/default/deploy/aerogear-unifiedpush-server.war/
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at
org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at
org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at
org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source:
Failed to resolve schema nsURI=http://java.sun.com/xml/ns/javaee
location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at
org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
at
org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
at
org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
at
org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
at
org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
at
org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)
... 33 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve
schema nsURI=http://java.sun.com/xml/ns/javaee
location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd
at
org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:281)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 41 more
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Do-AeroGear-UnifiedPushServer-c...
Sent from the aerogear-dev mailing list archive at Nabble.com.
11 years, 7 months
Unified Push Server in Wildfly 8 final installation registration issue
by JChrist
Hello everyone,
I have deployed the Unified push server (latest version, from master branch)
on wildfly 8 final. Everything seems to be normal,
except than when an app makes a registration (an android app installation),
there is the following exception thrown:
WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed
executing POST /registry/device:
org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find
MessageBodyWriter for response object of type:
org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type:
application/octet-stream
Is this something known, or should I report it to JIRA?
Thanks!
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-...
Sent from the aerogear-dev mailing list archive at Nabble.com.
11 years, 7 months
iOS Push registration lib / iOS 7
by Christos Vasilakis
Hi all,
currently the push-ios registration lib relies on AFNetworking branch 1.x for its networking stack. In the process of updating to iOS 7, the plan was to update it also to use the AFNetworking 2.x series that is optimised for iOS 7.
I am thinking though if it makes sense, at this point, to remove the AFNet dependency and go with just plain iOS 7 NSURLSession API for the networking. I think, It will make easier for developers to integrate it in their own projects, without having to another dependency which may or may not use as their networking stack.
Wdyth?
-
Christos
11 years, 7 months
toc
by Erik Jan de Wit
Hi,
As you may know I’ve created a example of how the toc could look like on our new site, the problem is with mobile we don’t have enough room to have a toc there as well. We could just remove the toc or we could have something like this:
This is a drop down that shows the same information as the original toc and also behaves that way. I’m not a designer, but I think this would make a very nice solution.
Here is a screen shot of how the toc would look on a desktop:
What do you think?
Cheers,
Erik Jan
11 years, 7 months
AeroGear project structure and the website
by Hylke Bons
Hey everyone,
So we've been doing continuous improvements to the website. Corinne and
Erik have been making some awesome progress shaping up the new
documentation section (roadmap here:
http://aerogear.org/docs/planning/roadmaps/AeroGearWebSite/) according
to the mockups
(https://raw2.github.com/hbons/aerogear-design/master/website-restructure/...).
We've split stuff up into "Setup Howtos", "Examples", "API
Documentation" and "Guides". I don't think there was much controversy
here and there's been made some headway already in unifying some of the
documentation.
The most important change in the website mockups was that instead of
focusing on platform branding, the focus is on solving use cases that
"we happen to support on these platforms". So Core/Push/Security are the
main players over iOS/Android/JS, although these are still referenced
everywhere and presented in a graphic on top of the home page.
Before we can work on the project homepage sections and download areas
of the website we should have a discussion about how the AeroGear
project itself is structured. The project seems to have grown
organically and new modules have been added here and there. There are
some of these that make the structure of the project more complicated
that it needs to be (in my opinion) to present it in a simple way to
developers visiting the website.
I've done some research on the project structure and have written down
the findings, as well as points where there's room for improvement and
possible solutions, here: http://oksoclap.com/p/AeroGearModuleUntangling
TL;DR: The most important questions that we need to answer are these:
- "If I download a library on one platform, what must I download to use
the same features on an other platform?"
-"Is this a part I use on the client, or on the server side?"
-"What do we mean when talking about different AeroGear
subprojects/modules?"
One solution might be:
https://raw2.github.com/hbons/aerogear-design/master/website-restructure/...
I've made a lot of assumptions here, and it might not work, but I'd like
to hear your thoughts on it.
It would clarify a lot if we could harmonise the different downloads
across platforms, either by providing single download solutions or
splitting everything up and naming all the parts consistently. I'm
interested in what the technical issues might be, as I wasn't around
when most of these decisions were made, or I simply missed them.
Thoughts or other ideas? :)
Thanks,
Hylke
11 years, 7 months
