The "strong technical reason to do so" was the fact that the name was extremely confusing, in that the class had/has nothing to do with SOAP 1.2. It was misnamed at the start, and we just ddn't get around to fixing it before 1.0. You bring up a valid concern, but I believe this case was justified.
--Glen > -----Original Message----- > From: James M Snell [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 23, 2002 5:57 PM > To: [EMAIL PROTECTED] > Subject: Concerns about renaming files > > > I noticed today that the Axis 1.0 file > DefaultSOAP12TypeMappingImpl was > renamed to DefaultSOAPEncodingTypeMappingImpl in the Axis 1.1 > beta. This > raises an important concern about backwards compatibility. > Before Axis' > initial 1.0 release, renaming files wasn't that big of a > problem, but now > we need to be much more careful or we run the risk of > breaking production > level applications. > > We should NOT be renaming any files unless there is a strong > technical > reason for doing so. Looking at the > DefaultSOAPEncodingTypeMappingImpl > case, the only reason seems to be semantic .. "Rename > DefaultSOAP12TypeMappingImpl to something a little more accurate" > > A bit more care please. > > - James Snell > IBM Emerging Technologies > [EMAIL PROTECTED] > (559) 587-1233 (office) > (700) 544-9035 (t/l) > Programming Web Services With SOAP > O'Reilly & Associates, ISBN 0596000952 > > Have I not commanded you? Be strong and courageous. > Do not be terrified, do not be discouraged, for the Lord your > God will be with you whereever you go. - Joshua 1:9 >
