0

每当我使用

@SubjectRequired或@SubjectNotRequired注释：

play.api.http.HttpErrorHandlerExceptions$$anon$1: Execution exception[[CompletionException: java.lang.NullPointerException]]
    at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:293)
    at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:220)
    at play.api.GlobalSettings$class.onError(GlobalSettings.scala:160)
    at play.api.DefaultGlobal$.onError(GlobalSettings.scala:188)
    at play.api.http.GlobalSettingsHttpErrorHandler.onServerError(HttpErrorHandler.scala:100)
    at play.core.server.netty.PlayRequestHandler$$anonfun$2$$anonfun$apply$1.applyOrElse(PlayRequestHandler.scala:100)
    at play.core.server.netty.PlayRequestHandler$$anonfun$2$$anonfun$apply$1.applyOrElse(PlayRequestHandler.scala:99)
    at scala.concurrent.Future$$anonfun$recoverWith$1.apply(Future.scala:344)
    at scala.concurrent.Future$$anonfun$recoverWith$1.apply(Future.scala:343)
    at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
Caused by: java.util.concurrent.CompletionException: java.lang.NullPointerException
    at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
    at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
    at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:961)
    at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)
    at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
    at play.core.j.HttpExecutionContext$$anon$2.run(HttpExecutionContext.scala:56)
    at play.core.j.HttpExecutionContext$$anon$2.run(HttpExecutionContext.scala:56)
    at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:39)
    at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:415)
    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
Caused by: java.lang.NullPointerException: null
    at be.objectify.deadbolt.java.cache.DefaultSubjectCache.apply(DefaultSubjectCache.java:80)
    at be.objectify.deadbolt.java.cache.DefaultSubjectCache.apply(DefaultSubjectCache.java:38)
    at be.objectify.deadbolt.java.ConstraintLogic.getSubject(ConstraintLogic.java:348)
    at be.objectify.deadbolt.java.ConstraintLogic.subjectTest(ConstraintLogic.java:116)
    at be.objectify.deadbolt.java.ConstraintLogic.subjectPresent(ConstraintLogic.java:72)
    at be.objectify.deadbolt.java.actions.SubjectPresentAction.lambda$testSubject$129(SubjectPresentAction.java:91)
    at java.util.Optional.orElseGet(Optional.java:267)
    at be.objectify.deadbolt.java.actions.AbstractSubjectAction.lambda$execute$118(AbstractSubjectAction.java:76)
    at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:952)
    at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)

我的代码如下所示：

在课堂实施DeadboltHandler

@Override
public CompletionStage<Optional<? extends Subject>> getSubject(Context elContext) {
    return CompletableFuture.supplyAsync(
        () -> {
            try {
                return Optional.ofNullable(da.getUser(Integer.parseInt( elContext.session().get("userId"))));
            } catch (Exception e) {
                e.printStackTrace();
                return null;
            } 
        });
}

where is 有一个构造函数：

DataAccess da;

DeadboltSecureHandler(Database db){
    da = new DataAccess(db);
}

并在课堂上实施HandlerCache

@Inject 
public DeadboltHandlerCache(Database db){
    DeadboltHandler defaultHandler = new DeadboltSecureHandler(db);
    handlers.put(HandlerKeys.DEFAULT.key, defaultHandler);
}

@Override
public DeadboltHandler apply(final String key){
    return handlers.get(key);
}

@Override
public DeadboltHandler get(){
    return defaultHandler;
}

有什么想法我搞砸了吗？

4

1 回答 1

1

一些东西...

deadboltHandler您使用的是 null，对此最可能的解释HandlerKeys.DEFAULT.key与be.objectify.deadbolt.java.ConfigKeys.DEFAULT_HANDLER_KEY.

如果您查看文档，您会发现以下内容（这让我猜测您使用的是早于 2.5.3 的 Deadbolt 版本）：

注意 ConfigKeys.DEFAULT_HANDLER_KEY 的使用 - 这是所有注释指定的默认处理程序键。在以前版本的 Deadbolt 中，注释驱动的约束将用于HandlerCache#apply(DEFAULT_HANDLER_KEY)获取处理程序，因此默认处理程序必须与DEFAULT_HANDLER_KEY. 从 Deadbolt 2.5.3 开始，这一点得到了改进，任何使用默认处理程序键的注释驱动的约束将改为使用HandlerCache#get.

您将使用当前代码遇到的下一个问题是：

当您返回时null，您违反了该getSubject方法的合同。每当有东西返回CompletionStage<Optional<? extends Subject>>时，CompletionStage必须包含一个Optional. 与其返回null，不如返回Optional.empty()。

于 2017-02-09T09:03:02.220 回答