[#XFIRE-377] cannot remove xsd:any and xsd:anyAttribute elements from generated wsdl - jira.codehaus.org

XFire

cannot remove xsd:any and xsd:anyAttribute elements from generated wsdl

Created: 01/May/06 09:47 AM Updated: 06/May/06 05:02 PM Resolved: 06/May/06 05:02 PM

Component/s:

None

Affects Version/s:

1.1-RC1

Fix Version/s:

1.1

Time Tracking:

Not Specified

Description

« Hide

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

Sort Order:

[ Permalink | « Hide ]

Wouter added a comment - 01/May/06 10:11 AM

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).

[ Permalink | « Hide ]

Dan Diephouse added a comment - 03/May/06 01:54 PM

Yes, as you found out this is possible. I think I've changed my mind about having it on by default though - it breaks some tools which can't deal with the UPA stuff.

[ Permalink | « Hide ]

Dan Diephouse added a comment - 06/May/06 05:02 PM

Turned off extensibility by default