Friday, November 16, 2007
JDeveloper does not decompile the class file automaticaly. When you drop a .class in the editor, jdev only provides the class description with methods...not the java code.
Jdev configuration file located in <jdev-home>/jdev/bin/jdev.conf has to be modified to allow jad to be taken into account for decompilation. The following line has to be added at the end of the jdev.conf file.
AddVMOption -Djcncmd=c:/jadnt158/jad.exe -p -b -ff -nl -pi99999 -space -t2 -noinner
Take care to modify the jad path !
When you create an application with GWT and Gear (http://code.google.com/p/gwt-google-apis/), a manifest has to be created to manage offline content.
To minimize the manifest management (and the downloading process) a dedicated manifest has to be created for each browser.
A solution is to use a ServletFilter. This filter will automaticaly return the manifest regarding user's browser.
The filter configuration manages manifest version and resources to be included in the manifest (.css, .html, .gif...).
This filter will only be trigged when the manifest file is requested by Gears.
I hope this solution can help..
Don' t hesitate to post any comments or modifications.