Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1-RC1
-
Fix Version/s: 1.1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
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
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).