|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
The wrapper mechanism we designed assumes you start with a "normal" OSGi bundle, and makes all of it tenant aware, so I'm confused about what you're trying to achieve.
The new multi-tenancy mechanism in the platform is designed to be completely transparent, so in order to use it you can simply rip out all your multi-tenancy code from your bundles and implement them as if there were no tenants. When you do that, you can then use the wrapper to create a multi-tenant version of such a bundle. That way you do not have to explicitly deal with multi-tenancy at all, plus we get two versions of each bundle. This should be the standard way of working.
The other alternative is to completely implement the multi-tenant version of the bundle yourself in which case you do not use the wrapper we designed, but implement multi-tenancy by hand. Especially if you also implement some form of storage, be sure to study the documentation and code of our wrapper and the life cycle listeners to ensure you correctly handle tenant-specific data.
My confusion comes from the fact that you seem to be doing both (using the wrapper and doing a custom implementation).