You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For almost all of my/our applications (SAAS/Cloud/... solutions) we have one instance of an application running for multiple customers/tenants. One colum in the relevant tables contains a key to the customer that actually owns that data (multi-tenant shared schema). Would be great if OptimusFaces (or maybe OmniPersistence?) would have explicit support for this to (besides being able to do it in custom filters).
In which way this would be fully flexible I have no real clue yet. Maybe by defining a property in a web.xml which contains a field name that if present on the entity is used in the query retrieving the value from the session as an EL expression. Or maybe adding it as an annotation on the entity. I'm explicitly not mentioning multi-tenancy in separate schema's or separate db's or...
But most of all, really, really cool work. I have something homegrown that is sort of like this but with (at most) 40% of the functionality of the OptimusFaces and 10% of the OmniPersistence that I can now start removing... Compliments upfront! Will start experimenting over the weekend.
The text was updated successfully, but these errors were encountered:
Thanks for compliments :) It's not yet finished though. And then I need to test with MyFaces and EclipseLink too. Any feedback, improvements and new features is always welcome at this stage.
For almost all of my/our applications (SAAS/Cloud/... solutions) we have one instance of an application running for multiple customers/tenants. One colum in the relevant tables contains a key to the customer that actually owns that data (multi-tenant shared schema). Would be great if OptimusFaces (or maybe OmniPersistence?) would have explicit support for this to (besides being able to do it in custom filters).
In which way this would be fully flexible I have no real clue yet. Maybe by defining a property in a web.xml which contains a field name that if present on the entity is used in the query retrieving the value from the session as an EL expression. Or maybe adding it as an annotation on the entity. I'm explicitly not mentioning multi-tenancy in separate schema's or separate db's or...
But most of all, really, really cool work. I have something homegrown that is sort of like this but with (at most) 40% of the functionality of the OptimusFaces and 10% of the OmniPersistence that I can now start removing... Compliments upfront! Will start experimenting over the weekend.
The text was updated successfully, but these errors were encountered: