Definitely not a good idea to fix scope only for ajax.py module
Opened this issue · 1 comments
alfishe commented
- Fixing module name is really bad and prevent dajax/dajaxice usage in properly architectured and complex applications
- Silent (without even logging the fact) failing to obtain any registrations causes false understanding that component isn't working at all.
At least explicitly mention fact that ONLY ajax.py module in application root can work.
there is a workaround - specify import explicitly in urls.py
Example:
dajaxice_autodiscover()
from django.utils.importlib import import_module
import_module('project.app.services.servicemodule')
then registration starts to work as desired and generate all is needed.
- Better solution - make more intelligent autodiscover
Hope you'll take my notes into account when developing new version. Idea is really great but implementation and documenting... not so perfect... yet =)
dgmdan commented
I just ran into this. I was trying to use ajax.py in two directories but found that only one of them was being registered with dajaxice. The workaround worked, thanks!