[
https://issues.apache.org/jira/browse/CXF-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated CXF-1260:
----------------------------
Attachment: ignore_cxf_xml.patch.txt
this patch ensures that ConfigureImpl will not look for cxf.xml on the
classpath and will not create a Busapplicaiton context. The application context
is either passed in in the constructor or set via the setter. at the moment the
set injection is preformed automatically as it implements the
ApplicationContextAware interface.
> ConfigureImpl with spring construction duplicates looking for cxf.xml on the
> classpath and can error out with a warning
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-1260
> URL: https://issues.apache.org/jira/browse/CXF-1260
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.0.3
> Reporter: Gary Tully
> Fix For: 2.0.4
>
> Attachments: ignore_cxf_xml.patch.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
