Loading a mapping file should be negligable. It's done only once (unless
you've accidently put it in a loop). Once a mapping is loaded into
memory it's converted into JDOClassDescriptors (or XMLClassDescriptor if
you are using Castor XML). The only advantage of a Compile time option
would be that you don't have to use reflection to access the fields or
the accessor methods (setter/getter).
However, based on who you talk to, reflection may not really have much
of a performance impact on an application. There are tests that show
it's insignificant, and other tests that show that it is. I haven't
jumped on either band wagon. You can test for yourself by implenenting
JDOClassDescriptor for one of your classes and see if it's faster than
using a mapping file. It's a bit of work to implement one of these by
hand so get a big cup of coffee and some good music if you decide you
want to try it.
No matter how much fine tuning you do with Castor, the database and
network is probably going to remain your biggest overhead.
--Keith
"Davis, Richard" wrote:
>
> Hey, a couple of questions about JDO mapping:
>
> Is there a JDO compile time descriptor option? Is there an impact with
> having to load the jdo mapping file at run time?
>
> thanks, rich
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
