Jsf UnserializableDependencyException:WELD-001413:bean声明了钝化作用域，但具有非钝化功能的依赖项

我有以下CDI托管bean：

@Named
@SessionScoped
public class InfoPageController implements Serializable {

    @Inject
    private InfoPageMapper mapper;

}

它在部署到GlassFish 4.1期间引发以下异常：

Exception while loading the app : CDI deployment failure:WELD-001413: The bean Managed Bean [class de.triaconsulting.cashyourgame.fe.controller.InfoPageController] with qualifiers [@Default @Any @Named] declares a passivating scope but has a non-passivation-capable dependency Managed Bean [class de.triaconsulting.cashyourgame.fe.mapper.InfoPageMapper] with qualifiers [@Any @Default]
org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001413: The bean Managed Bean [class de.triaconsulting.cashyourgame.fe.controller.InfoPageController] with qualifiers [@Default @Any @Named] declares a passivating scope but has a non-passivation-capable dependency Managed Bean [class de.triaconsulting.cashyourgame.fe.mapper.InfoPageMapper] with qualifiers [@Any @Default]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPointPassivationCapable(Validator.java:477)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:395)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:291)
    at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:165)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:529)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:515)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:490)
    at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:419)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:90)
    at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:225)
    at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
    at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:496)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219)
    at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:356)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:356)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722)
    at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:534)
    at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:224)
    at org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:189)
    at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:459)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:167)
    at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:201)
    at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:175)
    at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:235)
    at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:284)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:201)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:133)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:112)
    at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
    at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:561)
    at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:56)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:137)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:565)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:545)
    at java.lang.Thread.run(Thread.java:745)

---

这是如何导致的，我如何解决它？

根据服务器错误消息，请检查de.triaconsulting.cashyourgame.fe.mapper.InfoPageApper。 InfoPageApper实现是否可序列化

在InfoPageController对象的会话范围中插入InfoPageApper对象。 会话范围对象及其成员需要序列化。因此，InfoPageApper对象必须能够序列化

因此，InfoPageApper必须实现可序列化接口

---

如果不想序列化InfoPageController中的InfoPageApper对象，可以在此变量处设置transient关键字。

首先选择解决方案，然后给出解释：

最简单的方法是将

InfoPageController

中的字段

InfoPageApper mapper

标记为

transient

：

@Named
@SessionScoped
public class InfoPageController implements Serializable {

    @Inject
    transient private InfoPageMapper mapper;

现在解释一下：

错误消息以可读的语言表示：

会话范围为的bean InfoPageController必须是 可序列化，但它需要InfoPageApper，而InfoPageApper不是 可串行化或瞬态-无法确定如何 序列化InfoPageController

在CDI中，有一些作用域（通常是SessionScope）要求bean可以序列化，这主要是因为它们以某种方式连接到HTTP会话，HTTP会话可以包含更多适合内存的对象，服务器有时可能需要将它们交换到磁盘

似乎是因为InfoPageController实现了可序列化。但根据Java序列化原则，这还不够。您需要确保可序列化类的所有成员字段都是以下字段之一： -基本类型（整型、布尔型） -可序列化的对象（所有序列化规则递归应用） -该字段标记有关键字transient（与private关键字位于同一级别）

CDI的诀窍在于，您可以将所有注入的字段标记为瞬态，因为当对象从磁盘反序列化到内存中时，它们会再次注入。因此，您不会丢失瞬态对象，否则在反序列化时该对象将为空，因为它以前未存储到磁盘

---

另一个解决方案是使注入的bean InfoPageApper也可序列化。但是，当字段被注入InfoPageApper时，问题可能会反复出现。Transient关键字可以解决您的问题，如果不需要，也不会强制其他BENA可序列化。

该消息提到

InfoPageApper

，但我在您的帖子中没有看到任何定义-除了

InfoPageController

中的引用。消息有点精简：

bean管理的bean[…InfoPageController]。。。声明一个钝化作用域，但有一个非钝化功能的依赖项管理Bean[…InfoPageApper]

我相信这仅仅意味着不是会话作用域Bean的所有注入Bean/属性都是可序列化的。在标记字段transient之前，我将再次检查该字段是否属于会话处理bean。如果InfoPageApper是具有默认作用域（@Dependent）的bean，则隐式将其设置为会话作用域bean。因此，它在每个会话中都是重复的。如果映射器有更多的控制器角色，您可能最好将会话范围的元素注入其中，每次调用时都会检索到正确的数据。@Kazaag-您是对的，在某些情况下，将注入的bean作为SessionScoped是有意义的。从技术角度来看，它也是一个可序列化的bean，因此它可以解决异常问题。从逻辑角度来看，应用程序的行为可能不同，因为多个bean在会话范围内共享同一个bean。也许有一点建议：对于我的测试用例，我还忘了在bean中将发现模式从“注释”设置为“全部”。xml。