Thanks for the test unit. I included it in a sample app, it works as expected. I.E., the test unit does not reproduce the problem I have seen with CrudRestController sample app. I will try and get back to you in a week comparing the test unit versus sample app and check if it executes the appropriate line of code in the dispatcher.
On Tuesday, June 12, 2012 1:39:44 PM UTC-7, Alessandro Molina wrote: > > I tried replicating the issue in a test to include it inside the TG > test suite, but have been unable to. > > This is the test that I added to the test unit following your > guidelines, but it seems to correctly get dispatched to third/new and > not to the wrong controller as in your case: > https://gist.github.com/2919976 > > Let me know if that code replicates the issue for you. > > On Mon, Jun 11, 2012 at 3:06 AM,wrote: > > > > Did the sample application help narrow down the issue? Let me know if I > am > > mistaken. > > > > Thanks. > > > > > > On Tuesday, May 1, 2012 12:48:09 AM UTC-7, ozwyzard wrote: > >> > >> > >> 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/ > >> > >> > -- 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/-/HNGEEslItTkJ. 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.
