Paul Brinkley wrote:
> At 10:12 PM 3/4/01 +0530, J.Ganesan wrote:
> >
> >
> >Paul Brinkley wrote:
>
>
> The standard way around this is externalization. It's a
> more hands-on version of serialization. First, have your
> class implement java.io.Externalizable. Then you have to
> implement two methods it defines; I can't remember the
> names of them off the top of my head, but they're clearly
> outlined in the Javadoc for Externalizable. An externalizable
> object writes -only- those fields you tell it to in the
> "write" method.
Externalization works. Thank you and others for helping me.
ganesan
>
>
> The superclass is initialized using its no-arg constructor.
> AbstractTableModel happens to have one, so you're fine there.
>
> Again, I'm not certain serialization/externalization is the
> "right" approach here, since you're explicitly interested
> in saving only the table data. I would implement a method
> on X that saves just table data, but that's me.
>
> _______________________________________________
> Advanced-swing mailing list
> [EMAIL PROTECTED]
> http://eos.dk/mailman/listinfo/advanced-swing
_______________________________________________
Advanced-swing mailing list
[EMAIL PROTECTED]
http://eos.dk/mailman/listinfo/advanced-swing
