Hi Benson, Here is an important thing that CXF bus will try to find the extensions component's configuration with the name start with 'cxf-extension' in the class path when the bus is loading.
Since cxf-servlet transport conflicts with jetty http transport and we do not want to use the cxf-servlet as default transport, cxf-servlet.xml's name is not start with the 'cxf-extension'. cxf-extension-http just includes some http client side components, if the user want to use cxf http client, he do not need to include the jetty http transport module. Willem. -----Original Message----- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 21:17 To: [email protected] Subject: Adding extensions, howto? (what's up in rt/transports/http) If someone will please answer the following, I'll put it in the wiki. rt/transports/http has both a cxf-extension-http.xml and also a cxf-servlet.xml, with differnt contents. Why?
