Hi Friends -

I'd appreciate your expert thoughts and suggestions for the below requirement.

We dont have a static entity model i.e. our table doesnt contain a fixed set of coulmns. Or to put in another way we doesnt want our CUSTOMER entity to contain just id, firstName, lastName and age. We want our entity to be generic (name=value pair) so that we can accomodate N number of attributes without touching the TABLE def. This gives us lot of flexibility while boarding new customers etc. As of now our CUSTOMER table has around 200 attributes (and increasing).

Initially we started off with a POJO but i dont see thats a viable option. Appreciate if you can provide some suggestions on how to handle this. One option that appears to be the solution is a dynamic-map entity-mode. After browsing throught the forums it seems like it has many performance implications!

Thank you in advance.

Hello triveni,

I'm also very interested in using dynamic entities.

Currently I tried it with dynamic-map entity-mode. It seems to work, but I have no performance-comparison to static POJOs, beause I don't know how to realize it the other way. Dynamic-map is still in experimental state, but I hope that it will became stable.

Mark