I was able to reproduce the problem using a sample application.  I was able 
to narrow it down to one issue.  With that one change, the 
nested CrudRestControllers work correctly in the sample app (as well as my 
app).  Without that change, it lands on the wrong 
controller in the sample app.

I have placed the pertinent files here: 
https://bitbucket.org/wyzard/sample_tg215crud_app/

There are 3 controllers, 3 simple models, and associated __init__.py files, 
one call to the level1 controller in root.py, and 
importing the model files in model/__init__.py

If the Level2Controller::get_one() method has a fixed argument, with no 
variable arguments, the level1/test/level2/level3/new routes to level2's 
new()
instead of level3's new().

If the Level2Controller::get_one() method takes dummy *arg and **kw args, 
the level3/new routes correctly to level3's new().

I have many print statements in my copy of the TG 2.1.5 code-base to track 
this, which I have not included in the sample app repository.

When the level2 get_one() takes variable args (ArgSpec), the 
_check_for_sub_controllers() 
routine takes the "if var_args:' path,
else it takes the 'elif:' path.

Is there a requirement that the get_one() method of nested 
CrudRestControllers should take variable arguments?  Am I using it 
incorrectly?

In essence, either I am using it incorrectly, or there is some defect in 
the ELIF case.

If you would like me to add other files, let me know.

Thank you for your time and effort.

wyzard

On Wednesday, April 25, 2012 10:49:39 PM UTC-7, ozwyzard wrote:
>
>
> Thank you for looking into it.  It will take me a few days to write a 
> sample app.  Hopefully sometime next week.  Hope that's okay.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/turbogears/-/2ifM-K53vHgJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en.

Reply via email to