Hi Isomorphic,
I noticed the following behaviour playing with FileLoader.cacheISC() in SmartGWT v9.0p_2013-10-29/EVAL Deployment. I have this in my html login page (it's a plain page pointing to j_security_check):
FF Developer console shows a HTTP 200/OK for the http://localhost:8080/myproj/myproj/sc/modules/ISC_FileLoader.js.
The calls made by the FileLoader for ISC_Core.js and the other js files all return HTTP 404 because the path used is http://localhost:8080/myproj/myproj/sc/system/modules/ISC_Core.js.
In http://www.smartclient.com/docs/9.0/...ss..FileLoader I did not find a setting for the path to the modules.
Is this a bug or am I missing something?
Best regards,
Blama
I noticed the following behaviour playing with FileLoader.cacheISC() in SmartGWT v9.0p_2013-10-29/EVAL Deployment. I have this in my html login page (it's a plain page pointing to j_security_check):
Code:
<script type="text/javascript" language="javascript">var isomorphicDir = "myproj/sc/";</script> <script type="text/javascript" language="javascript" src="myproj/sc/modules/ISC_FileLoader.js"></script> <script type="text/javascript" language="javascript">FL.cacheISC();</script>
The calls made by the FileLoader for ISC_Core.js and the other js files all return HTTP 404 because the path used is http://localhost:8080/myproj/myproj/sc/system/modules/ISC_Core.js.
In http://www.smartclient.com/docs/9.0/...ss..FileLoader I did not find a setting for the path to the modules.
Is this a bug or am I missing something?
Best regards,
Blama
Comment