June 2016 - Aerogear-users - Jboss List Archives

UnifiedPush Node sender move to Promises

by Luke Holmquist

Hello people, I think i would like to move the unifiedpush-node-sender, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client , to be Promise based. Currently it uses callback pattern that many node.js packages use as well as emitting events. When i first created this 3 years ago, that was sort of the standard way of doing things, but Promises have become very popular(i know i love them :)) and have been a native feature since node 0.12.x considering we have not yet hit a 1.0.0, we can pretty much just make this change and we will be ok. If this is to big of a change all at once, we could always do both callbacks and Promises. I think we did this for Datamanager in the past. Perhaps once we fully move to promises, then we can hit a 1.0.0 My only concern is other projects that might be using the sender that are not yet on node 0.12 or above, since this is when promises became native. I would really like to not have to include the polyfill. i suppose those users would need to stick to the previous versions then. anyway, would like to hear some thoughts. -Luke

8 years, 5 months

2
4
0 / 0

Jackson Dependency Conflict with Aerogear 1.1.0

by Jonathon Rogoff

I have been successfully using Aerogear 1.0.0 in my product for a while now. I am making some additions (primarily using contentAvailable to prompt apps I haven't heard from lately to check in once in a while) and thought it would be a opportunity to upgrade to 1.1.0. I upgraded the Aerogear server as well as my Android and iOS apps without any problems. However, my jboss web server, used by administrators to initiate messages, is proving problematic. After upgrading the unifiedpush-java-client to 1.1.0.Final on my jboss web server, I cannot get it to play nicely with the resteasy-jackson2-provider implementation (3.0.16.Final) I use for custom RESTful communication between my apps and the web server. It appears that including the unifiedpush-java-client 1.1.0 causes my RESTful services to use the codehaus jackson implementation in the unifiedpush-java-client. Therefore, all of my fasterxml jackson annotations (@JsonIgnore and @JsonFormat) are ignored causing my RESTful services to fail. If I exclude both jackson-jaxrs and jackson-databind from the unifiedpush-java-client in my pom.xml then everything compiles and my RESTful services work. However, when attempting to send a push notification from the server I get a "java.lang.NoClassDefFoundError: org/codehaus/jackson/map/ObjectMapper" from UnifiedPushMessage for obvious reasons. I tried going back to the 1.0.0 version of the unifiedpush-java-client, but that just results in status code 400 responses from the aerogear 1.1.0 server. Do you have any suggestions for resolving this conflict, or should I just roll everything back to the 1.0.0 version until further notice? I appreciate any direction you can provide. - Jonathon Rogoff

8 years, 5 months

1
0
0 / 0

Device registration - Method not allowed

by Philipp Koetz, mVISE AG

Hello, we have encountered a problem while registering Android devices against the unified push server. Apple devices are not affected and can register successfull. We are using org.jboss.aerogear:aerogear-android-push:2.2.1 as client lib. Could you also provide a Deeplink which we can manually test the device registration? 2016-05-25 13:20:15,193 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-29) failed to execute: javax.ws.rs.NotAllowedException: No resource method found for GET, return 405 with Allow header at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:375) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:114) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.10.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at org.jboss.aerogear.unifiedpush.rest.util.VersionFilter.doFilter(VersionFilter.java:65) [unifiedpush-jaxrs-1.1.3.Final.jar:1.1.3.Final] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at org.jboss.aerogear.unifiedpush.service.filter.HttpContextFilter.doFilter(HttpContextFilter.java:55) [unifiedpush-service-1.1.3.Final.jar:1.1.3.Final] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_72-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_72-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72-internal]

8 years, 5 months

3
11
0 / 0

UPS Device Registration Endpoints

by Luke Holmquist

thats right folks, i'm asking this question on a Friday before a Holiday weekend(US) at 3:52(est) i've started to implement the Device registration endpoints in node and was just wondering what the id is here in this header -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid" is it something specific, or just a random number/alpha-numeric thingy here is the doc link for reference: https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932 I've also decided to create this as a separate module instead of including it in the node admin client here: https://github.com/bucharest-gold/unifiedpush-admin-client mostly becuase these registration endpoints don't needed to be KC authenticated. and they could also be used on a IOT device or something that runs node that has webpush/simplePush or some new crazy protocol. -Luke

8 years, 5 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Aerogear-users June 2016