Hi Alexander
After hours of debugging, I think I found the problem, and I think it is a bug of the 0.8.1 To be short, the cohabitation of many libraries beggining with the same radical for namespace make the uri generation fail in source mode.

*How to test*
I don't know if you can test this : just try to use in a same application two libraries whom namespaces both begin with "org", or "qx", or whatever. You will notice that the last library declared in the config.json will "override" the uri for the first library classes : thus, these classes are not found (source mode only).

*Why?*
+ Already in the 0.8, whatever the namespace was declared in Manifest.json, the detected namespace of a library like "org.argeo.slc" was always "org" (as printed in the debug instruction of LibraryPath.py line 103 ) + This was apparently not really problematic, until 0.8.1 where the Generator.py file seems to make reference to the detected namespace to choose which uri to use for a given class when generating the source script. Line 1337 lib = self._libs[self._classes[fileId]["namespace"]] + Solving : for me, I can solve this by using the previous 0.8.0 Generator.py instructions :
cUri = Path.rel_from_to(self.approot, self._classes[fileId]["uri"])
cUri = Path.posifyPath(cUri)
but there was surely a good reason for the latter changes!

*Result : *
For me it's a bug, but perhaps once again I missed something and a namespace cannot be something like "org.something.somethingelse" ? This problem does not appear in build mode, I don't know why, did not investigate this case. If you want I can enter a bug, but maybe someone more python expert than me should do it?

Cheers

Charles


Alexander Back a écrit :
Hi Charlie,

Charlie wrote:
Hi Alexander
Thanks for your answer. As shown in the config.json, a given class file called TestList.js (and defining the class"org.argeo.slc.web.TestList"), defined in the "slc-web" library should appear as
"argeo-ria-lib/class/org/argeo/slc/web/TestList.js"
and appear as
"./class/org/argeo/slc/web/TestList.js" in the firebug network tab.

That's why I suspect that my URI is not correctly computed. At the build time, the library is correctly detected and analysed, so absolute path is indeed working.
It is the same result if I declare or not the "uri" key in the config.json

Phew, these infos are quite much, but I think the best way to get a solution is that you try to explain me your setup.

* In which directory is your application located at the harddrive?
* What is the URI you are loading your application (path to your index page where the JS file is included)
* Where do you store the JS files at the server (the URIs to them)


Another hint:
With the new features of the generator you do not have to repeat the whole job in your "config.json" if you just want to add/overwrite one piece.

--snip--
// original job from "base.json"
"source-script" :
{
    "desc"    : "create includer script of current application",

    "extend" : ["common"],

     "compile-source" :
     {
       "file" : "${ROOT}/source/script/${APPLICATION}.js",
       "locales" : "${LOCALES}",
       "root" : "source"
     }
}

// overwriting "file" and "root" looks like
"source-script" :
{
    "extend" : ["common"],

     "compile-source" :
     {
        "file" : "${ROOT}/script/${APPLICATION}.js",
        "root" : "${ROOT}",
     }
}
--snip--

This also works for all other keys. This should minimize your "config.json" and you'll also get a better overview of what you customized.

cheers,
   Alex

------------------------------------------------------------------------------
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
qooxdoo-devel@lists.sourceforge.net
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
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to