[ http://issues.apache.org/jira/browse/AXIS-1976?page=comments#action_65468 ] Brian Nielsen commented on AXIS-1976: -------------------------------------
Thanx, for the quick-fix, I've just use 2 hours+, figuring out what the heck happende between RC3 and Final. I have a Web Service, done by XSD/WSDL first, WSDl2Java and then some variations on in the server-config.wsdd. I tried out the RC2, RC2, Final and 1.2.1 (15/5-2005) and the old ones RC2 and RC3 works correctly but with the later ones i get these nasty xsi:types in my response message. I've also tried fiddeling with the different wsdd-configurations. This is a problem since I'm using a handler to validate the messages against my schemas, and the validating parser (xerces dom-level3) find this incompatible. Hopefully someone can figure out a testcase so that this regression won't happen again. Bye the way i run axis-to-axis. Regards Brian > dotnet_soapenc_bugfix is "blindly" reset > ---------------------------------------- > > Key: AXIS-1976 > URL: http://issues.apache.org/jira/browse/AXIS-1976 > Project: Axis > Type: Bug > Components: Basic Architecture > Versions: 1.2 > Environment: not really important > Reporter: clint dovholuk > Priority: Blocker > > org.apache.axis.encoding.TypeMappingRegistryImpl.doRegisterFromVersion(String > version) "blindly" resets the dotnet_soapenc_bugfix. > generated a bunch of classes based on a .NET web service > set the dotnet_soapenc_bugfix flag in server-config.wsdd but the > autogenerated class ALL call: > > ((org.apache.axis.client.Service)super.service).setTypeMappingVersion("1.2"); > which eventually will call doRegisterFromVersion with "1.2" (or sometimes > null though i didn't track THAT down) > this blindly overrides the flag as set in the server-config.wsdd file. > I can't believe this is "on purpose" > suggest looking for the flag in the server-config.wsdd and setting some > system flag stating that it's specified and to NOT re-set it? > thanks, > -dovholuk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
