Secondly, are we parsing the XML file multiple times? The only
way for the first warning to be fired is if OpenJPA has read my
entity mappings, but the exception that is thrown later is a SAX
exception which implies that OpenJPA is reading the file again.
Sounds like an inefficient startup algorithm that we should fix.
Issue #3?
We might be parsing it multiple times, but for different reasons and
with different parsers. Are you listing entities in an orm.xml and
then
pointing at that orm.xml / relying on the default location?
IIRC (and that's a fairly big "if"), the first "parse" is more of a
string scan looking for class names than a real XML parse, and is
done with a subclass of ClassArgParser. This is one of those things
that made sense for the way the metadata system warmed up, then we
changed some stuff or the spec changed or both, and it no longer
makes much sense. I had it on my list of things to redo, but it got
pushed off because it hadn't caused enough problems to justify the
effort.
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
