This one time, at band camp, bikehead said:
b>I have some clarification questions:
b>
b>1. how exactly is the descriptor used? I have hunted throught the API
b>and I can find a use of it anywhere. How does castor know to use my
b>CustomerDescriptor class? An example would be great.
b>
b>2. The reason I'm even trying to understand the descriptor is that it
b>appears to let me control how a values are accessed from an object.
b> Specifically, as far as I can tell the XMLFieldDescriptor has a
b>XMLFieldHandler which defines implementations for getValue and setValue
b>calls. I have a non-standard way to access fields in my objects and I
b>want to change the implementations of get/setValue to access the object
b>using different access methods. If I change the implementation of the
b>handlers for my descriptor will Castor XML use the new implementations
b>to access the properties in my object? Will Castor JDO use these
b>handlers to access the properties also?
Brian,
Please see these two documents about the mapping descriptor:
http://www.castor.org/xml-mapping.html
http://www.castor.org/jdo-mapping.html
There are two documents describing it because it is used for both JDO
and XML. It is completely legal, however, to have more than one mapping
descriptor that is used at different times for different scenarios.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
