Hmm, perhaps I misunderstood. I thought what he was saying was, he wants to obfuscate the method name "whatever", so the log.debug argument has to be changed as well . . .
However, if the value of log.isDebugEnabled can be discovered at compile time (not sure how commons logging works), perhaps conditional compilation (if it exists) would leave this statement out of your distribution class file? Erik -----Original Message----- From: Martin Gainty <[EMAIL PROTECTED]> Sent: Dec 12, 2005 9:19 AM To: Struts Users Mailing List <user@struts.apache.org> Subject: Re: [OT] obsfucating struts web application this is straight from the docs available at http://jakarta.apache.org/commons/logging/apidocs/org/apache/commons/logging/Log.html /*only enable when debug is enabled*/ if (log.isDebugEnabled()) { log.debug("whatever"); } Martin- ----- Original Message ----- From: "su mo" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <user@struts.apache.org> Sent: Monday, December 12, 2005 6:33 AM Subject: Re: [OT] obsfucating struts web application Hi - I tried this approach after my initial question My app uses dispatch action classes with parameter configured to method names. I have used ProGuard and configured in a such a way that public methods of Action classes are left untouched. (no name change) My each "public Action method" has very little info or obvious info from the browser form data handling. I delegated control flow and business logic to private methods. So, I did not need to mess around with renaming struts config entries though it's possible with proguard as it generates some kind of mapping in order to view the stacktrace of an exception My next task is how to hide log.debug("methodName") :) Any ideas? -Regards Sumo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
