The main thing is that why does calling "generate.py api" generate files
in lowercase.
Tracing the "generate.py api", I found that eventually the "build-data"
job of qooxdoo-0.8-sdk\component\apiviewer\api.json file is called which
in turn runs the "api" job on python generator. This generates all the
data files (class files) in the custom/api/script folder (like
qx.class.js etc).
Now, since I don't know much about python, so I cannot explore how this
job runs internally by python and why does it generate files in
lowercase instead of uppercase.
Now, I have 2 options:
1. Know the internal working and try to generate files in uppercase.
2. Understand how offline access is able to resolve case name and
implement similar thing for server.
amit
P.S. : Pretty strange that only I faced this issue =-O
Amit Rana wrote:
Hi Thomas,
I know I have been bombarding you with queries. But, thanks a lot for
replying back. Its just that I have been working on this API issue
since days without much success. :'(
Please find my comments below.
thron7 wrote:
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.
Ah, sorry, I didn't spot your other comments on first sight... So it's
really all about capitalization of resource names in the online access.
Yes, it looks capitalization issue to me.
I tried the same with online access but no success.
Ok, that gives me some relief that the behaviour is consisten for any
kind of online access - that is good.
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. :-(
I don't think that messing with the generated qooxdoo application will
get you far. You can of course, just for testing, edit the
script/apidata.js and convert all 'fullName' entries to all-lower case,
in the hope that the generated URLs will then work. But this is just a
vague guess, and a dead end at this. qooxdoo class and file names are
aligned and usually work nicely together.
This is working. I changed "qx.Class" in apidata.js to "qx.class" and
its working (when i click on Class node, I see the information). So,
maybe I need to see how apidata is being generated.
The real problem seems to be your web server. Which server are you
using? Why does it force all lower-case names when looking for resources
on the file system? Is this configurable?
T.
I am using Tomcat server v5.0 in Eclipse v3.3.1.1. I will try to
explore the searching of files problem in my server settings.
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
