Eclipse Community Forums: EclipseLink » @Multitenant guidelines

Help

Home

Home » Eclipse Projects » EclipseLink » @Multitenant guidelines

Show: Today's Messages :: Show Polls :: Message Navigator

@Multitenant guidelines [message #895593]

Fri, 13 July 2012 17:28

Andriy Zhdanov

Messages: 6
Registered: June 2012

Junior Member

Hi,

Could someone please help me to understand how to use @Multitenant in context of these two problems:

1) How to set orm mapping per tenant, using EMF per tenant?

2) Not using EMF per tenant, how entityManager.setProperty(MULTITENANT_PROPERTY_DEFAULT, <name>) is supposed to work in multi threading? Are EntityManager properties per thread?

3) Using EntityManager per tenant, 'drop-or-create-tables' ddl.generation droops table on every create, i.e. per tenant. Is it designed?

Thank you.

Report message to a moderator

Re: @Multitenant guidelines [message #895956 is a reply to message #895593]

Mon, 16 July 2012 16:03

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

1) You don't exactly set one orm.xml per tenant. Instead, you would have one orm.xml with shared mappings and then override it for individual tenants.
Here is a simple multitenant example using a shared orm.xml:
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Multitenant

Extending the shared mappings is done using a MetadataSource as described here:
http://wiki.eclipse.org/EclipseLink/Examples/JPA/MetadataSource
A more complex example of multitenant mentioned in the above is here:
http://wiki.eclipse.org/EclipseLink/Examples/MySports

2) EntityManagers should not be shared amongst threads, so I'm not sure what you mean. Each thread should obtain a new EntityManager as required - they are not thread safe.

3) Drop-and-create is as designed. Each login will attempt to drop tables and recreate them. It is not meant only to be used with development where the schema frequently can change and need to be recreated, and won't work well with multitenant apps as each tenant will log in with its own ootentially different metadata. You may want to use just the create table option, or the new "create-or-extend-tables" feature with multitenant apps.

Best Regards,
Chris

Report message to a moderator

Re: @Multitenant guidelines [message #896205 is a reply to message #895956]

Tue, 17 July 2012 14:51

Andriy Zhdanov

Messages: 6
Registered: June 2012

Junior Member

Hi Chris,

Thank you for your answer, it is very clear now. Strange I did not find mysports example myself, and those pages were not so clear before.

I have further question, though, if you don't mind.

Regarding 'Multitnant' doc, 1st item in the thread, about 'Persistence Usage for Multiple Tenants'

Do you have any idea, how @PersistenceUnit and/or @PersistenceContext container managed injection can be used with multi-tenancy?

I understand one can do the following in managed bean:

    @PersistenceContext(unitName = "myPU")
    EntityManager em;

Though, it's not possible to make it variable.

Thank you.

Report message to a moderator

Previous Topic:	Dynamic entities: adding properties after initialization
Next Topic:	cannot use eclipselink 2.x

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 12:03:39 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter