I did a pass through and added the logging guards and fixed the message calls that I found. If you or anyone else sees any other issue, please let us know. Thanks.
On Sun, May 30, 2010 at 3:07 PM, Jason Dillon <[email protected]> wrote: > On May 30, 2010, at 6:27 AM, Bryant Luk wrote: >> This will take some more time than I have right now but just to give >> some reasoning why {} was changed to {0}, it's because messages with >> multiple parameters can have their ordering switched if a translation >> is done of the message file (i.e. the first parameter to logger.info >> could wind up being the 2nd parameter in the message). > > Thats, fine, then just be sure to guard all logging calls. > > --jason > > >
