To my knowledge, these methods may have been put in place for possible future implementation. However, the fact that they are not implemented means, no one can really use them. So it is best to remove them till the methods are properly implementd, whithout confusing users.
+1 for removal. Thanks, Samisa... On Mon, 17 Jan 2005 08:14:56 +0000, John Hawkins <[EMAIL PROTECTED]> wrote: > > Anyone got an opinion on removal of these methods - or how come they're in > this state? > > John Hawkins > > > > > Andrew Perry2/UK/[EMAIL PROTECTED] > > 14/01/2005 16:10 > Please respond to > "Apache AXIS C Developers List" > To"Apache AXIS C Developers List" <[email protected]> > cc"Apache AXIS C Developers List" <[email protected]> > SubjectRe: SoapSerialiser > > > > > > > > > > > > > The same seems to be true for IHandlerSoapDeSerializer > > virtual xsd__hexBinary AXISCALL getBodyAsHexBinary()=0; > virtual xsd__base64Binary AXISCALL getBodyAsBase64Binary()=0; > virtual AxisChar* AXISCALL getBodyAsChar()=0; > > These are only partially implemented or not implemented and should be > removed from the public API until the implementation is complete. > > The getBodyAsChar() method also has a malloc() in it which shouldn't be > used. For memory allocation news should be used. This method seems to be > 'in progress' and not finished. > > Regards, > > Andrew Perry > IBM Web Services Client for C/C++ > [EMAIL PROTECTED] > Mail Point 127 > IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN > Tel. Internal 249828 External + 44 (0)1962 819828 > Fax. + 44(0)1962 818080 > > John Hawkins/UK/[EMAIL PROTECTED] wrote on 14/01/2005 15:29:31: > > > > > +1 for removing. > > > > Nobody has requested this function and there is no impl. > > > > > > John Hawkins > > > > > > > > > > > Andrew Perry2/UK/[EMAIL PROTECTED] > > 14/01/2005 15:19 > > > > Please respond to > > "Apache AXIS C Developers List" > > > > To > > > > [email protected] > > > > cc > > > > Subject > > > > SoapSerialiser > > > > > > > > > > > > > > > > > > I've been writing handler tests to test the public APIs available to > > handlers and have come across several of the public APIs which have empty > > implementations in the code and //TODO comments. > > > > Is there a plan to actually implement these methods? > > > > I feel that these methods should not be in the public API and should be > > removed until there is an implementation behind them. > > > > Examples of these are : > > > > IHandlerSoapSerialiser->getBodyAsString > > IHandlerSoapSerialiser->setBodyAsHexBinary > > IHandlerSoapSerialiser->setBodyAsBase64Binary > > > > > > Regards, > > > > Andrew Perry > > IBM Web Services Client for C/C++ > > [EMAIL PROTECTED] > > Mail Point 127 > > IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN > > Tel. Internal 249828 External + 44 (0)1962 819828 > > Fax. + 44(0)1962 818080 > > > > >
