<<What would modifying a properties file directly gain you that modifying a configuration file wouldn't?>>
This would be for the benefit of the user (by user I mean the administrator configuring the web service) of the web service developed with CXF. The user would just need to change property file settings. The user will not need knowledge of the CXF configuration files or increase the chance of the mistakenly (or deliberately) changing the CXF configuration files resulting in the web service failing. Thanks Glen. I will 'research' Java configuration. -----Original Message----- From: Glen Mazza [mailto:[email protected]] Sent: Friday, March 11, 2011 10:42 AM To: [email protected] Subject: EXTERNAL: Re: Configuration files for CXF Since both the config files and the properties files are text files deployed with your application, I'm not sure what the difference would be. What would modifying a properties file directly gain you that modifying a configuration file wouldn't? At any rate, one possibility would be to look at Java API solutions for your configuration, and then, using standard Java properties file reading techniques from within Java class files, load your configuration in that way. Glen On 3/11/2011 10:34 AM, Morris Jr, David P wrote: > Can hardcoded values in the configuration files for CXF be removed and read > out of properties files? Basically remove the hardcoding for the web services > endpoints. Is there an 'expression language'? -- Glen Mazza Software Engineer, Talend (http://www.talend.com) blog: http://www.jroller.com/gmazza
