servlet with @OAuth2AuthenticationDefinition could not be deployed due to CDI deployment failure:WELD-001408:
119 views
Skip to first unread message
Kamlendu Pandey
Dec 10, 2019, 11:42:27 AM12/10/19
to Payara Forum
Pl. help ! I am just running an example from https://github.com/javaee-samples/vendoree-samples/tree/master/payara/oauth2/src/main/java/fish/payara/security/oauth2/testapp which uses @OAuth2AuthenticationDefinition annotation apart from payara 5.194 I am using downloaded payara-api-5.194.jar . I am able to build the war file but while deploying it throws exception as
SEVERE: Exception during lifecycle processing
org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type OAuth2State with qualifiers @Default
at injection point [UnbackedAnnotatedField] @Inject private fish.payara.security.oauth2.OAuth2AuthenticationMechanism.state
at fish.payara.security.oauth2.OAuth2AuthenticationMechanism.state(OAuth2AuthenticationMechanism.java:0)
-- WELD-001408: Unsatisfied dependencies for type OAuth2State with qualifiers @Default
at injection point [UnbackedAnnotatedField] @Inject private fish.payara.security.oauth2.OAuth2AuthenticationMechanism.state
at fish.payara.security.oauth2.OAuth2AuthenticationMechanism.state(OAuth2AuthenticationMechanism.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:512)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:487)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:496)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:93)
at org.glassfish.weld.WeldDeployer.processApplicationLoaded(WeldDeployer.java:517)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:428)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:333)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepare(ApplicationLifecycle.java:490)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:540)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:557)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:553)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:552)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:583)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:575)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:574)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1483)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:119)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1865)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1741)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:564)
at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:251)
at org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:166)
at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:520)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:217)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:182)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:156)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:218)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:95)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:260)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:177)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:109)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:88)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:53)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:524)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:89)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:94)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:33)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:114)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:569)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:549)
at java.lang.Thread.run(Thread.java:748)
Mike Ryan
Dec 12, 2019, 10:09:15 AM12/12/19
to Payara Forum
I am also facing this problem. If I import the payara-api, I receive this same exception and cannot deploy.
I'm only interested in using the @RealmIdentityStoreDefinition.
Mike Ryan
Dec 12, 2019, 11:03:27 AM12/12/19
to Payara Forum
This issue has a suggested fix that worked for me, which was using provided in the dependency.
I'm using Gradle, so for me that meant using
providedCompile 'fish.payara.api:payara-api:5.194'
Ondro Mihályi
Dec 12, 2019, 11:46:00 AM12/12/19
to Mike Ryan, Payara Forum
Hi,
Yes, using the payara-api as a provided dependency (i.e. not bundled in the WAR file) is the solution.
The sample project uses it that way, you just have to look in the parent pom how the dependency is declared: https://github.com/javaee-samples/vendoree-samples/blob/master/payara/pom.xml#L30
št 12. 12. 2019 o 17:03 Mike Ryan <m.rya...@gmail.com> napísal(a):
--
You received this message because you are subscribed to the Google Groups "Payara Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to payara-forum...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/payara-forum/76bc25a1-880c-434a-ab01-93329fbef68c%40googlegroups.com.
Kamlendu Pandey
Dec 15, 2019, 1:53:41 PM12/15/19
to Payara Forum
Tanks. With maven it is fine. But how to do this with ANT builder. Netbeans use ANT as default builder.
Reply all
Reply to author
Forward
0 new messages