Guy,
A couple of items. It isn't explicitly pointed out (but is there in
the configuration) that the "tenant id" property name is
application definable. EclipseLink defaults to a certain name but
the name of the tenant id isn't particularly special in any way and
as you show in an example there can be more than one.
Also, the tenant id value resolution is not spelled out.
EclipseLink should look in the EM properties, the EMF properties,
and then in the Context if in an Java EE container. That should be
spelled out.
Looking good,
Shaun
On 07/03/2011 3:29 PM, Guy Pelletier wrote:
I have now updated the document after some initial
feedback (notice the new link, the doc has moved)
http://wiki.eclipse.org/EclipseLink/Development/Indigo/Multi-Tenancy
Please review and provide any feedback.
Thanks,
Guy
On 17/02/2011 11:49 AM, Guy Pelletier wrote:
All,
This document provides a first cut outline to our multi-tenant
using a shared schema solution aimed for the 2.3 release.
http://wiki.eclipse.org/EclipseLink/DesignDocs/Multi-Tenancy
Please review and provide any feedback.
Thanks,
Guy
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
--
Shaun Smith | Principal Product Manager
Phone: +1.905.502.3094 | Mobile: +1.416.558.6244
Oracle Fusion Middleware, TopLink
ORACLE Canada | 100 Milverton Drive, Mississauga, Ontario | L5R
4H1
Oracle is committed to developing practices and
products that help protect the environment
|