>From another thread on this list it appears that the jaxws:features tag must be nested within the jaxws:endpoint tag.
Mark Dan, Can you shed light on the jaxws:feature tag. I tried this and I get: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 37 in XML document from ServletContext resource [/WEB-INF/beans.xml] is invalid; nested except ion is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jaxws:features'. Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jaxws:features'. I looked at the spring.handlers in cxf-2.0-incubator.jar and the registered handler class is org.apache.cxf.jaxws.spring.NamespaceHandler which only registers handlers for endpoint, client, and server. So is jaxws:feature a new feature on the way that isn't in 2.0 as yet? Thanks. Mark dkulp wrote: > > ... > 3) Any chance of getting a tcpdump of the response? I'd like to know if > the data is on the wire or not. Since you seem to be using spring > config on the server, you could just try adding: > <jaxws:features> > <bean class="org.apache.cxf.feature.LoggingFeature"/> > </jaxws:features> > and looking at the log output. > > > -- View this message in context: http://www.nabble.com/CXF-server-with-XFire-generated-client---problem-with-returning-a-type-DataHandler-with-MTOM-tf4222406.html#a12044166 Sent from the cxf-user mailing list archive at Nabble.com.
