XData return an List without freeing it

[wlandgraf (Wagner Landgraf)]

Hi @Ansgar_Gosling, welcome to TMS Support Center!

It's partially possible (see below)

This is a very peculiar situation, actually, because usually you should not use global/singleton data in the services, because they are multithreaded.

Thus, it will only work and make sense in the specific case where you have global data that is never modified. It might be your case, but then I would just suggest that you create a local copy of the data from the global one and return it.

What you can do to help in this task is to tell XData to destroy only the root object (the list, for example) and not the "inner" objects (the itens in list, for example).

You do that this way:

TXDataOperationContext.Current.Handler.ActionResultDestruction := TActionResultDestruction.RootOnly;

Reference:

Returning nested PODO from XData service

XData destroys all objects serialized in the response. Thus, it will indeed destroy both TLoginResult instance and the TLoginUser instance, so you are fine. If you want to keep the User lifetime to be managed by the TLoginResult object, you can set the following property in your Login implementation: TXDataOperationContext.Current.Handler.ActionResultDestruction := TActionResultDestruction.RootOnly; This way, only the root object (TLoginResult) will be destroyed, and it will be up to you (or …