> > I also prefer ignoring it consistently. But considering that > > enhancement fails, this seems like more than a WARN. More like a > > SEVERE. And if you get a SEVERE during enhancement, should we > > really put the EMF into service at all? Issue #2? > > I agree. If we get an enhancement error, I think we should throw an > exception from the EMF consturctor. The problem is that enhancement > seems to happen only as beans are used (loaded into memory), so the > EMF doesn't know that enhancement won't work.
I think that if the classes are listed in the persistence.xml, it will fail eagerly. Probably setting exclude-unlisted-classes to true and referencing an orm.xml will also cause eager failure. > >> 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? -Patrick _______________________________________________________________________ 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.
