Not an issue anymore, the latest version (PR9) fixes this. On Mar 29, 5:26 pm, Peter <[email protected]> wrote: > Hi Ryan, > > Thanks for your response. > > In terms of my catchall route you are right, the second (and last) > route definition with that name is leading. But the other routes are > uniquely named, furthermore I have specified a prefix for my api > routing. > I've solved this for now using numeric prefixes, but it's not > something I prefer to do. > > Peter > > On Mar 8, 3:55 pm, ryan weaver <[email protected]> wrote: > > > > > > > > > Hey Peter- > > > Is it possible that you have a route inside the FrontBundle's routing.yml > > that has the same name as a route inside the ApiBundle's routing.yml? Since > > route name's must be unique (we use them to generate URLs), then the second > > appearance of the route inside FrontBundle would overwrite the one inside > > ApiBundle. This is the expected behavior. As a best practice, you should > > probably include some sort of prefix on each route in the individual bundles > > (e.g. api_some_route and front_some_route). > > > Thanks! > > > Ryan Weaver > > Lead Programmer - iostudio - Nashville, > > TNhttp://www.iostudio.comhttp://www.thatsquality.com > > Twitter: @weaverryan > > > On Fri, Mar 4, 2011 at 4:34 AM, Peter <[email protected]> wrote: > > > I'm not sure wether this is the place to file a bug report, but I > > > couldn't find anything else for Symfony2. > > > > Anyway, I found something that could be described as a bug: the > > > generated UrlMatcher class lists its routing options, ordered by route > > > name, rather than order of appearance. > > > > For instance, I have the following case: > > > > Main routing config: > > > api: > > > resource: @ApiBundle/Resources/config/routing.yml > > > prefix: /api > > > > front: > > > resource: @FrontBundle/Resources/config/routing.yml > > > > The problem is, a certain route that should be matched by the api > > > routing config is picked up by the front routing. When I disable the > > > front routing it works as intended. > > > > Furthermore, I have a catchall route in both configs, that seem to > > > overwrite each other due to this behaviour. Thus my API catchall route > > > is not available at all. > > > > If bundles really are supposed to work independently this should be > > > fixed, I think. > > > > -- > > > If you want to report a vulnerability issue on symfony, please send it to > > > security at symfony-project.com > > > > You received this message because you are subscribed to the Google > > > Groups "symfony developers" group. > > > 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/symfony-devs?hl=en
-- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. 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/symfony-devs?hl=en
