cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Smyth <>
Subject Re: Use of ***.cxf files in the samples
Date Mon, 18 Jun 2007 14:44:27 GMT
Johnson, Eric wrote:

>What is the reason for using .cxf files to hold the configuration
>information for the samples instead of just using the default cfx.xml
>file? Is this a "Best Practice" for using CXF?
Hi Eric,

What do you mean with the default cxf.xml file - and with 'instead of'?
If you refer to the META-INF/cxf/cxf.xml shipped in the  cxf-rt-core 
module, this is one of many cfg files that wire together the CXF 
runtime  - actually its the core cfg file, and you are unlikely to get 
anywhere without it.
ADDITIONALLY, demos may use a cfg file containing application specific 
configuration that overwrites/completes the defaults in the default 
cxf.xml files and the other default cfg files on the class path 
(cxf-extension*.xml). This file is mostly called cxf.xml also, but could 
also be callled "hello-world-secure.xml" or similar to indicate
Both files will be (and must be)  used, and there will be no mix up as 
long as the application speciffic cfg files is not picked up as 
"META-INF/cxf/cxf.xml" (it isn't, all of the demos pick it up as "cxf.xml").
If you want to avoid this potential clash, use the URL form of creating 
a bus (with an absolute file URL).
For the demos however, picking up the application (or demo) specific cfg 
file from the classpath works just fine as it's independent of the 
installation directory (although a relative file URL would do the same).

Hope that helps,

IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

View raw message