Amit Rana wrote:
> Hi,
>
> Since I was getting error as "Couldn't load file: ..", so searching in
> apiviewer-0.js revealed a code snippet :
>
> var M=new qx.io.remote.Request(L);
> M.addListener(D,function(N){this.error("Couldn't load file: "+L);},this);
>
> So, I tried a simple code :
>
> var L =
> "http://localhost:8080/Chiron/js/spagobi/api/script/qx.Class.js";;
> var M=new qx.io.remote.Request(L);
> M.addListener("failed",function(N){this.error("Couldn't load
> file: "+L);},this);
> M.addListener("completed",function(N){this.error("Loaded file:
> "+L);},this);
> M.send();
>
> This gives console output as Couldn't load file ....
>
> And, var L =
> "http://localhost:8080/Chiron/js/spagobi/api/script/qx.class.js";;
> gives output as Loaded file ...
>
> I know that this had to work because files on server are with
> lowercase names. But, if its not a case-sensitive issue, then why is
> the server giving me Error 404.
> Now, how to solve this for the server (online access) and why the
> local file (offline access) work's are the real mysteries for me. :-)
No, it only shows that you cannot compare online with offline access, as
I suggested. Go back to online access and try the direct loading of the
apiviewer app ... and then tell me again, like you did before, it is
working while the access through a link is not! (I wouldn't belive it...).
And, I'm still wondering why this "/Chiron/..." path suddenly comes into
play...
T.
>
> thron7 wrote:
>> Amit Rana wrote:
>>
>>> My Application start page is :
>>> http://localhost:8080/MyApplicationName/ (which shows the server's
>>> index.html)
>>>
>>> This index.html has the link to API as :
>>> <span class="local"><a
>>> href="myJSfolder/custom/api/index.html"><b>Open API
>>> viewer</b></a></span>
>>>
>>> Clicking on this shows the URL on browser as :
>>> http://localhost:8080/MyApplicationName/myJSfolder/custom/api/index.html
>>>
>>> This index.html has code as :
>>> <script type="text/javascript" src="script/apiviewer.js"></script>
>>>
>>> Firebug console says :
>>> GET http://localhost:8080/Chiron/js/spagobi/api/script/qx.Class.js
>>>
>>
>> THIS ^^^^ is very suspicious! Why is there a request to a URL with
>> server path starting with "/Chiron/js/...", when we are in a path
>> that starts with "/MyApplicationName/..."?!
>>
>> - Clear your browser cache.
>> - Clear any server cache you might have.
>>
>>
> Sorry Thomas, the firebug console error is not
> GET http://localhost:8080/Chiron/js/spagobi/api/script/qx.Class.js
> (was trying with a dummy application earlier)
> but
> GET
> http://localhost:8080/MyApplicationName/myJSfolder/custom/api/script/qx.Class.js
>
>
> with response as :
> The requested resource
> (/MyApplicationName/myJSfolder/custom/api/script/qx.Class.js) is not
> available.
>>
>>> with response as : The requested resource
>>> (/MyApplicationName/myJSfolder/custom/api/script/qx.Class.js) is not
>>> available.
>>>
>>> And, when I go to :
>>> http://localhost:8080/MyApplicationName/myJSfolder/custom/api/script/
>>> in browser URL, I see a list of files with qx.class.js as one of them.
>>>
>>>
>>> I went into : qooxdoo-0.8-sdk\component\apiviewer and did a
>>> generate.py source.
>>
>> Why would that help? Aren't you trying to browse a custom api viewer,
>> built in your own project with "generate.py api"?!
>>
>>
> I just wanted to test if the files generated are with lower/upper case
> (because qooxdoo-0.8-sdk\framework\api\script has the files with
> uppercase which got ma confused)
>>> It also generated a script folder with classes in lowercase
>>> (qx.class.js) and calling index.html works.
>>>
>>
>> You're using Windows, so capitalisation doesn't matter.
>>
>>
> I agree as the offline access works fine. I need to solve how.
>>> I created a dummy index.html and called
>>> qooxdoo-0.8-sdk\component\apiviewer\index.html and that too works.
>>> Then, from dummy index.html, I called
>>> MyApplicationName/myJSfolder/custom/api/index.html and that works too.
>>>
>>> So, the problem occurs only when data is on server. I am trying to
>>> dig into that.
>>>
>>
>> Yes, there is not much use in testing against an offline access
>> (file:// protocol). You have to test and compare online access.
>>
>> T.
> I tried the same with online access but no success. I got the same
> error. I have to set some path in a file (mostly apiviewer-0.js and
> via config.json) but not able to get that. :-(
>
> amit
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
