Rogerio Pereira schrieb:
The resource loading itself works well, but i think that's no chance to
have a module in another jar since dojo requires the modules in a
relative path from dojo source tree, as you already know, this isn't
changed in the last version of myfaces.
Ok, I had a good nights sleep over this.
Afair it still is possible.
The resource loading from myfaces should resolve that problem.
Following, we have our own dojoized classes outside of the dojo
hierarchy, I doubt jars are the issue here.
Dojo itself resolves the namespaces over urls not over files
so once you have dojo on your client all the other
classes are loaded relatively to your dojo root.
But that does not happen on jar level it happens on uri level.
You can move your own classes outside of the dojo hirarchy
relatively to dojo afair, by using the myfaces resource loading
mechanisms. Jars are a non issue in this case, in my opinion.
All I can say is check out some of the dojoized components
of myfaces.
while some of them only consume dojo some of them really
use the class mechanisms and component mechanisms, and they
use relative paths, starting from the dojo hierarchy into
the local package hierarchy.
The most important part is, if you define those paths
on the dojo side you have to have in mind that all of
this is loaded over relative urls which then have to root
into your javasources.
(I will again have a deeper look into those issues
tomorrow when I do the dojo upgrade, then I will have
more infos on this and how I did it, it probably was something
like <dojo resource class>/../<my own resource class>/dojo javascript
class)>
But as I said the easiest way to kickstart probably is to bypass all
of this and add your dojoized javascripts to the dojo class hierarchy
itself vial a build process (which for now is the preferred way
by the dojo people as it seems)
