Ooooops, sorry!!

I see the "client" element is not top-level, but a child of "conduit"!

<slinks away>



Cornel Masson wrote:
I'm trying to use the "http-conf" schema (http://cxf.apache.org/transports/http/configuration) in my cxf.xml to configure the HTTP connection properties of my client. However, at runtime I get this Spring error:

"Cannot locate BeanDefinitionParser for element [client]"

I found that strange since I know all the schemas, as well as spring.handlers & spring.schemas, are inside the CXF jar (cxf-2.1.4.jar) so there could hardly be a classpath issue. Then I searched through the entire CXF 2.1.4 source code to look for the NameSpaceHandler that registers the BeanDefinitionParser for the 'client' element: guess what - I couldn't find any! I found org.apache.cxf.transport.http.spring.NamespaceHandler, but that only registers the following:

       registerBeanDefinitionParser("conduit",
new HttpConduitBeanDefinitionParser()); registerBeanDefinitionParser("trustDecider", new MessageTrustDeciderBeanDefinitionParser()); registerBeanDefinitionParser("authSupplier",
               new HttpAuthSupplierBeanDefinitionParser());
       registerBeanDefinitionParser("basicAuthSupplier",
new HttpBasicAuthSupplierBeanDefinitionParser());
       registerBeanDefinitionParser("destination",
               new HttpDestinationBeanDefinitionParser());

...but nowhere is a parser for the "client" element registered. It's in the XSD, but no BeanDefinitionParser. Huh?? Am I going mad or is something wrong here?

Thanks
Cornel

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

Reply via email to