-
17 Mar 2012 4:28 PM #1
Control over Ext.Loader config options
Control over Ext.Loader config options
I find debug breakpoints are lost after deploying a project. The problem seems to be because the Ext.Loader prefers to disable caching which then seems to cause the browsers to forget any debug break points. If I add
disableCaching: false;
to the loader's setConfig options in designer.js then I'm able to debug until designer.js is re-generated. What am I doing wrong? Is there an option in the designer i can set to have it generate the extra loader configuration I seem to need. Is there an better way to be debugging?
-
18 Mar 2012 11:17 AM #2
Mmmm....
Rather than a property in the application may be different deploy and lauch options:
Launch/Deploy with loader enabled / cache disabled (current behaviour)
Launch/Deploy with loader enabled / cache enabled
Launch/Deploy with loader disabled
And make an application's option which one you want when just click launch or deploy.
Regards.UI: Sencha Architect 2.x / ExtJS 4 MVC
Server side: EJB 3.1 / CDI / JPA 2 / JAX-RS / JasperReports
Application Server: Glassfish 3.1.x
Databases: Oracle 10g & 11g / DB2 9 & 10 / Firebird 2.5
If you like my answer please vote!


Reply With Quote