-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
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
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
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
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
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
