Re: -XdisableClassMetadata compiler flag - Was [Re: Hiding fully qualified class name sent to the browser]
-XdisableClassMetadata cut off from the compiled code all class metadata as SomeInstance.getClass().getName(); - this won't be available *But I am not sure that it will completely remove the classes names from the compiled code, cause it also uses them on rpc calls * 2010/7/7 moorsu moo...@gmail.com Hi, I tried to use the compiler flag *-XdisableClassMetadata* to replace the classnames as suggested by Olivier. But the classnames still appear in the *.cache.html files. I tried both in maven POM.xml also in the Google Eclipse Plugin. My POM.xml code snippet like this plugin groupIdorg.codehaus.mojo/groupId artifactIdgwt-maven-plugin/artifactId version${gwt-maven-plugin.version}/version configuration disableCastCheckingtrue/disableCastChecking disableClassMetadatatrue/disableClassMetadata resourcesOnPathfalse/resourcesOnPath runTargetsrc/main/webapp/index.html/runTarget webappDirectorysrc/main/webapp/webappDirectory styleOBF/style extraJvmArgs-Xmx2048m -Xss4024k/extraJvmArgs /configuration executions execution goals goalcompile/goal /goals /execution /executions /plugin What is the right way to achieve this? thanks moorsu. On Wed, Jun 23, 2010 at 8:50 PM, Olivier Monaco olivier.mon...@free.frwrote: Hi, If your problem comes from class name included in the JavaScript files (and affected to some properties of JavaScript object), you can try to use the following optimization: http://code.google.com/p/google-web-toolkit/wiki/NoClassMetadataOptimization Olivier On Jun 22, 3:55 pm, moorsu moo...@gmail.com wrote: Hi, Would it be possible to obfuscate the fully qualified class name which is visible at the browser if you use firebug?. I would like to see it as a.b.c.d instead com.mycompany.myproduct.mypackage.MyClassName. Also I do not use the same domain object as model but use Lists and Maps to send data to browser. thanks! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- http://gwtupdates.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: -XdisableClassMetadata compiler flag - Was [Re: Hiding fully qualified class name sent to the browser]
On 7 juil, 15:03, Gal Dolber gal.dol...@gmail.com wrote: -XdisableClassMetadata cut off from the compiled code all class metadata as SomeInstance.getClass().getName(); - this won't be available *But I am not sure that it will completely remove the classes names from the compiled code, cause it also uses them on rpc calls ...unless you also inherits name='com.google.gwt.user.RemoteServiceObfuscateTypeNames' / -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: -XdisableClassMetadata compiler flag - Was [Re: Hiding fully qualified class name sent to the browser]
Good to know! thanks! 2010/7/7 Thomas Broyer t.bro...@gmail.com On 7 juil, 15:03, Gal Dolber gal.dol...@gmail.com wrote: -XdisableClassMetadata cut off from the compiled code all class metadata as SomeInstance.getClass().getName(); - this won't be available *But I am not sure that it will completely remove the classes names from the compiled code, cause it also uses them on rpc calls ...unless you also inherits name='com.google.gwt.user.RemoteServiceObfuscateTypeNames' / -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- http://gwtupdates.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
-XdisableClassMetadata compiler flag - Was [Re: Hiding fully qualified class name sent to the browser]
Hi, I tried to use the compiler flag *-XdisableClassMetadata* to replace the classnames as suggested by Olivier. But the classnames still appear in the *.cache.html files. I tried both in maven POM.xml also in the Google Eclipse Plugin. My POM.xml code snippet like this plugin groupIdorg.codehaus.mojo/groupId artifactIdgwt-maven-plugin/artifactId version${gwt-maven-plugin.version}/version configuration disableCastCheckingtrue/disableCastChecking disableClassMetadatatrue/disableClassMetadata resourcesOnPathfalse/resourcesOnPath runTargetsrc/main/webapp/index.html/runTarget webappDirectorysrc/main/webapp/webappDirectory styleOBF/style extraJvmArgs-Xmx2048m -Xss4024k/extraJvmArgs /configuration executions execution goals goalcompile/goal /goals /execution /executions /plugin What is the right way to achieve this? thanks moorsu. On Wed, Jun 23, 2010 at 8:50 PM, Olivier Monaco olivier.mon...@free.frwrote: Hi, If your problem comes from class name included in the JavaScript files (and affected to some properties of JavaScript object), you can try to use the following optimization: http://code.google.com/p/google-web-toolkit/wiki/NoClassMetadataOptimization Olivier On Jun 22, 3:55 pm, moorsu moo...@gmail.com wrote: Hi, Would it be possible to obfuscate the fully qualified class name which is visible at the browser if you use firebug?. I would like to see it as a.b.c.d instead com.mycompany.myproduct.mypackage.MyClassName. Also I do not use the same domain object as model but use Lists and Maps to send data to browser. thanks! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.