TYPO3 Core

First, a bit of history, to know where I go:

.h2 History

Today I encountered a problem while working on a login service for an application using TYPO3 6.2 and Extbase.

My login service relies on a REST Repository of my own, that allows me to get data from a REST interface somewhere in my cloud. This always worked fine with TYPO3 4.7.7 and 4.7.17 but with the update to 6.2.5, a strange behaviour occured: the cached Datamap Objects were empty!

So I got down on my knees ans shoveld for some hours to get to the place where the magic happens: the DataMapperFactory. As expected, the fields and everything got parsed correctly by the DocCommentParser and the information was stored as expected by it. But what then happened was strange. Very strange: the tcaDefaultConfigs for the table was empty.

Long story short: at the point where my login service wanted to access my RESTCallModel for the first time, no TCA was loaded at all, therefore making a mapping of the fields from the TCA to the fields of the object impossible!

I've tried several things like force-loading the TCA or just don't cache the datamaps, but this didn't solve the problem, since for the first, other errors appeared that and the second didn't solve the problem at all, since at the point where I needed the dataMapper there would be any TCA ever.

I was able to solve the problem by first checking if a cached DataMapper for my object existed and then silently fail to log in, so that the object isn't called until the TCA is first loaded.

This is kind of an ugly way to do this and I'm not very proud of that hack but at least it works.

.h2 The point

It would be great to have TCA loaded for the login services since it impossible to properly load an object from the repository if it wasn't already cached due to missing TCA definitions at the point where the DataMapperFactory has to build the DataMapper object for a model.