[
https://issues.apache.org/jira/browse/CXF-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550077
]
Gary Tully commented on CXF-1275:
---------------------------------
I think the fix for #CXF-1260 will not help. The resolution of config in
ConfigureImpl is unnecessary. The BusApplicationContext does the real work.
I think you need to use the URL version to specify the config file:
-Dcxf.config.file.url=classpath:META-INF/cxf.xml
Gary.
> System property -Dcxf.config.file has no effect
> -----------------------------------------------
>
> Key: CXF-1275
> URL: https://issues.apache.org/jira/browse/CXF-1275
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.0.3
> Reporter: Ralf Taugerbeck
>
> I would like to specify a custom cxf configuration file to my client
> application (e.g. META-INF/cxf.xml), but the system property
> -Dcxf.config.file obviously has no effect.
> Because the default constructor of ConfigurerImpl passes the name of the
> default config file, the corresponding code in ConfigurerImpl(String cfgFile)
> is never executed:
> public ConfigurerImpl(String cfgFile) {
> if (null == cfgFile) {
> cfgFile = System.getProperty(USER_CFG_FILE_PROPERTY_NAME);
> }
> ...
> Could you please modifiy the code of the default constructor to:
> public ConfigurerImpl() {
> this(null);
> }
> or something equivalent? I'm not sure whether this issue is fixed by the
> #CXF-1260 patch.
> Thanks,
> Ralf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
