Hi, This test shouldn't fail, because if the datasource is not Serializable CDI implementation must handle it (so that it can be used as passivation capable dependency). Weld creates Serializable proxy in such case - see [1]. Can you please post the stacktrace of your failure and describe your environment (app server, CDI impl etc.)? Thanks Tomas [1] https://github.com/weld/core/blob/2.4/impl/src/main/java/org/jboss/weld/b... ----- Original Message ----- From: "Lazar Kirchev" <lazar.kirchev(a)gmail.com&gt; To: cdi-tck(a)lists.jboss.org Sent: Monday, June 5, 2017 5:08:46 PM Subject: [cdi-tck] Question about a test in the TCK for CDI 1.1 Hello, I have a question about the test DataSourcePassivationDependencyTest ( https://github.com/cdi-spec/cdi-tck/blob/1.1/impl/src/main/java/org/jboss... ) In this test a DataSource is injected in the passivation capable bean Pool ( https://github.com/cdi-spec/cdi-tck/blob/1.1/impl/src/main/java/org/jboss... ) and according to the spec the DataSource should be Serializable in this case. In this way the test requires the DataSource to be Serializable, but actually DataSources may not be Serializable. There are DataSource implementations which are not, and with such an implementation the test fails. Is this expected, that all CDI implementations are used with Serializable DataSources? Regards, Lazar _______________________________________________ cdi-tck mailing list cdi-tck(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-tck