Yeah, sorry for pointing the only one out that has not been deprecated. Imho depreciation only means 'be aware, method will not be supported in the near future', it does not imply that usage of these methods will result in some kind of failure. So either these methods stay deprecated but usage does not result in exceptions being thrown, or they should be removed completely.
roger -----Original Message----- >From: Ilkka Priha > Hmm, you're right, but maybe that one should also be deprecated. Both >addOrderByAscending(<field>) and addOrderByDescending(<field>) were deprecated >in 1.25 and replaced by the corresponding Query methods (as were all GroupBy >methods). They still call internally addOrderBy(<name>,<direction>), which is >currently not deprecated. Looks like illogical to me and is the cause of >problems you and others have encountered. ************************************************************************* The information contained in this communication is confidential and is intended solely for the use of the individual or entity to whom it is addressed.You should not copy, disclose or distribute this communication without the authority of iBanx bv. iBanx bv is neither liable for the proper and complete transmission of the information has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
