When each class is encountered its metadata is checked for correctness. This
could impact on performance of startup since it is performed each time an
instance of the PMF/EMF is created (and this can happen many times with
instances spinning up). Once the user has had their metadata checked once it
can be assumed to be ok, so just provide a persistence property that says
"don't bother checking metadata for validity, and startup. I'll take the
consequences!"
Original issue reported on code.google.com by googleco...@yahoo.co.uk on 22 Oct 2012 at 1:00
Original issue reported on code.google.com by
googleco...@yahoo.co.uk
on 22 Oct 2012 at 1:00