2006/8/16, Werner Punz <[EMAIL PROTECTED]>:
First of all sorry for having been absent for a while
due to health reasons. I will try to be more present
in the immediate future.

Welcome back.

The best way, given from what I can remember about the namespace issue
is to simply extend the dojo namespace.
This however is probably not possible in your case unless you are
willing to roll your own myfaces.
What we did was to bend the resource loading mechanisms
myfaces already had in place to our own namespace within
the myfaces structure and adjusted our own dojo based
component classes to that namespace (check the code for that
it was more or less a trial and error on my side til things
started to work, due to lack of documentation on this issue back then).

The lack of documentation is the sad part.

I am not entirely sure since I do not know the current status
of the resource loading if stuff like that works from a different
jar as well, you can give it a try however.
But as I said it is probably the easiest to just add your
stuff to the dojo namespace, this is the recommended
way by the dojo people for now until the entire
namespacing issue is more or less fixed (rolling
your own namespaces is not fully documented
and not very well working to my knowledge)
I have not checked out the current dojo version in this regard
if the entire namespacing issue has been fixed.

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.

Reply via email to