Is it a good idea to return nHibernate Entity from WebApi? For simple entity I tried to use this but what about complex entities. How will lazy loading be handled in that case?
Asked
Active
Viewed 364 times
0
-
1Well, I do use NHiberante, web-api and angularjs. And what does go form DB to UI and back is POCO object. But it is not for free. You have to manage serialization. So either you will use custom JSON Resolvers (injectable into web api) or convert POCO into DTO decorated with [Json] attributes. But in general, it is feasable... Maybe start, try to play with, google and ask here once an issue will appear... – Radim Köhler Jun 17 '14 at 10:53
1 Answers
4
It is possible to return complex entities via WebAPI, however it is not the best way to do it, what I would suggest is create a DTO object to match the client side operation map it to the NHibernate entity and send it over the API.
With regard to the lazy loading, it will have no use if you expose the object via the web API, as the object serializes all the properties of the entity will be accessed and they will be loaded from the persistence, so in fact using lazy loading is inefficient in this scenario.

Low Flying Pelican
- 5,974
- 1
- 32
- 43