ConfigureImpl with spring construction duplicates looking for cxf.xml on the classpath and can error out with a warning

Since: http://svn.apache.org/viewvc?view=rev&revision=584908

cxf.xml in rt-core is responsible for creating an instance of ConfigureImpl. This is problematic because the defauilt constructed version of ConfigureImpl looks for cxf.xml (or cxf.config.file sys property) on the classpath (it does not look for cxf.config.uri!) and creates a BusApplicationContex if it finds one. This is unnecessary as the current applicaton context will be injected in via the ApplicationContextAwareProcessor.

When cxf.xml on the classpath references other beans that come from extensions, application context creation fails with an exception that is logged as a warning. this is ugly.
This is not uncommon as cxf.xml is the default user configuration file name.

It seems like ConfigureImpl is duplicating code around default configuration that is already managed by the BusApplicaitonContext.

Does ConfigureImpl have a place outside spring that necessitates looking for cxf.xml?

I think the fix may be to remove the posibility that ConfigureImpl can create its own BusApplicationContext. What do you think.