commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimiter Dimitrov" <dimi...@blue-edge.bg>
Subject RE: [beanutils][lang] how to serialize/deserialize Methods/PropertyDescriptors
Date Thu, 06 Feb 2003 20:41:38 GMT
> From: Stephen Colebourne [mailto:scolebourne@btopenworld.com] 
> Sent: Thursday, February 06, 2003 10:19 PM
>
> There might be a case for serializing Method objects to be in 
> [lang]. PropertyDescriptor would be excluded from [lang] 
> however, as this is out of scope for [lang] and in scope for 
> [beanutils].
>
> Would you want to separate the two methods into two 
> locations? Would it be of use to only have the Method one committed?
> 
> Stephen


Yes, it's fine to split them and commit the Method only. 

Though I use the PropertyDescriptor serialization, I'm still not sure if
I like it this way.

I'm not sure which is better to have a static "foreign" method or to
create a SerializablePropertyDescriptor wrapper.

For my case the latter makes sence, since I store a collection of
propertiesin a serializable class.
Currently I implement the read/writeExternal() methods to serialize
them.
With this wrapper, I can just convert them when I put them in the list
and use the default java serialization.

Is it too specific case? An issue with the wrapper approach is that it
doesn't work on classes with no accessible constructor (e.g. Method).


I also think that we don't need two ways to save a PropertyDescriptor.
I prefer the getter/setter dethods approach, so we can discard the other
(class+propName).

--Dimiter


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message