Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Configuring a EclipseLink JPA Application (ELUG)"
m |
m (→How to Provide Authenticated Reads and Writes of Secured Data Through the Use of an Exclusive Isolated Client Session) |
||
| Line 18: | Line 18: | ||
If you want to [[Introduction%20to%20Data%20Access%20(ELUG)#Providing Authenticated Reads and Writes of Secured Data Through the Use of an Exclusive Isolated Client Session|provide read and write control]] for your EclipseLink JPA application, specify in the [[Customizing%20the%20EclipseLink%20Application%20(ELUG)#Using the Session Customizer Class|SessionCustomizer]] that an exclusive connection should be used. For more information, see [[Configuring%20a%20Database%20Login%20(ELUG)#SessionCustomizer-config|Configuring Session Login Using SessionCustomizer]]. | If you want to [[Introduction%20to%20Data%20Access%20(ELUG)#Providing Authenticated Reads and Writes of Secured Data Through the Use of an Exclusive Isolated Client Session|provide read and write control]] for your EclipseLink JPA application, specify in the [[Customizing%20the%20EclipseLink%20Application%20(ELUG)#Using the Session Customizer Class|SessionCustomizer]] that an exclusive connection should be used. For more information, see [[Configuring%20a%20Database%20Login%20(ELUG)#SessionCustomizer-config|Configuring Session Login Using SessionCustomizer]]. | ||
| − | The next step is to pass one or more properties to the <tt>createEntityManagerFactory</tt> method, as the following example demonstrates. These properties should indicate that one or more specific entities use an isolated cache. | + | The next step is to pass one or more properties to the <tt>createEntityManagerFactory</tt> method, as the following example demonstrates. These properties should indicate that one or more specific entities use an isolated cache. |
| − | + | ||
| − | + | ||
| + | Map properties = new HashMap(); | ||
| + | properties.put("eclipselink.cache.shared.Employee", "false"); | ||
| + | ... | ||
| + | EntityManagerFactory emf = Persistence.createEntityManagerFactory(properties); | ||
| + | In the preceding example, an entity named <tt>Employee</tt> uses isolated cache and will be read and written through an exclusive connection. | ||
| + | For more information, see [[Using%20TopLink%20JPA%20Extensions%20(ELUG)#How to Use the Persistence Unit Properties for Caching|How to Use the Persistence Unit Properties for Caching]]. | ||
==Setting Up Packaging== | ==Setting Up Packaging== | ||
Revision as of 10:53, 13 June 2008
Contents
This section contains information on how you can configure your EclipseLink persistence project.
When configuring an EclipseLink JPA application you cannot use the org.eclipselink.sessions.Project class, but you can still customize sessions and descriptors by using the customizer extensions (see Using EclipseLink JPA Extensions for Customization and Optimization).
You can set up your EclipseLink JPA application using various IDEs.
At run time, if the eclipselink.jar file is on the application classpath, you have the option to choose EclipseLink as a persistence provider for your application.
Configuring Oracle Database Proxy Authentication for a JPA Application
One of the features of the Oracle Database is proxy authentication. For more information, see Oracle Database Proxy Authentication.
How to Provide Authenticated Reads and Writes of Secured Data Through the Use of an Exclusive Isolated Client Session
If you want to provide read and write control for your EclipseLink JPA application, specify in the SessionCustomizer that an exclusive connection should be used. For more information, see Configuring Session Login Using SessionCustomizer.
The next step is to pass one or more properties to the createEntityManagerFactory method, as the following example demonstrates. These properties should indicate that one or more specific entities use an isolated cache.
Map properties = new HashMap();
properties.put("eclipselink.cache.shared.Employee", "false");
...
EntityManagerFactory emf = Persistence.createEntityManagerFactory(properties);
In the preceding example, an entity named Employee uses isolated cache and will be read and written through an exclusive connection.
For more information, see How to Use the Persistence Unit Properties for Caching.
Setting Up Packaging
You can package your application manually (see Packaging an EclipseLink JPA Application), or use an IDE.