DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15764>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15764 API changes break backwards compatibility with Axis 1.0 ------- Additional Comments From [EMAIL PROTECTED] 2003-01-06 19:18 ------- Just to chime in here, Axis 1.0 is still *very* fresh. I am all for preserving as much backwords compat as the next person, but I don't think we want to jump off the cliff here. Our shipped product is SOURCE and I want that source to be as clean and easy to read/understand as possible. Axis isn't at that point yet, so I don't think that most classes fall under the "can never go away" category yet. For instance, I don't think that DefaultSOAP12TypeMappingImpl is a class name that should live forever. I DO think that, for instance, AxisServlet should remain as stable as possible because it makes sense that many people have extended it. I also think the Emitter class API needs to remain stable, because many people are using it. Lets not break people when we can help it, but Axis is still in flux and is in no way done, nor are its interfaces set in stone.
