ConfigurationProviders don't know anything about
PersistenceProviders,
of course, and need to be constructible via a no-args constructor.
But
maybe the PersistenceProviderImpl could populate the
ConfigurationProvdierImpl with information about which subclass of
PersistenceProviderImpl it should succeed for.
I've come up with the beginnings of an idea of how to fix this. The
idea ties in nicely with something else I've been wanting to do for a
while, which is get rid of ConfigurationProviders as a service, and
do everything through ProductDerivations.
If no one has any objections, I can play around with this later in
the week.
-
_______________________________________________________________________
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.
