The ClassUtil methods are great for converting XML service results into
locally typed instances, but lack a feature I've been using in my own
version of such things.
For rapid prototyping and ease of evolution, I've found it extremely useful
to make my various Model objects dynamic classes rather than sealed classes
and allow them to have whatever "extra" properties come across from the
server in the XML results. Frankly, in many cases, the property data coming
for the server doesn't need to be statically typed unless my Model classes
needs to compute or otherwise use a specific property. Often, it's just a
property for display to the user.
You should be able to add such by augmenting your loops to not just process
the properties and accessors of the target class, but also consider any
additional properties of the source object itself.
Original issue reported on code.google.com by bpja...@gmail.com on 24 Jun 2008 at 2:49
Original issue reported on code.google.com by
bpja...@gmail.com
on 24 Jun 2008 at 2:49