Cordova Push Plugin Release
by Erik Jan de Wit
Hi,
We are going to release a new version of the cordova push plugin the new version 1.0.2 a new feature is support for external configuration. Now instead of using code you can store the variantId and secrets into a separate json file. With more platforms support coming this will not `pollute` your code anymore. Check out the 1.0.x branch to give it a spin.
Here are the release notes:
Bug
[AGCORDOVA-36] - Make Push Plugin work again with Android < 4.4
Feature Request
[AGCORDOVA-34] - externalise Push config
9 years, 6 months
OAuth2, OpenID connect and AeroGear
by Bruno Oliveira
Good morning,
Today we had a meeting to discuss some of the priorities for security on
AeroGear[1]. One of the items is OAuth2 support. Currently we have
several great examples and implementations for GDrive, flows for
Keycloak and etc.
Although is a bit confuse for developers getting started from scratch.
I would like to keep our libaries aligned, considering the limitations
of each technology of course, as well consolidate each flow[2].
Also the team agreed that OpenID connect (with Facebook and Google) should be considered a low
priority at the moment. That said I have some open questions:
- Should we provide separated SDKs for OAuth2? Or let's put everything
into *-auth and break into modules later?
Note: Not only for Keycloak, but also compatible with other technologies
like passport on Node.js. In the end, OAuth2 is just a protocol and
should support other servers.
- Should we provide examples for OpenID connect? Or abstractions?
To track this issue, we have the following Jira[3] and another for
OpenID connect[4]. Fell free to link to your respective project.
[1] -
http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...
[2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
[3] - https://issues.jboss.org/browse/AGSEC-180
[4] - https://issues.jboss.org/browse/AGSEC-190
--
abstractj
PGP: 0x84DC9914
9 years, 6 months
[UPS] Proposal to change the Push Message Format
by Sebastien Blanc
Hi,
I was looking at our current Push Message Format[1] and I was wonderimg if
you should not add some more structure to it, decoupling config, criterias
and the message itself :
{
"config" : {
"ttl" : 3600,
"content-available" : true,
"simple-push": "version=123"
},
"criteria" : {
"alias" : ["user(a)account.com", "someone(a)aerogear.org", ....],
"categories" : ["someCategory", "otherCategory"],
"deviceType" : ["iPad", "AndroidTablet"],
"variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e",
"444939cd-ae63-4ce1-96a4-de74b77e3737"]
}
,
"message": {
"alert":"HELLO!",
"sound":"default",
"badge":7,
"someKey":"some value",
"anotherCustomKey":"some other value"
},
}
wdyt ?
Sebi
[1]http://aerogear.org/docs/specs/aerogear-push-messages/
9 years, 6 months
notification alert and app launched displays the alert
by chansdad
Hello
I am testing aerogear for a project of mine . Able to send alerts .
Here are couple of questions
1. Can I send alerts based on a deviceId?
2. alerts is visible in the notifications panel in android . when i select
the alert , it takes me to the app . and when the app is active displays the
alert dialog on top of the app . can i disable this? when the app is not
active , alert is not displayed on the app screen.
3. Can i customize the alert as it displays on the screen.
4. Does aerogear support rich media notifications to be displayed on
homescreen. If not is there a plan to add this feature?
Thanks and to be honest , aerogear makes it super simple to send out
notifications .I still need to figure out if i can send messages by
deviceId as that is my key requirement.
Regards
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/notification-alert-and-app-laun...
Sent from the aerogear-dev mailing list archive at Nabble.com.
9 years, 6 months
Java8 on master? (was: Re: [UPS] A thought: On MASTER only support WildFly?)
by Matthias Wessendorf
While at it :), as a follow-up thought on that, I am wondering if, on
MASTER, we should look into making it Java8?
-Matthias
On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
> Hello,
>
> as said in the other email thread earlier this week ([1]) there is a bug
> in the last JBoss AS 7.1 release (see [2]), that basically means the server
> works properly only on EAP6.x and WildFly.
>
> Because of that, I am wondering about removing the -as7 module (see [3]),
> on our MASTER branch. For the 1.0.x branch, I'd like to keep it, for EAP
> usage reasons.
>
> What do you guys think?
>
> -Matthias
>
> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
> [2] https://issues.jboss.org/browse/AS7-4694
> [3]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/serve...
>
>
> --
> 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, 6 months
General Android Updates
by Summers Pittman
Last week was a big week.
* Merged last PR from out "Alpha" list
* Android L released
* Maven Android Plugin 4.0-rc.1 migration begun
* Deprecates apklib
* Introduces new project layout
* Travis builds on multiple JDKs now.
We continued work on sync and started work on Shoot and Share. This led
to the discovery of some issues with the module system and Gradle. The
aar builds produced by our current build system don't handle
dependencies correctly. This problem doesn't seem to exist in the
4.0-rc.1 plugin. Also the 4.0 project structure is compatible with the
Gradle project structure which *SHOULD* make interacting with Android
Studio better.
This week we are tackling several big issues/tasks at once.
* Updating all of the Travis builds to use multi-JDK
* Updating all of the projects to MAP 4.0-rc.1
* Updating all of the projects to API level 21.
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
9 years, 6 months
Upgrade from 0.10.2
by JChrist
Hello everyone.
I am currently using the Aerogear Unified Push Server v 0.10.2 and have
already gathered a number of installations on one application variant (an
iOS app).
I was thinking about upgrading to the latest version (the v1.0.x series) and
I would greatly appreciate if you could point out an upgrade plan (if such
exists), so as to not lose the existing installations.
Kind regards
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Upgrade-from-0-10-2-tp9545.html
Sent from the aerogear-dev mailing list archive at Nabble.com.
9 years, 6 months
Problems to setup UPS
by Daniel Passos
Hey Guys,
Today I’ve spend a lot of time (without success), trying test #408
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/408> using a
new JBoss AS 7.1/Wildfly 8.1.0 installations
Using Java version “1.7.0_45”
------------------------------
JBoss AS 7.1 Generate the UnifiedPush Database and Datasource
[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
→ ~/Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/jboss-cli.sh
--file=../databases/h2-database-config.cli
#1 data-source add --name=UnifiedPushDS --driver-name=h2
--jndi-name=java:jboss/datasources/UnifiedPushDS
--connection-url="jdbc:h2:${jboss.server.data.dir}/unifiedpush;DB_CLOSE_DELAY=-1"
--user-name=sa --password=sa --use-ccm=true
#2 data-source enable --name=UnifiedPushDS
The batch executed successfully.
Deployment
[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
→ mvn jboss-as:deploy -Pas7
Server Log
19:26:19,552 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-8) MSC00001: Failed to start service
jboss.deployment.unit."ag-push.war".WeldService:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."ag-push.war".WeldService:
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
dependencies for type [HttpServletRequest] with qualifiers [@Default]
at injection point [[parameter 1] of [constructor] @Inject public
org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408
Unsatisfied dependencies for type [HttpServletRequest] with qualifiers
[@Default] at injection point [[parameter 1] of [constructor] @Inject
public org.jboss.aerogear.unifiedpush.service.impl.SearchManager(HttpServletRequest)]
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
... 5 more
Wildfly 8.1.0 Generate the UnifiedPush Database and Datasource
[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
→ ~/Development/Java/Server/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.sh
--file=../databases/h2-database-config.cli
The batch failed with the following error (you are remaining in the
batch editing mode to have a chance to correct the error):
{"JBAS014653: Composite operation failed and was rolled back. Steps
that failed:" => {"Operation step-1" => "JBAS014749: Operation handler
failed: Service jboss.data-source-config.UnifiedPushDS is already
registered"}}
Server Log
19:49:48,359 INFO [org.jboss.as.connector.subsystems.datasources]
(MSC service thread 1-2) JBAS010400: Bound data source
[java:jboss/datasources/UnifiedPushDS]
19:49:48,360 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 1) JBAS014612: Operation ("add") failed -
address: ([
("subsystem" => "datasources"),
("data-source" => "UnifiedPushDS")
]): org.jboss.msc.service.DuplicateServiceException: Service
jboss.data-source-config.UnifiedPushDS is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1511)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188)
at org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:606)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:484)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:281)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:276)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:271)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:145)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:199)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at java.security.AccessController.doPrivileged(Native Method)
[rt.jar:1.7.0_45]
at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_45]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
[wildfly-controller-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
[wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
[wildfly-protocol-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.1.1.Final.jar:2.1.1.Final]
19:49:48,376 INFO [org.jboss.as.connector.subsystems.datasources]
(MSC service thread 1-7) JBAS010409: Unbound data source
[java:jboss/datasources/UnifiedPushDS]
Deployment
[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
→ mvn wildfly:deploy -Pwildfly
.
.
.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] UnifiedPush Auth Server ........................... SUCCESS [10.217s]
[INFO] UnifiedPush Server for JBossAS (WAR) .............. FAILURE [4.306s]
[INFO] UnifiedPush Servers Parent ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.561s
[INFO] Finished at: Mon Oct 20 19:26:19 BRST 2014
[INFO] Final Memory: 35M/367M
[INFO] ------------------------------------------------------------------------
Server Log
19:50:58,648 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-4) MSC000001: Failed to start service
jboss.undertow.deployment.default-server.default-host./auth:
org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth: Failed to
start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.RuntimeException: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:160)
at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2175)
at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:295)
at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:236)
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:214)
at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:119)
at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:505)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
[jboss-msc-1.2.2.Final.jar:1.2.2.Final]
... 3 more
Caused by: javax.persistence.PersistenceException: Unable to build
entity manager factory
at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:83)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:95)
at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:24)
at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:16)
at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:28)
at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:15)
at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:88)
at org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:67)
at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:173)
at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:42)
at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:33)
at org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:137)
at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
at org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:86)
at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.<init>(UpsKeycloakApplication.java:35)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
[rt.jar:1.7.0_45]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
[rt.jar:1.7.0_45]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
[rt.jar:1.7.0_45]
at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
... 15 more
Caused by: org.hibernate.engine.jndi.JndiException: Unable to lookup
JNDI name [java:jboss/datasources/UnifiedPushDS]
at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:117)
at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:115)
at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:75)
... 36 more
Caused by: javax.naming.NameNotFoundException:
datasources/UnifiedPushDS -- service
jboss.naming.context.java.jboss.datasources.UnifiedPushDS
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:415)
[rt.jar:1.7.0_45]
at javax.naming.InitialContext.lookup(InitialContext.java:415)
[rt.jar:1.7.0_45]
at org.hibernate.engine.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:114)
... 52 more
19:50:58,659 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 1) JBAS014613: Operation ("deploy")
failed - address: ([("deployment" => "auth-server.war")]) - failure
description: {"JBAS014671: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./auth" =>
"org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth: Failed to
start service
Caused by: java.lang.RuntimeException: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
Caused by: javax.persistence.PersistenceException: Unable to build
entity manager factory
Caused by: org.hibernate.engine.jndi.JndiException: Unable to
lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
Caused by: javax.naming.NameNotFoundException:
datasources/UnifiedPushDS -- service
jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
19:50:58,662 ERROR [org.jboss.as.server] (management-handler-thread -
1) JBAS015870: Deploy of deployment "auth-server.war" was rolled back
with the following failure message:
{"JBAS014671: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./auth" =>
"org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth: Failed to
start service
Caused by: java.lang.RuntimeException: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
Caused by: javax.persistence.PersistenceException: Unable to build
entity manager factory
Caused by: org.hibernate.engine.jndi.JndiException: Unable to
lookup JNDI name [java:jboss/datasources/UnifiedPushDS]
Caused by: javax.naming.NameNotFoundException:
datasources/UnifiedPushDS -- service
jboss.naming.context.java.jboss.datasources.UnifiedPushDS"}}
Using java version “1.8.0_25”
------------------------------
JBoss AS 7.1
I can not start JBoss AS 7.1 using Java 8
[passos]: ~
→ ./Development/Java/Server/JBoss/jboss-as-7.1.1.Final/bin/standalone.sh
-b 0.0.0.0
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/passos/Development/Java/Server/JBoss/jboss-as-7.1.1.Final
JAVA: java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation
-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
-Djboss.server.default.config=standalone.xml
=========================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
19:42:02,527 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:42:02,866 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:42:02,947 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
"Brontes" starting
Wildfly 8.1.0 Deploy
[passos]: ~/Development/Projects/AeroGear/aerogear-unifiedpush-server/servers
[git:pr/408]
→ mvn wildfly:deploy -Pwildfly
Seeing an error during mvn -Pdeploy install of quickstarts on Mac OS
X, using jdk 1.6. I do not see this error with jdk 1.7. I'm trying to
deploy against EAP, but I'm not sure that matters given the error
looks to be JDK/path/version-based.
[ERROR] Failed to execute goal
org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
(deploy) on project switchyard-validate-xml: Execution deploy of goal
org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy-only
failed: Plugin org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final or
one of its dependencies could not be resolved: Could not find artifact
sun.jdk:jconsole:jar:jdk at specified path
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/jconsole.jar
-> [Help 1]
I found the same problem in SwitchYard quickstart
<https://issues.jboss.org/browse/SWITCHYARD-2315>
— Passos
9 years, 6 months
