I don't think there would be a problem in including Cloneable and Serializable. It just doesn't feel particularly useful.
Hm, this might be possible but I don't really see a use for it that wouldn't already be covered by having Object as type (mostly just a catch-all type to monitor/tweak bean attributes).
The only case I am not sure about is proxyability; array types are not proxible but if you can treat that same bean as Serializable, that should be proxyable.
When it comes to arrays of superclasses, remember that arrays are both mutable and covariant. Meaning that if someone produced Integer[] and someone else consumed it as Number[], they could set some element of the array to a Double, violating the original expectation that only Integers are present. I wasn't doing CDI at that time, but this feels like a good enough reason to exclude arrays of superclasses.
I do not know the original decision either but your justification makes a lot of sense.
_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
