[ http://jira.codehaus.org/browse/XFIRE-377?page=all ]
Dan Diephouse updated XFIRE-377:
--------------------------------
Fix Version: 1.1
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.
> 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
> Fix For: 1.1
>
>
> 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