Hi,
I think the reflection will be used all the time, because if you define the
mapping (and in the mapping you can define getters/setters) there's still
necessary to create objects "on the fly".
Something like:
1) this element is mapped to this class
2) create the class by reflection [obj = Class.forName(...).newInstance();]
3) this element is mapped to use this setter
4) invoke this setter over the created object
Method m ...;
m.invoke(obj, <args>);
5) ...
All these frameworks need to use reflection to marshal/unmarshal objects.
This is my opinion, but I can be wrong :-)
Pat
On Fri, 8 Dec 2006 16:53:34 +0800, Xinjun Chen wrote
> Hi,
>
> I am going to start testing Castor. I have some questions about Castor.
> From google, I can find that quite a few articles saying Castor is slow
because of Java reflection.
> Here my question is, if during the marshalling and unshalling, the
binding.xml is provided, will Castor still use Java reflection during
marshalling and unmarshalling?
>
>
> Regards,
> Xinjun
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
