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:35 ------- Tom, I agree that SOME classes can be changed, but there are some that should not be. The Eclipse article makes the distinction nicely. What we need in Axis is to make a distinction between those classes that are part of the user API and those classes that are "Axis Internal". "Axis Internal" classes should never be used by end users, or at least, should only be used with a certain amount of incurred risk. We should not, however, be seeing changes to user API's that break existing clients. Of course, this is a bit difficult to do since many of the interfaces that were originally in Axis have been replaced with class implementations (a very bad design decision that we cannot easily undo). In any case, regardless of how long Axis 1.0 has been out, it is still gold code and care needs to be taken.
