Hi, I have a soap web service served from a .net app. Sometimes we add fields to some of the objects but these are always optional and from a XML/HTTP standpoint the xml tags that represent those fields could be left out and it works fine. (like say we have user with a firstname and lastname and we add middle name). This should let existing users of the web services keep working.
and this is exactly how it does work for almost everyone. Clients using .net, python, ruby etc all have no problem with this. But any change at all seems to break anyone using Axis. It seems that on every request Axis checkes the endpoints WSDL and verifies that it is EXACTLY like the stubs it has. If not then it throws an exception (unexpected subelement). Our clients are very frustrated with this because they have to get a developer to regenerate the stubs every time we add something (and they often do not care about the addition). Our product management is frustrated because they have to give our clients 2 months warning before they add a field (again...just it seems for clients using axis). Our customer support is frustrated because the clients don't listen to our warnings and then after the release they get angry calls rom the customers because the web services are broken. Is there any simple option in Axis to turn this feature off and have Axis just assume it's current stubs are correct? If not is this planned for the future? Thanks Ryan Bergman --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
