Lance,
great to talk to you again. :-)
>> "Serializable" and "Externalizable" only are marker interfaces that
>> declare that the programmer thinks that his Java Bean is serializable.
> Yes i am aware of that.
Yes, certainly. But since this is a public discussion I thought it
beeing approporiate to write a few illustrative words, so others can
easily follow my rationale.
>> Whether or not it is serializable depends on a lot of other factors,
>> like having a public no-arg constructor, marking all non-serializable
>> attributes as transient, and so on (= the bean ACTUALLY is
>> serializable, independend of the declaration using marker interfaces).
> Historically when a specification references serializable it is done
> so based on the requirements defined in the Serialization spec.
It seems that this is not as obvious as you might expect. At least the
first answer I received in this thread was that it is *not* needed to
implemented Serializable.
>> Also, if a bean ACTUALLY is serializable, you can serialize it even
>> if it is NOT marked as "Serializable" or "Externalizable", using
>> java.bean.XMLEncoder. Using XMLEncoder you can serialize an object
>> independent of its marker interfaces.
> If you are looking for specific specification clarification, then you
> need to use the JSR alias for either JSR 220 or JSR 317 using the
> alias jsr-220-comments_at_jcp.org or jsr-317-comments_at_jcp.org
I see. Thank you for the tip. I will ask Linda to clarify this. :-)
Thanks
Markus
--
http://www.xing.com/go/invita/58469