This one time, at band camp, [EMAIL PROTECTED] said:
>Thanks for your quick reply. Kind of along the same line... The most
>overhead seems to be when JDO is initializing. What are some common
>strategies people use to avoid this overhead in their applications? I am
>thinking along the lines of initializing during Servlet startup, but I'm
>not sure at what point in the code JDO starts to initialize, and also how
>wise it is to do something like this.
Yes, that's correct. Usually that can be mitigated by writing a startup
servlet. However, if you switch mappings on the fly, the app will take
a slight hit again. With a J2EE container it can be fired up by the
container at startup. For example, JBoss has an MBean to fire up Castor
when the container is initialized.
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
