AeroGear.js
by Lucas Holmquist
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 <https://github.com/orgs/AeroGear-Components/dashboard>
I think i've started to ramble, so i'll stop here and look for comments
9 years, 1 month
deployment problem - master branch
by Ivan Gürtler
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 <https://www.twitter.com/AHEADiTec> | mobile
security solutions
9 years, 1 month
Release: New parent staged (was: Re: parent release ?)
by Matthias Wessendorf
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_st...
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 <matzew(a)apache.org>
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
9 years, 1 month
Aerogear Unifiedpush with oracle DB ... longer parameters problems
by Ivan Gürtler
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 <https://www.twitter.com/AHEADiTec> | mobile
security solutions
9 years, 1 month
UPS bug - am I crazy?
by Douglas Campos
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(a)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/mo...
[2]:https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/mo...
--
qmx
9 years, 1 month
