On Tuesday 07 August 2007 18:56, mark.boyd wrote: > From another thread on this list it appears that the jaxws:features > tag must be nested within the jaxws:endpoint tag.
Oops. Yep. Sorry for not being more clear on that. That's correct. You are applying that feature to that endpoint. Dan > > 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. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
