Re: [cdi-dev] [weld-dev] Overly restrictive serialization requirements

Hi David, On 24 May 2011, at 12:06, Pete Muir wrote: I think this is what you are missing, CDI can validate this at deployment time in many cases as it can resolve the actual bean (and hence concrete type) that will be injected. Of course, it can't actually check that the instance will serialize, but it can check some basic requirements (like it must impl serializable, and that it's dependency graph is passivatable). There are of course some special situations such as producers, when we don't know the concrete type at deployment type, and generally producers are passivation capable even if they don't implement serializable (we can only check this if the return type is final, then it must implement Serializable). This is a good point, the spec doesn't allow for custom serialization callbacks. I wonder if it makes sense that if the class does override serialization then CDI should assume the class is passivation capable. Leaving aside EJBs (of which SFSBs are always passivation capable due to the guarantees of the EJB container), this is largely all the spec requires checking - that the entire graph of dependencies injected into a passivation capable bean is passivation capable. Because we can do a much stricter check on the class as we know at deploy time exactly what it's fields, methods and constructors will be called with, this is something that Java cannot know so cannot enforce, with the proviso regarding custom serialization not being accounted for above.