[FLOW3-general] No controller youl be resolved for routeParts

[Bastian Waidelich]

Andreas Beyl wrote:

> Well, the global Routes.yaml contains this [...]

Looks all good (except that you probably don't want to have Welcome & 
Flow routes active in your application).
It looks like none of your routes match, but only one of the Flow 
fallback routes (that's why the exception message is a bit misleading).

And the reason for that is probably:
Similar to RealUrl the Flow routing framework uses a lookup table to 
store references to "object route parts" and the corresponding URI 
segment in order to avoid ambiguity and to avoid that an URI breaks when 
you rename a model (therefore you won't need an extra property 
uriSegment, the ObjectRoutePart takes care of normalizing any object 
property).
A drawback is: The routing doesn't know about the mapping until it first 
created an URI pointing to the entity (that's where the object path 
mapping is created if it doesn't exist yet).

For a REST service you would usually first retrieve the URIs in some 
index action. If that doesn't work in your case and "OLBW" is some kind 
of "code" that won't be duplicate and doesn't change, you could use that 
as identifier in the db - then you won't need the "objectType" part in 
your route at all.
Alternatively you could create a really simple route part handler that 
looks up the league by code and vice versa (see [1]).

HTH

[1] 
http://flow.typo3.org/documentation/guide/partiii/routing.html#route-part-handlers

-- 
Bastian Waidelich
--
Core Developer Team

TYPO3 .... inspiring people to share!
Get involved: typo3.org