The HTTP "conduit" element is handled by the org.apache.cxf.transport.http.spring.NamespaceHandler, which registers the HttpConduitBeanDefinitionParser for the "conduit" element. The HttpConduitBeanDefinitionParser takes care of parsing the "security" namespace configuration inside the "conduit" Element - there is not a separate Spring NamespaceHandler for the security schema.
I don't know enough about using groovy in this way to say if there's a workaround for the problem you have encountered, sorry. Colm. On Tue, Jul 3, 2018 at 5:03 PM, boca2608 <[email protected]> wrote: > Hi Colm, > > Thank you very much for taking time to help. > > The reason why I used the org.apache.cxf:cxf-common-schemas:2.3.11 was > that > according to CXF docs, this package contains the namespace handler for cxf > security, and that the latest version of this package (according to Maven) > is 2.3.11. In any case, I tried to use CXF 3.2.5 but received the same > error. It seems that XmlBeanDefinitionReader tried to create the > defaultNamespaceHandlerResolver using the default handler mappings > location > (META-INF/spring.handlers). This created the map I included in the > original > post which contains most CXF namespace handlers, except for the security > one. > > Thanks! > > > > -- > Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
