Thomas Dudziak wrote:
On Mon, 8 Mar 2004, Edson Carlos Ericksson Richter wrote:
I don't want to start a fight. Ok, in programming world has several (thousands, maybe million) of ways to do exactly same work using same language. But I have more than 120000 lines of code based in the suppose that a method of my bean will be called even if it's a proxy (and toString is one of this method). This is a basic supposition for the Java language at all: a proxy must be a transparent approach to my real object.
I think this is a proper use (and Charles didn't say differently). In fact, the 'fix' to allow the use of toString without materializing the proxy is in error here. I mean, toString is a regular method of an object just like any other method, so calling it should result in materializing the proxy. I'd rather fix the logging in OJB here, e.g. using a ProxyHelper.toString method which returns "unmaterialized proxy for ..." when its an OJB proxy, and calls the normal toString method if its not a proxy. This probably means quite a few changes to OJB, but I think this the 'better' way.
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
