I generally doubt that this is undefined/unintended! Of course Object methods cannot get intercepted, but they must be delegated 1:1 through to the underlying instance. And that's exactly where this log statement sits.
LieGrue, strub --- On Thu, 9/23/10, Eric Covener <[email protected]> wrote: > From: Eric Covener <[email protected]> > Subject: Re: [DISCUSS] remove logging for "Calling method on proxy is > restricted except Object.toString()" > To: [email protected] > Date: Thursday, September 23, 2010, 2:25 PM > On Thu, Sep 23, 2010 at 10:14 AM, > Mark Struberg <[email protected]> > wrote: > > hoi! > > > > Just for cleaning this up finally. > > > > Our InterceptorHandler contains a log.trace with the > following wording: > >> logger.trace("Calling method on proxy is > restricted except Object.toString(), but current method is > Object. [{0}]", methodName); > > > > Is this really a problematic situation? > > > > I mean this ALWAYS happens if a bean gets stored in a > Map or any other situation where equals() or hashCode() is > being invoked. > > > > I'd strongly favour to remove this logging. > > > > I wonder if we could note it in the log once per Bean type, > so we know > that the app is using the undefined behavior Object > methods. > > -- > Eric Covener > [email protected] >
