[ http://jira.codehaus.org/browse/XFIRE-377?page=comments#action_64485 ]
Wouter commented on XFIRE-377: ------------------------------ OK, so we kind of found out how to accomlish this - so no bug, but documentation isn't quite up to date / easy to grasp In the end, we removed services.xml, defined Spring dispatcher servlet in web.xml, added an xfire-servlet.xml containing service definitions and xfire configuration (overriding the already defined typeMappingRegistry). Kind of: Spring exporter + Advanced configuration (where CommonsAnnotations has been replaced by jsr181WebAnnotations). > cannot remove xsd:any and xsd:anyAttribute elements from generated wsdl > ----------------------------------------------------------------------- > > Key: XFIRE-377 > URL: http://jira.codehaus.org/browse/XFIRE-377 > Project: XFire > Type: Bug > Versions: 1.1-RC1 > Reporter: Wouter > Assignee: Dan Diephouse > > > Although following the steps as described in issue XFIRE-295, I still get > xsd:any and xsd:anyAttribute in the generated wsdl. > I tried both adjustng the typeMappingRegistry bean definition in the > xfire-all jar and overriding the typeMappingRegistry in my > applicationContext.xml and/or services.xml > Strange thing is: my debugger DOES show the configuration values to be > defaultExtensibleElements = false > defaultExtensibleAttributes = false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
