Forum Discussion
toehser
17 years agoNew Contributor
Huh. Well, fixing it may be problematic for a couple of reasons, one being that that service is written and owned by a different team (same division at least...), the other being that really Axis2 is doing the generation, so it is probably an Axis2 bug. Maybe when I rev the version of Axis2 jars which I'm going to do anyway it will just "go away"... I think it is Axis2-1.3 that generated the XML.