Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Examples/MySports/EMFperTenant"
(→Provider) |
|||
Line 7: | Line 7: | ||
While EclipseLink 2.4.0 does not offer explicit support for EntityManagerFactory (EMF) per tenant it is possible to construct an extended JPA provider that handles this usage scenario. In order to introduce an extended PersistenceProvider two classes needed to be added to the MySports example: | While EclipseLink 2.4.0 does not offer explicit support for EntityManagerFactory (EMF) per tenant it is possible to construct an extended JPA provider that handles this usage scenario. In order to introduce an extended PersistenceProvider two classes needed to be added to the MySports example: | ||
* example.mysports.persistence.MySportsProvider ([http://git.eclipse.org/c/eclipselink/examples/mysports.git/tree/MySports%20App/jpa-provider/example/mysports/persistence/MySportsProvider.java src]) | * example.mysports.persistence.MySportsProvider ([http://git.eclipse.org/c/eclipselink/examples/mysports.git/tree/MySports%20App/jpa-provider/example/mysports/persistence/MySportsProvider.java src]) | ||
+ | ** Handles the use of 'mysports-{league}' persistence unit names where the prefix is used as the template persistence unit name. | ||
* example.mysports.persistence.MySportsProviderInitializer ([http://git.eclipse.org/c/eclipselink/examples/mysports.git/tree/MySports%20App/jpa-provider/example/mysports/persistence/MySportsProviderInitializer.java src]) | * example.mysports.persistence.MySportsProviderInitializer ([http://git.eclipse.org/c/eclipselink/examples/mysports.git/tree/MySports%20App/jpa-provider/example/mysports/persistence/MySportsProviderInitializer.java src]) | ||
+ | ** Handles the initialization from both the container and agent weaving | ||
=== Configuration: persistence.xml === | === Configuration: persistence.xml === | ||
Line 37: | Line 39: | ||
</persistence> | </persistence> | ||
</source> | </source> | ||
+ | |||
+ | == Java SE Testing == | ||
+ | |||
+ | In order to test outside of a container using the custom PersistenceProvider a new agent is required. | ||
+ | * example.mysports.persistence.MySportsWeavingAgent ([http://git.eclipse.org/c/eclipselink/examples/mysports.git/tree/MySports%20Tests/agent-src/example/mysports/persistence/MySportsWeavingAgent.java src]) | ||
+ | * META-INF/MANIFEST.MF ([http://git.eclipse.org/c/eclipselink/examples/mysports.git/tree/MySports%20Tests/agent-src/META-INF/MANIFEST.MF src]) | ||
+ | ** <pre>remain-Class: example.mysports.persistence.MySportsWeavingAgent</pre> | ||
== Usage == | == Usage == |
Revision as of 14:26, 21 June 2012
The EclipseLink MySports Example implements a SaaS based solution where a single instance of the MySports application to handle requests for multiple leagues (tenants). Each league has its own custom look and feel as well as custom extension attributes for entities. Having different extension attributes requires different mappings for each tenant and thus you must have a separate EntityManagerFactory (EMF). To implement the EMF per tenant in a common application the EclipseLink persistence framework needs to be extended with a custom JPA persistence provider.
Provider
While EclipseLink 2.4.0 does not offer explicit support for EntityManagerFactory (EMF) per tenant it is possible to construct an extended JPA provider that handles this usage scenario. In order to introduce an extended PersistenceProvider two classes needed to be added to the MySports example:
- example.mysports.persistence.MySportsProvider (src)
- Handles the use of 'mysports-{league}' persistence unit names where the prefix is used as the template persistence unit name.
- example.mysports.persistence.MySportsProviderInitializer (src)
- Handles the initialization from both the container and agent weaving
Configuration: persistence.xml
Here is what the template persistence unit is defined as. It is this persistence unit that is used and customized to create the tenant specific persistence unit.
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"> <persistence-unit name="mysports" transaction-type="RESOURCE_LOCAL"> <provider>example.mysports.persistence.MySportsProvider</provider> <non-jta-data-source>jdbc/MySports</non-jta-data-source> <mapping-file>META-INF/local-eclipselink-orm.xml</mapping-file> <class>example.mysports.model.User</class> <class>example.mysports.model.Team</class> <class>example.mysports.model.Player</class> <class>example.mysports.model.Division</class> <validation-mode>NONE</validation-mode> <properties> <!-- ... --> </properties> </persistence-unit> </persistence>
Java SE Testing
In order to test outside of a container using the custom PersistenceProvider a new agent is required.
- example.mysports.persistence.MySportsWeavingAgent (src)
- META-INF/MANIFEST.MF (src)
-
remain-Class: example.mysports.persistence.MySportsWeavingAgent
-
Usage
In order to use
JPS-RS Usage
Since the MySports application also exposes its persistence unit(s) over REST using JPA-RS the tenant specific persistence units must be exposed as well.