The facts are that:
1. A gbean itself does not need to be serializable.
2. Only the gbean attributes are serialized.
3. The de-serialized attributes are injected at runtime to construct the gbean.
My question is why does a gbean get different treatment than attribute? I've got a feeling it's this way because gbeans are complex objects while most gbean attributes are simple types. But we are starting to see gbean objects that have complex attribute types.
Why not also give gbean attributes the kind of runtime construction support that is given to gbeans? If this was done, then you don't force complex attributes to implement the Serializable interfaces. This could go a long way in helping solve some of the serialization issues that are being discussed in other threads.
Regards, Hiram Chirino
