-100 This is a really inappropriate solution to the problem of running cxf, at least on trunk where kar files work pretty well ( I don't know about 2.x).
Here are a couple IMO more appropriate solutions that avoid including cxf-specific goo to confuse all non-cxf users. (I'm not trying to be mean to cxf, I don't think we should include any consuming project specific configuration)
1. Pack up all of cxf in a kar file including (in resources/etc/jre.properties or whatever files are appropriate) so that when the kar is installed, the etc files are as appropriate for cxf.
2. Just put the configuration files (jre.properties) in such a kar and let the user try to figure out how to install the rest of cxf by themselves.
Working with Geronimo I've verified that these ideas work if you construct a custom assembly and install the app-specific kar after the karaf framework kar. I haven't tried just installing a kar in an already built server, but I think it would work too.
Also a link to Dan's blog about this would be helpful.