of course. Exactly, Your Answer is correct. When Cxf is installed, CXF is in need of dependency Jars.
In My Case, Dev Server can access the internet, But Operation Server didn't allowed to access the internet. and I was installed CXF by hand. in Other Case, It have a problem with installing CXF. Thank you for your answer 2015-08-20 15:37 GMT+09:00 Christian Schneider <[email protected]>: > > > Am 20.08.2015 um 05:49 schrieb 이듀이: > >> Second Step. add Install CXF ( if already have installed, pass it) >> >> if you use Karaf or you don't find CXF you should add Install CXF >> >> 1. copy feature.xml (apache-cxf-3.0.2-features.xml) to system directory >> >> >> \system\org\apache\cxf\karaf\apache-cxf\3.0.2\apache-cxf-3.0.2-features.xml >> >> 2. copy jars ( cxf ) to system directory >> >> system\org\apache\cxf\* >> >> >> 3. edit etc/org.apache.karaf.features.cfg >> >> you must add features.xml at featuresRepositories >> and must add feaures Name (cxf) at featuresBoot >> >> You should not copy the dependencies by hand. > > If you do not mind that cxf is downloaded from the internet (or your local > maven repo or nexus) then simply do this: > feature:chooseurl cxf 3.0.2 > feature:install cxf-jaxws > > If you want everything to be self contained then create a custom karaf > distribution like servicemix does. > There you use maven and the karaf maven plugin to create a custom system > dir that contains all necessary jars and feature files. > Copying the files by hand would be extremely error prone. > > For example you described to copy only the org/apache/cxf jars. CXF neeeds > a lot of jars outside that namespace though. So you would end with an > inconsistent system where only > parts of cxf dependencies are installed locally. > > Anyway I would not start with this part. When learning to work with smx or > karaf it is good enough to install cxf using the command line. The self > contained distribution is typically only relevant for production > deployments. > > Christian > >
