On Jul 1, 2009, at 13:28 , Andreas Junghans wrote:
[CUT]
The serialization behaviour you need is quite different from what's
currently done (JavaBean-based vs. attribute-based). I don't think it
would be good idea to completely replace the existing approach.
Instead, the algorithm should be configurable so that users can choose
between JavaBean-based and attribute-based serialization (or plug in
their own custom code).
Yes, I fully agree.
Inspired from Hibernate, an annotation at class (bean) level may be used to choose.
Currently, I'm no more trying to filter the map but to build it since beanutils use the bean-based way. This is currently super ineficient since the map is still calculated the bean-based way but I don't care.
First, I want to make it work and only after, I'll think about what to improve.
Here is what can be done with Hibernate as an analogy :
@Entity
@AccessType("field")
public class MyBean { ... }
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
